Skip to main content

​
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.

​
How to navigate the EVM catalog

  1. Start with the global Dataset Index to see every published dataset (across chain families).
  2. Use the category links below to drill into the dataset pages by use case.
  3. Use _tracing_id with the Lineage endpoints and Verification suite to prove every record matches onchain state.

​
Categories (by use case)

Ledger & execution primitives

Blocks, transactions, logs, contracts, and deterministic function results.

Tokens & pools

Token registries, pool inventory, and pool configuration metadata (including fee terms).

Reserves

Normalized pool liquidity snapshots across AMM models (constant-product, concentrated liquidity, bin pools).

Swaps

Swap-derived datasets for pool economics (per-swap fee accounting and related swap signals).

Pricing layers

Price surfaces and aggregates (L1/L2/L3, OHLC, swap prints, VWAP/LWAP) derived from verified on-chain activity.

Yields & ROI

Pool yield and ROI predictions across fixed horizons, with full lineage back to swaps and reserves.

​
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_at appear 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

  1. Start with the Dataset Index for a complete list of IDs and table names.
  2. Review dataset-specific docs in /data-catalog/evm/** to understand primary keys, column semantics, and verification hooks.
  3. When ingesting data, use the Lineage endpoints and Verification suite to prove every record matches onchain state.
  • 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.