|
|
--- |
|
|
license: cc-by-nc-4.0 |
|
|
tags: |
|
|
- ethereum |
|
|
- evm |
|
|
- blockchain |
|
|
- cryptocurrency |
|
|
- crypto |
|
|
- onchain-data |
|
|
- tabular |
|
|
- timeseries |
|
|
- datasets |
|
|
- pandas |
|
|
- polars |
|
|
- duckdb |
|
|
pretty_name: BlockDB Liquidity Pools - Sample |
|
|
size_categories: |
|
|
- 10M<n<100M |
|
|
--- |
|
|
|
|
|
## Sample Notice |
|
|
|
|
|
This dataset contains **a small sample** of the full BlockDB Liquidity Pools 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 |
|
|
Canonical list of liquidity pools across all supported DEXes. Each row represents a unique pool with its configuration (exchange, type, tokens, factory) and identifiers (contract address for v2/v3-style pools, pool_id for v4-style pools). |
|
|
|
|
|
This table serves as the single source of truth for pool identity; child time-series tables (reserves, swaps, yields) reference pools by their pool_uid. |
|
|
|
|
|
|
|
|
## 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: |
|
|
|
|
|
• pool_uid BYTEA – Unique pool identifier derived from address or pool_id (primary key) |
|
|
• exchange_id INTEGER – Exchange/DEX identifier |
|
|
• type_id INTEGER – Pool type identifier (FK to liquidity_pool_types) |
|
|
• block_number BIGINT – Block of the log attributed as the genesis/recognition point |
|
|
• 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 |
|
|
• factory BYTEA – 20-byte DEX factory/pool-manager address |
|
|
• tokens BYTEA[] – Array of 20-byte token addresses in the pool |
|
|
• contract_address BYTEA – 20-byte address for v2/v3-style pools (nullable for id-only v4) |
|
|
• pool_id BYTEA – 32-byte identifier for v4-style pools (nullable for v2/v3) |
|
|
• pairnum NUMERIC(6) – Pair number, if applicable |
|
|
• asset_managers BYTEA[] – Array of asset manager addresses, if applicable |
|
|
• amp NUMERIC(6) – Amplification parameter for stable pools |
|
|
• weights NUMERIC(6,5)[] – Token weights (0..1) for weighted pools |
|
|
• tick_spacing SMALLINT – Tick spacing for concentrated liquidity pools |
|
|
• _tracing_id BYTEA – Tracing ID of this pool record |
|
|
• _genesis_tracing_ids BYTEA[] – Tracing IDs of the genesis records leading to this pool record |
|
|
• _parent_tracing_ids BYTEA[] – Tracing IDs of the parent records leading to this pool record |
|
|
• _created_at TIMESTAMPTZ – Record creation timestamp |
|
|
• _updated_at TIMESTAMPTZ – Record last update timestamp |
|
|
|
|
|
|
|
|
### Notes |
|
|
• At least one of contract_address or pool_id is always populated. |
|
|
• Indexes on block_number, factory, type_id, (factory, type_id), and tokens (GIN) support fast lookups. |
|
|
• Binary values can be rendered as hex via encode(column, 'hex') in SQL for display or downstream joins. |
|
|
|
|
|
|
|
|
## Lineage |
|
|
Each pool record includes deterministic _tracing_id, _genesis_tracing_ids, and _parent_tracing_ids, providing: |
|
|
|
|
|
• Provenance tracking from raw logs to pool discovery |
|
|
• Reproducible analytics and signal extraction |
|
|
• Cross-system consistency checks (RPC vs. indexers vs. internal warehouses) |
|
|
|
|
|
|
|
|
## Common Use Cases |
|
|
• Building DEX pool registries across multiple protocols |
|
|
• Pool discovery and new listing detection |
|
|
• Foundation for swap, reserves, and yield analytics |
|
|
• Cross-DEX liquidity analysis and comparison |
|
|
|
|
|
|
|
|
## Quality |
|
|
• Verifiable lineage: deterministic cryptographic hashes per row |
|
|
• Reorg-aware ingestion: continuity and consistency across forks |
|
|
• Complete historical coverage: from chain genesis to present |
|
|
|
