Skip to main content

Overview

  • Dataset ID: 0301
  • Tables:
    • blockdb_evm.b0301_liquidity_pools_reserves_v1 — One row per pool per on-chain observation event.
    • blockdb_evm.b0301_liquidity_pools_reserves_details_v1 — Granular tick/bin/range rows for a snapshot; join snapshot_id to parent _tracing_id.
  • API: POST /evm/reserves

Snapshot columns (blockdb_evm.b0301_liquidity_pools_reserves_v1)

Primary key: (pool_uid, block_number, tx_index, log_index).
ColumnTypeDescription
chain_idBIGINTEVM chain identifier; see Chain.
pool_uidBYTEAPool surrogate key; FK → b0211_liquidity_pools_v1.pool_uid.
exchange_idINTEGERExchange identifier.
type_idINTEGERLiquidity pool type identifier.
block_numberBIGINTBlock when this state was observed.
block_timeTIMESTAMPTZBlock time.
tx_indexINTEGERTransaction index within the block.
log_indexINTEGERLog index within the transaction.
reservesNUMERIC(78,0)[]Current reserves per token for even-style pools (raw units).
current_tickINTEGERCurrent tick (concentrated liquidity, e.g. Uniswap v3).
current_sqrt_priceNUMERIC(49,0)Q64.96 sqrt price integer.
current_binINTEGERCurrent bin id for bin-style AMMs.
_tracing_idBYTEABlockDB tracing ID; unique.
_parent_tracing_idsBYTEA[]Parent tracing IDs.
_created_atTIMESTAMPTZRecord creation time.
_updated_atTIMESTAMPTZRecord last update time.
CHECK (ck_b0301_reserves_has_payload) requires at least one of: reserves, current_tick, current_bin, or (per DDL) liquidity_values, amounts0 when those columns exist in your deployed schema. The shipped DDL file references liquidity_values / amounts0 in the payload check; confirm deployed columns match your environment.

Details columns (blockdb_evm.b0301_liquidity_pools_reserves_details_v1)

Join: details.snapshot_id = reserves._tracing_id.
ColumnTypeDescription
chain_idBIGINTEVM chain identifier; see Chain.
snapshot_idBYTEAParent snapshot _tracing_id.
tickINTEGERSingle-tick locator (v3-style).
lower_tickINTEGERRange lower bound.
upper_tickINTEGERRange upper bound.
bin_idINTEGERSingle-bin locator.
liquidityNUMERIC(38,0)Engine-native liquidity (e.g. Uniswap v3 (L)).
amount0NUMERIC(78,0)Token0 amount at locator (decimals-adjusted).
amount1NUMERIC(78,0)Token1 amount at locator (decimals-adjusted).
Uniqueness: one row per (snapshot_id, tick), per (snapshot_id, bin_id), or per (snapshot_id, lower_tick, upper_tick) range.

Use cases

  • Pool state backtesting and simulation
  • Liquidity distribution analysis (ticks/bins)
  • TVL and pricing model inputs

Liquidity pools

Pool registry keyed by pool_uid.

Swap fees

Per-swap economics tied to the same pool events.
Last modified on March 21, 2026