Overview
- Dataset ID:
0301 - Tables:
blockdb_evm.b0301_liquidity_pools_reserves_v1,blockdb_evm.b0301_liquidity_pools_reserves_details_v1 - Description: Per-pool reserve snapshots at every on-chain event (one row per event), with optional granular tick/bin/range detail rows joined via
snapshot_id. - Primary key:
(pool_uid, block_number, tx_index, log_index)(reserves);(snapshot_id, tick/bin/range)(details) - API: POST /evm/reserves
- CSV Sample (reserves): Download
- CSV Sample (details): Download
- JSON Sample (reserves): Download
- JSON Sample (details): Download
Sample Viewer
Snapshot columns (blockdb_evm.b0301_liquidity_pools_reserves_v1)
Primary key: (pool_uid, block_number, tx_index, log_index).
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.
Uniqueness: one row per
(snapshot_id, tick), per (snapshot_id, bin_id), or per (snapshot_id, lower_tick, upper_tick) range.
Tick range coverage: Detail rows cover a ±1% range around the current price tick by default. If you need a wider tick range or full tick coverage, contact us.
Use cases
- Pool state backtesting and simulation
- Liquidity distribution analysis (ticks/bins)
- TVL and pricing model inputs
Related datasets
Liquidity pools
Pool registry keyed by
pool_uid.Swap fees
Per-swap economics tied to the same pool events.