BlockDB/Liquidity-Pools-Reserves-Ethereum-And-EVM-Cryptocurrency-Data

Sample Notice

This dataset contains a small sample of the full BlockDB Liquidity Pools Reserves dataset.
It is provided for evaluation, research, and interoperability testing only.

If you need full historical coverage, real-time streaming, or end-of-day (EOD) exports please contact us directly:

📧 support@blockdb.io
🌐 https://www.blockdb.io

Dataset Overview

Time-series of pool reserve/state snapshots across all AMM types. Each row represents a snapshot of pool state at a specific on-chain event, including reserves for constant-product pools and tick/bin data for concentrated liquidity pools (Uniswap v3/v4, Algebra, TraderJoe bins, etc.).

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.

Schema

List of columns exactly as delivered:

•	id BIGINT – Unique snapshot identifier (primary key)
•	pool_uid BYTEA – Unique pool identifier (FK to liquidity_pools)
•	exchange_id INTEGER – Exchange/DEX identifier
•	type_id INTEGER – Pool type identifier (FK to liquidity_pool_types)
•	block_number BIGINT – Block when this state was observed
•	block_time TIMESTAMPTZ – UTC timestamp when the block was mined
•	tx_index INTEGER – Transaction index within the block
•	log_index INTEGER – Log index within the block
•	reserves NUMERIC(78,0)[] – Array of current reserves per token for even-style pools (raw units)
•	current_tick INTEGER – Current tick for concentrated-liquidity pools (e.g., Uniswap v3)
•	current_sqrt_price NUMERIC(49,0) – Q64.96 sqrt price as integer; decode via (value / 2^96)^2 for mid-price
•	current_bin INTEGER – Current bin id for bin-based AMMs (e.g., TraderJoe v2)
•	_tracing_id BYTEA – Tracing ID of this reserves record
•	_genesis_tracing_ids BYTEA[] – Tracing IDs of the genesis records leading to this record
•	_parent_tracing_ids BYTEA[] – Tracing IDs of the parent records leading to this record
•	_created_at TIMESTAMPTZ – Record creation timestamp
•	_updated_at TIMESTAMPTZ – Record last update timestamp

Notes

•	At least one of reserves, current_tick, or current_bin is always populated.
•	Unique constraint: (pool_uid, block_number, tx_index, log_index) guarantees one snapshot per pool per event.
•	For Q64.96 sqrt price: mid_price = (current_sqrt_price / 2^96)^2, then adjust for token decimals.
•	Indexes on (pool_uid, block_number DESC, tx_index DESC, log_index DESC), (block_number, tx_index, log_index), and block_time support fast lookups.

Lineage

Each reserves record includes deterministic _tracing_id, _genesis_tracing_ids, and _parent_tracing_ids, providing:

•	Provenance tracking from raw logs to decoded reserves snapshots
•	Reproducible analytics and signal extraction
•	Cross-system consistency checks (RPC vs. indexers vs. internal warehouses)

Common Use Cases

•	Reconstructing historical pool states for backtesting
•	TVL (Total Value Locked) calculations
•	Liquidity depth analysis and slippage estimation
•	Price impact modeling for concentrated liquidity pools

Quality

•	Verifiable lineage: deterministic cryptographic hashes per row
•	Reorg-aware ingestion: continuity and consistency across forks
•	Complete historical coverage: from chain genesis to present