RBudzynski's picture
Upload 5 files
e7edd2f verified
metadata
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