Inspect candle coverage and storage health
Monitor active collection, timeframe backfill, data span, gaps, pools, fetch freshness, and database footprint.
System
Historical candle storage
Coverage
1m through 1d timeframes
Quality
Span, gaps, pools, fetch
Maintenance
Token and inactive cleanup
What the OHLCV Data tab is for
OHLCV Data is a dedicated storage and collection view, not a normal token list. It reports historical candle coverage for charts and strategies. These candles never replace direct pool prices for execution or P&L.
Reading the interface
Use membership, coverage, and actions together before drawing a conclusion about a token.
Coverage columns
The table summarizes historical-data completeness.
Status and priority
Show whether collection is active and its maintenance urgency.
Candles and backfill
Report candle count and completed 1m, 5m, 15m, 1h, 4h, 12h, and 1d coverage.
Span, gaps, pools, fetch
Measure history depth, missing intervals, pool count, and freshness.
Storage maintenance
These controls remove historical data, not token identity.
Delete one token
Removes stored candles and OHLCV pools after confirmation.
Cleanup inactive
Deletes records older than the inactive-hour threshold.
Global summary
Reports total tokens, active tokens, candles, and database size.
Recommended workflow
- 1
Review global counts and database size.
- 2
Sort by backfill, gaps, span, or last fetch.
- 3
Allow active collection to repair expected gaps.
- 4
Run cleanup only when old history should be removed.
Practical guidance
- OHLCV drives charts and strategies; pool price drives trades and P&L.
- Deleted data may need collection and backfill again.
OHLCV deletion is destructive. Confirm the mint and storage intent before removing data.