Scope
The EVM catalog spans the canonical ledger, execution traces, liquidity metadata, and pricing layers for Ethereum and compatible L2/L3 chains. Every table in/data-catalog/evm mirrors the SQL definitions published in /BlockDb.Postgres.Tables.Public, which in turn match the payloads returned by the EVM API family.
Dataset Families
| Family | Dataset IDs | Highlights |
|---|---|---|
| Ledger & Execution | 0101-0105 | Blocks, transactions, logs, contracts, deterministic function results. |
| Tokens & Pools | 0201-0203 | ERC-20 / ERC-721 registries plus liquidity pool inventory. |
| Reserves | 0301 | Normalized pool reserves ready for pricing/risk engines. |
| Pricing Layers | 0401-0404 | Synthetic L1-L3 token prices and OHLC aggregates. |
| Pricing Analytics | 0501-0502 | VWAP/LWAP windows derived from the pricing layers. |
Design Principles
- Schema parity: Column names, types, and constraints stay aligned with the SQL scripts shipped alongside this repo.
_tracing_id,_created_at, and_updated_atappear in every table for lineage. - Deterministic identifiers: Dataset IDs map to the Dataset enumeration and are referenced inside API responses (
data[].dataset_id). - Chain coverage: Use the Chain enumeration to see which networks (Ethereum mainnet, Polygon, Arbitrum, Base, etc.) are available per dataset.
How to Work With the Catalog
- Start with the Dataset Index for a complete list of IDs and table names.
- Review dataset-specific docs in
/data-catalog/evm/*to understand primary keys, column semantics, and verification hooks. - When ingesting data, use the Lineage endpoints and Verification suite to prove every record matches onchain state.
Related Resources
- Delivery options - determine how to receive the EVM tables (archives, API, streaming).
- Quickstart - bootstrap schemas and run your first EVM request.
- Coverage - inspect chain + temporal coverage before building analytics.