How Teams Use BlockDB
BlockDB’s catalog spans ledger data, liquidity intelligence, pricing analytics, and verification primitives. This page highlights the most frequent deployment patterns so you can jump directly to the right guides.1. Research & Analytics
- Goal: Build dashboards or notebooks that track chain activity, token flows, or venue liquidity.
- Datasets:
blocks,transactions,logs, plustoken-to-token prices. - API Focus: Raw Data endpoints for deterministic querying, combined with Pricing Suite for normalized price context.
- Why BlockDB:
_tracing_idlineage fields let analysts reconcile every metric with the original onchain proof.
2. Risk & Compliance
- Goal: Prove data provenance, replay suspicious transactions, and maintain auditable records.
- Datasets:
function resultsfor deterministic state,liquidity pools, andreserves. - API Focus: Lineage & Verification endpoints to recompute receipt roots or logs blooms.
- Why BlockDB: Delivery SLAs and Schema Governance ensure compatibility with regulated reporting stacks.
3. Trading & Pricing
- Goal: Feed execution systems with venue-aware spot prices, VWAP/LWAP aggregates, and liquidity curves.
- Datasets:
token-to-token prices L1/L2/L3,pricing analytics. - API Focus: Pricing Suite endpoints plus enumerations for
asset classesandfiat currencies. - Why BlockDB: Consistent normalization lets pricing desks compare onchain venues with centralized exchange references.
Choosing Your Path
Mix and match datasets: many teams start with archive deliveries to backfill analytics, then graduate to the real-time feeds described in the next Quickstart sections.
- Start with Archive Delivery if you need to hydrate years of data before going live.
- Jump to Real Time Delivery when you’re ready for incremental updates or streaming payloads.