File size: 3,397 Bytes
e7edd2f | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 | ---
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 Fee Terms - Sample
size_categories:
- 10M<n<100M
---
## Sample Notice
This dataset contains **a small sample** of the full BlockDB Liquidity Pools Fee Terms 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
Versioned fee terms per liquidity pool. Each row represents a fee configuration change event, tracking total fee, user/LP fee, protocol fee, and extra fee fractions. Fee terms are non-overlapping per pool, enabling accurate historical fee reconstruction.
## 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 (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 where the new fee term starts
• 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
• total_fee NUMERIC(18,18) – Total fee fraction (e.g., 0.003 = 0.30%)
• user_fee NUMERIC(18,18) – User/LP fee fraction (same units as total_fee)
• protocol_fee NUMERIC(18,18) – Protocol fee fraction (same units as total_fee)
• extra_fee NUMERIC(18,18) – Extra fee fraction (burn/staking/etc.)
• _tracing_id BYTEA – Tracing ID of this fee terms 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
• Primary key: (pool_uid, block_number, tx_index, log_index) guarantees uniqueness per fee change event.
• Fee fractions are between 0 and 1; user_fee + protocol_fee + extra_fee ≤ 1.
• Indexes on (pool_uid, block_number DESC, tx_index DESC, log_index DESC), block_number, block_time, and total_fee support fast lookups.
## Lineage
Each fee terms record includes deterministic _tracing_id, _genesis_tracing_ids, and _parent_tracing_ids, providing:
• Provenance tracking from raw logs to decoded fee changes
• Reproducible analytics and signal extraction
• Cross-system consistency checks (RPC vs. indexers vs. internal warehouses)
## Common Use Cases
• Historical fee reconstruction for swap cost analysis
• DEX fee comparison and competitive analysis
• Protocol revenue estimation and forecasting
• Fee change event detection and alerting
## Quality
• Verifiable lineage: deterministic cryptographic hashes per row
• Reorg-aware ingestion: continuity and consistency across forks
• Complete historical coverage: from chain genesis to present
|