Refresh Cadence
| Dataset Family | Expected Latency | Notes |
|---|---|---|
| Ledger & Execution (0101-0105) | < 5 minutes | Ingested directly from BlockDB Historic stream processors. |
| Tokens & Pools (0201-0203) | < 5 minutes | Includes contract verification heuristics before publishing. |
| Reserves (0301) | < 5 minutes | Triggered whenever on-chain state changes exceed configured thresholds. |
| Pricing Layers (0401-0404) | < 5 minutes | Updated on every book change from upstream venues. |
| Pricing Analytics (0501-0502) | < 5 minutes | Recomputed when underlying depth windows roll. |
How do I monitor data freshness?
Use the_updated_at column or the count and cursor envelope timestamps in the API.Dashboards can alert you when
_updated_at drifts beyond the SLA for the relevant dataset family.
Backfill Strategy
- Hotfix windows — If a venue outage occurs, BlockDB will replay the affected range.
- Historical expansions — New datasets start with block 0.
Need tighter guarantees? Mirror the dataset via the API and compare
_tracing_id values. Differences indicate your mirror is stale.Freshness by channel
- API: near-real-time, subject to reorg buffer and endpoint-specific processing
- Warehouse shares: near-real-time to hourly, depending on provider sync cadence
- Bulk exports (SFTP/S3/Blob): nightly snapshots with ad-hoc hotfix replays when required