BlockDB Canonical Raw Data (Lineage-Verified) | Ethereum & EVM Chains | Historical, EOD, ...

Dataset Overview
Canonical Raw Data represents the ground-truth layer of DeFi and on-chain intelligence.
Each sub-dataset captures data at a distinct level of the EVM execution stack - from the raw blocks to raw contract functions results. Each record includes a deterministic _tracing_id, forming the root lineage reference for all derived BlockDB datasets

Chains and Coverage
ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request).
Full history from chain genesis; reorg-aware real-time ingestion and updates.

Included Datasets

1. BlockDB Canonical Raw Blocks (Lineage-Verified)
Canonical block-level data including block hashes, parent relationships, miner addresses, gas parameters, and recomputed receipt roots for integrity verification.

2. BlockDB Canonical Raw Transactions (Lineage-Verified)
Full transaction-level coverage across all EVM networks, including sender/receiver, input data, gas details, and other fields.

3. BlockDB Canonical Raw Logs (Lineage-Verified)
Log events emitted by contracts, normalized across protocols.

4. BlockDB Discovered Smart Contracts
Catalog of deployed smart contracts discovered through emmitted logs.

5. BlockDB Discovered Smart Contract Function Results
Structured outputs of executed on-chain function calls (e.g., eth_call, view functions).

Lineage
Each record of these datasets includes a deterministic _tracing_id, forming the root lineage reference for all derived BlockDB datasets (swaps, liquidity, and token prices).
This ensures verifiable traceability, reproducibility, and proof-of-derivation for every downstream record.

Common Use Cases
• Establish a canonical on-chain ground truth across multiple EVM chains
• Power downstream datasets (tokens, swaps, liquidity, prices) with verified base-layer inputs
• Build data lineage visualizations or chain-state replayers for validation and analytics

Quality
• Verifiable lineage: deterministic cryptographic hashes per row
• Reorg-aware ingestion: continuity and consistency across forks
• Complete historical coverage: from chain genesis to present