Liquidity Pools | Ethereum EVM Blockchain Data

**Dataset Overview**

BlockDB Liquidity Pools Registry is the central pool identity table for the entire BlockDB DeFi data stack — the single source of truth for every AMM pool discovered across Ethereum and EVM-compatible chains. Each record identifies a unique pool with its exchange, pool type, full token composition array, factory address, and protocol-specific parameters including tick spacing for concentrated liquidity pools, amplification coefficient for stable pools, and weight arrays for Balancer-style pools. It handles both address-based pools (Uniswap v2/v3, SushiSwap, PancakeSwap) and ID-based pools (Uniswap v4) in a unified schema. All BlockDB time-series tables — reserves, swap fees, prices, yields, and TVL — reference this table via POOL_UID, making it the required JOIN anchor for any multi-dataset DeFi query in Snowflake.

<p><br/></p>

**Sample Notice**

This dataset contains **a small sample** of the full BlockDB Liquidity Pools Registry 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 via contact form on Snowflake Marketplace.

<p><br/></p>

**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.

<p><br/></p>

**Join Keys**

POOL_UID serves as the universal primary key for each liquidity pool. It is used as a foreign key across all affiliated tables - such as reserves, swaps, fees, prices, and yields - ensuring consistent identification and efficient JOINs for any DeFi analytics involving liquidity pools.

<p><br/></p>

**Lineage**

Each pool record includes deterministic _TRACING_ID and _PARENT_TRACING_IDS, providing verifiable provenance from the raw log where the pool was first discovered through to the decoded configuration stored here.

<p><br/></p>

**Quality**

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

原始信息汇总

Liquidity Pools | Ethereum EVM Blockchain Data 数据集概述

数据集基本信息

• 数据集名称: BlockDB Liquidity Pools Registry
• 提供商: BlockDB
• 访问模式: 免费试用
• 试用状态: 可用

数据集概述

BlockDB Liquidity Pools Registry 是整个 BlockDB DeFi 数据堆栈的中心池身份表，是跨以太坊和 EVM 兼容链发现的每个 AMM 池的唯一真实来源。每条记录都标识一个唯一的池，包含其交易所、池类型、完整的代币组成数组、工厂地址以及协议特定参数（包括集中流动性池的刻度间距、稳定池的放大系数以及 Balancer 式池的权重数组）。它在一个统一的模式中处理基于地址的池（Uniswap v2/v3、SushiSwap、PancakeSwap）和基于 ID 的池（Uniswap v4）。所有 BlockDB 时间序列表（储备金、交换费、价格、收益率和 TVL）都通过 POOL_UID 引用此表，使其成为 Snowflake 中任何多数据集 DeFi 查询所需的 JOIN 锚点。

样本说明

此数据集包含完整 BlockDB Liquidity Pools Registry 数据集的一个小样本。仅用于评估、研究和互操作性测试。如果需要完整的历史覆盖范围、实时流或日终导出，请通过 Snowflake Marketplace 上的联系表联系我们。

链和覆盖范围

ETH、BSC、Base、Arbitrum、Unichain、Avalanche、Polygon、Celo、Linea、Optimism（其他链可根据要求提供）。从链创世开始的完整历史记录；支持重组感知的实时摄取和更新。

连接键

POOL_UID 作为每个流动性池的通用主键。它在所有关联表（如储备金、交换、费用、价格和收益率）中用作外键，确保在涉及流动性池的任何 DeFi 分析中实现一致的标识和高效的 JOIN 操作。

数据血缘

每条池记录都包含确定性的 _TRACING_ID 和 _PARENT_TRACING_IDS，提供从首次发现池的原始日志到此处存储的解码配置的可验证来源。

数据质量

• 可验证的血缘：每行具有确定性的加密哈希值
• 重组感知的摄取：跨分叉的连续性和一致性
• 完整的历史覆盖：从链创世到现在

业务需求

区块链分析

• 构建跨 DEX 的池注册表，用于路由、分析和流动性监控
• 按协议、费用层级或代币对筛选池以进行针对性分析
• 跨储备金、交换、价格、收益率和 TVL 进行 JOIN 查询的锚表
• 跨所有支持链的池发现和新上市检测管道
• 协议市场份额分析和竞争性 DeFi 生态系统情报

数据字典

数据集名称: BLOCKDB0211_LIQUIDITY_POOLS_V1 数据集描述: Dataset 0211 — On-chain AMM pools (addressing, type IDs, fee tiers)

列信息

• POOL_UID (Binary)
• EXCHANGE_ID (Number)
• TYPE_ID (Number)
• BLOCK_NUMBER (Number)
• BLOCK_TIME (Timestamp_TZ)
• TX_INDEX (Number)
• LOG_INDEX (Number)
• FACTORY (Binary)
• TOKENS (Array)
• CONTRACT_ID (Binary)
• CONTRACT_ADDRESS (Binary)
• POOL_ID (Binary)
• PAIRNUM (Number)
• ASSET_MANAGERS (Array)
• AMP (Number)
• WEIGHTS (Array)
• TICK_SPACING (Number)
• _TRACING_ID (Binary)
• _PARENT_TRACING_IDS (Array)
• _CREATED_AT (Timestamp_TZ)
• _UPDATED_AT (Timestamp_TZ)

使用示例

按交易所和池类型统计活跃池数量

sql SELECT exchange_id, type_id, COUNT(*) AS pool_count, MIN(block_time) AS first_pool_created, MAX(block_time) AS latest_pool_created FROM PUBLIC.BLOCKDB0211_LIQUIDITY_POOLS_V1 GROUP BY 1, 2 ORDER BY pool_count DESC;

其他相关信息

• 刷新频率: 静态数据产品
• 云区域可用性: AWS（非洲（开普敦）、亚太（雅加达）、亚太（马来西亚）、亚太（孟买）等）
• 法律条款: 标准条款