BlockDB Liquidity Pools Reserves | Log-by-Log | Ethereum & EVM Chains | Historical, EOD, ...

Dataset Overview
Canonical, lineage-verified dataset of on-chain liquidity reserves capturing the complete state of AMM pools at block-level and real-time granularity.
Each record represents a verifiable snapshot of a pool’s state - either its aggregate reserve vector or its fine-grained tick/bin liquidity distribution - linked deterministically to the on-chain event that produced it.

Supports all major AMM architectures - from even-distribution (V2-style) to concentrated (V3/V4-style) and bin/range-based models - with full reproducibility from raw logs.

Key traits
• Protocol-aware coverage for V2, V3, V4, and hybrid AMM variants
• Historical snapshots and reorg-aware real-time updates
• Full tick-range from a minimum of -887272 to a maximum of 887272
• Highest granularity possible: Log-by-Log
• Schema-stable, versioned, and audit-ready
• Deterministic, traceable lineage from pool creation to latest reserve update

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.
Covers major protocols:
Uniswap V2/V3/V4, SushiSwap V2/V3, PancakeSwap V2/V3, Aerodrome V1/Slipstream, Curve, Balancer, TraderJoe, Maverick, Solidly, and others.

Schema
List the columns exactly as delivered.

liquidity_pools_reserves - pool-level snapshots
• id BIGINT - identity primary key
• pool_uid BIGINT - FK → liquidity_pools(uid)
• exchange_id INTEGER NOT NULL - exchange identifier (e.g. 1 Uniswap, 2 Sushiswap)
• type_id INTEGER NOT NULL - pool type FK (constant-product, concentrated, stable/weighted, etc.)
• block_number BIGINT - first block where the token was recognized
• block_time TIMESTAMPTZ - UTC timestamp when the block was mined
• tx_index INTEGER - tx index for that event
• log_index INTEGER - log index for that event
• reserves NUMERIC(78,0)[] - raw reserves per token (V2-style or Balancer pools)
• current_tick INTEGER - active tick for concentrated-liquidity pools
• current_sqrt_price NUMERIC(49,0) - Q64.96-encoded sqrt price (sqrtP = value / 2^96)
• current_bin INTEGER - bin index for bin-style AMMs
• _tracing_id BYTEA - deterministic row-level hash
• _parent_tracing_ids BYTEA[] - hash(es) of immediate parent rows in the derivation graph
• _genesis_tracing_ids BYTEA[] - hash(es) of original sources (genesis of the derivation path)
• _created_at TIMESTAMPTZ - Record creation timestamp.
• _updated_at TIMESTAMPTZ - Record last update timestamp

liquidity_pools_reserves_details - granular tick/bin distribution
• snapshot_id BIGINT - FK → liquidity_pools_reserves(id)
• tick INTEGER - single-tick record (Uniswap V3-style)
• lower_tick INTEGER - lower bound of a range (position-based)
• upper_tick INTEGER - upper bound of a range
• bin_id INTEGER - bin index (for bin-style AMMs)
• liquidity NUMERIC(38,0) - engine-native liquidity metric (e.g., Uniswap V3 L)
• amount0 NUMERIC(78,0) - token0 amount at this locator (raw units)
• amount1 NUMERIC(78,0) - token1 amount at this locator (raw units)

Notes
• All reserve and amount values are in raw on-chain token units.
• Apply ERC-20 decimals from erc20_tokens table when scaling for price or display.
• One of the payloads must be present per liquidity_pools_reserves row.

Lineage
Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph:
• _tracing_id - this row’s identity
• _parent_tracing_ids - immediate sources
• _genesis_tracing_ids - original on-chain sources
This supports audits and exact reprocessing to source transactions/logs/function calls.

Common Use Cases
• Price, TVL, and slippage calculations across pools and chains
• Routing and arbitrage research (depth, fee tiers, fragmentation)
• Market-structure analytics and liquidity regime detection
• Backtesting and AI modeling with verifiable pool states
• Monitoring dashboards for protocol health, volatility, and liquidity shifts

Quality
• Each row includes a cryptographic hash linking back to raw on-chain events for auditability.
• Tick-level resolution for precision.
• Reorg-aware ingestion ensuring data integrity.
• Complete backfills to chain genesis for consistency.