https://algotrading101.com/learn/wp-content/uploads/2020/06/yahoo-finance-api-guide.png">

This dataset contains real-time prices of various cryptocurrencies that are listed on Yahoo Finance. The data has been collected from Yahoo Finance API and consists of 9,600 rows of data.

Crypto Data Platform Market Outlook

According to our latest research, the global Crypto Data Platform market size reached USD 1.85 billion in 2024, reflecting robust adoption across institutional and retail segments. The market is expected to expand at a CAGR of 18.2% during the forecast period, with revenues projected to reach USD 9.25 billion by 2033. This growth is primarily fueled by the increasing demand for real-time data analytics, advanced trading solutions, and regulatory compliance tools in the rapidly evolving cryptocurrency industry. The surge in digital asset adoption, coupled with heightened institutional participation and technological advancements, is driving the need for comprehensive, scalable, and secure crypto data platforms worldwide.

A significant growth factor for the Crypto Data Platform market is the exponential rise in crypto trading volumes and the proliferation of digital assets. As institutional investors, hedge funds, and family offices continue to increase their exposure to cryptocurrencies, the requirement for accurate, timely, and actionable data has become paramount. Crypto data platforms are now pivotal in providing market participants with historical and real-time price feeds, blockchain analytics, on-chain indicators, and sentiment analysis. These platforms also enable seamless integration with trading systems and portfolio management tools, empowering users to make informed investment decisions. The ongoing innovation in decentralized finance (DeFi) and the emergence of new digital asset classes further intensify the demand for robust data solutions, positioning crypto data platforms as a critical infrastructure layer in the digital economy.

Another key driver is the growing emphasis on regulatory compliance and risk management across the crypto ecosystem. As governments and regulatory bodies worldwide introduce stricter frameworks for anti-money laundering (AML), know-your-customer (KYC), and market surveillance, enterprises and exchanges are increasingly leveraging crypto data platforms to ensure adherence to these mandates. These platforms offer advanced compliance modules, transaction monitoring, and risk analytics, enabling stakeholders to mitigate operational and reputational risks. The integration of artificial intelligence (AI) and machine learning (ML) into these solutions further enhances their capability to detect anomalies, prevent fraud, and deliver predictive insights, thereby fostering trust and transparency in the market.

The rapid advancement in cloud computing, API-driven architectures, and interoperability standards is also propelling the Crypto Data Platform market forward. As digital asset markets operate around the clock and across geographies, there is a pressing need for scalable, resilient, and highly available data infrastructure. Cloud-based deployment models facilitate seamless access to vast datasets, while API integrations enable real-time connectivity with trading platforms, wallets, and external data sources. This technological evolution is enabling both established financial institutions and emerging fintech startups to harness the power of crypto data without significant upfront investments in hardware or IT resources. As a result, the market is witnessing accelerated product innovation, ecosystem collaboration, and the entry of new players offering specialized data services.

Regionally, North America continues to dominate the Crypto Data Platform market, accounting for the largest revenue share in 2024. The region’s leadership is underpinned by the presence of major crypto exchanges, institutional investors, and a mature regulatory landscape. Europe and Asia Pacific are also witnessing rapid adoption, driven by progressive regulatory initiatives, growing fintech ecosystems, and increasing retail investor participation. Latin America and the Middle East & Africa are emerging as promising markets, supported by rising digital asset adoption and government-led blockchain initiatives. However, regional disparities in regulatory clarity, technological infrastructure, and capital market maturity present both opportunities and challenges for market participants.

Component Analysis

The Crypto Data Platform market by component is segmented into Solutions and Services, each playing a vital role in the industry’s value chain. Solutions encompass the core software platforms that aggregate, normali

🚀 Title: One-Hour High-Frequency Crypto Snapshot – Top 250 Coins, ~75K Ticks

📝 Overview

This dataset captures live market snapshots every 12 seconds for the top 250 cryptocurrencies, all fetched over a one-hour period using the CoinGecko Demo API. Perfect for real-time trend tracking, volatility analysis, and comparison across major coins.

📊 Schema Summary

🎯 Use Cases

• Visualize real-time price evolution for Bitcoin, Ethereum, and other major coins
• Compute rolling averages and short-term volatility
• Perform coin-to-coin comparisons (price dynamics, volume trends)
• Explore volume-price correlations, and flag anomaly detection
• Build heatmaps, live dashboards, or time-series models

📌 Attribution & Licensing

Data collected via CoinGecko API—**Data powered by CoinGecko**

🟦 What this is Canonical ERC-20 token reference with deterministic tracing at the row level. One row per token contract, with audit-grade lineage to the first recognition event and to parent/genesis derivations. • Schema-stable, versioned, audit-ready • Historical + real-time options

🌐 Chains / 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 the columns exactly as delivered. Keep names/types consistent with files. • contract_address BYTEA - PK; 20-byte ERC-20 contract address • tracing_id BYTEA - deterministic row-level hash (proof-of-derivation) • parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph • genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path) • genesis_block_number BIGINT - first block where the token was recognized • genesis_tx_index INTEGER - tx index for that event • genesis_log_index INTEGER - log index for that event • name TEXT - ERC-20 name() • symbol TEXT - ERC-20 symbol() • decimals SMALLINT - ERC-20 decimals()

Notes • Use encode(contract_address,'hex') for hex presentation. • Metadata (name, symbol, decimals) is populated from ABI reads. • If the ABI read was unsuccessful, the token is not present in this table (columns are NOT NULL by design).

🔑 Keys & Joins • Primary key: contract_address • Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Token registry to normalize joins for swaps, transfers, pools, and prices • Amount scaling via decimals for analytics, PnL, and model features • App backends: display names/symbols and validate token addresses

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage). Optional • Integrations to Amazon S3, Azure Blob Storage, Snowflake, and other enterprise platforms on request.

🗂️ Files (time-partitioned in UTC, compressed) • Parquet • CSV • XLS • JSON

💡 Quality and operations • Reorg-aware ingestion. • 99.95% uptime SLA. • Backfills to chain genesis. • Versioned, schema-stable datasets; changes are additive and announced.

🔄 Change policy Schema is stable. Any breaking change ships as a new version (e.g., erc20_tokens_v2) with migration notes. Content updates are additive (new rows/fields filled); types aren’t changed in place.

Context

This data set is generated by the help of Binance Api.

What is Binance Api? The Binance API is a method that allows you to connect to the Binance servers via Python or several other programming languages. With it, you can automate your trading.

More specifically, Binance has a RESTful API that uses HTTP requests to send and receive data. Further, there is also a WebSocket available that enables the streaming of data such as price quotes and account updates.

Content

In this data set the data is generated on the interval of 1 minute by an API. It includes many columns showing the real change in price of Bitcoin also shows the Open, High, Low, Close price of Bitcoin on particular minutes. The Open Time and Close Time in the data set are in Unix Timestamp.

Acknowledgements

Special thanks to Binance Stream Data Api.

🟦 What this is Canonical registry of all verified Aerodrome Slipstream liquidity pools, normalized into the BlockDB schema for deterministic cross-chain analysis. Fees are modeled separately as versioned terms, so fee changes over time are tracked precisely and are joinable back to the pool.

This dataset provides the structural backbone for connecting Aerodrome Slipstream pool states with liquidity, price, and swap datasets.

Key traits • Schema-stable, versioned, and lineage-verifiable • Deterministic pool UIDs across chains and factory contracts • Real-time and historical coverage with factory-level lineage • Fully joinable with reserves, prices, swaps, and fee-term timelines

🌐 Chains / Coverage ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request). Full backfill to chain genesis with reorg-aware real-time ingestion. Covers all verified Aerodrome Slipstream deployments across supported EVM networks.

📑 Schema List the columns exactly as delivered. Names/types are stable.

liquidity_pools (base registry) • uid BIGINT NOT NULL - stable pool identifier (derived from address or pool_id) • tracing_id BYTEA - deterministic row-level hash (proof-of-derivation) • parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph • genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path) • genesis_block_number BIGINT NOT NULL - factory create event block • genesis_tx_index INTEGER NOT NULL - create event tx index • genesis_log_index INTEGER NOT NULL - create event log index • contract_address BYTEA NULL - 20-byte pool address (v2/v3-style) • pool_id BYTEA NULL - 32-byte pool id (v4-style / manager-based) • factory BYTEA NOT NULL - DEX factory / pool manager address • type_id INTEGER NOT NULL - pool type FK (constant-product, concentrated, stable/weighted, etc.) • pairnum NUMERIC(6) NULL - optional pair ordinal/descriptor • tokens BYTEA[] NOT NULL - array of 20-byte token addresses (order matches protocol convention) • asset_managers BYTEA[] NULL - per-token managers (e.g., Balancer) • amp NUMERIC(6) NULL - amplification for stable/weighted math • pool_type TEXT NULL - optional human-readable type label • weights NUMERIC(6,5)[] NULL - per-token weights in 0..1 (5 dp) • tick_spacing SMALLINT NULL - grid size for concentrated liquidity

liquidity_pool_fee_terms (versioned, non-overlapping) • pool_uid BIGINT NOT NULL - FK → liquidity_pools(uid) • tracing_id BYTEA - Row identity hash (proof-of-derivation) • parent_tracing_ids BYTEA - Salted hashes of contributing parents • genesis_tracing_ids BYTEA - Salted hashes of ultimate sources • genesis_block_number BIGINT NOT NULL - Fee-update event block • genesis_block_time TIMESTAMPZ NOT NULL - Fee-update event timestamp • genesis_tx_index INTEGER NOT NULL - Transaction index • genesis_log_index INTEGER NOT NULL - Log index • pool_fee NUMERIC(18,18) NOT NULL - Total fee fraction (e.g. 0.003 = 0.30 %) • user_fee_bps SMALLINT NULL - Optional user-side fee share (0–10 000) • protocol_fee_bps SMALLINT NULL - Optional protocol-side fee share (0–10 000) • fee_source TEXT NOT NULL - Provenance of fee rate (e.g. onchain:event) • fee_share_source TEXT NOT NULL - Provenance of fee split (e.g. onchain:param, docs)

Checks • At least one identifier present (contract_address or pool_id) and lengths enforced (20B/32B).

Notes • Fee terms are non-overlapping; each record defines a valid block-range. • Use liquidity_pool_fee_terms for historical fee reconstruction or to obtain the active fee at a given block.

🔑 Keys & joins • Primary key: uid • Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index) • Foreign keys: • (genesis_block_number, genesis_tx_index, genesis_log_index) → logs(block_number, tx_index, log_index) • factory → decentralized_exchanges(contract_address) • type_id → liquidity_pool_types(id)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Building the complete pool registry for routing and analytics • Filtering pools by fee, type, or token pair • Integrating with reserves, price, and swap datasets for liquidity intelligence • MEV routing, arbitrage path optimization, and chain-wide pool analytics • Constructing pool-level AI or quantitative features

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, line...

Crypto-Native Payroll Market Outlook

According to our latest research, the global crypto-native payroll market size in 2024 reached USD 1.14 billion, reflecting a robust adoption curve across diverse industries. The market is expected to grow at a CAGR of 22.7% from 2025 to 2033, reaching an anticipated value of USD 8.41 billion by 2033. This impressive growth trajectory is primarily driven by the increasing acceptance of cryptocurrencies as legitimate payment instruments, the demand for borderless payroll solutions, and the proliferation of blockchain-enabled financial services. As per our latest research, the market is witnessing a surge in both enterprise and SME adoption, underpinned by the promise of faster settlements, reduced transaction costs, and enhanced transparency.

One of the primary growth factors for the crypto-native payroll market is the growing globalization of the workforce. With remote and distributed teams becoming the norm, especially in the IT and digital services sectors, traditional payroll systems often struggle with cross-border payments, compliance, and currency conversion complexities. Crypto-native payroll solutions offer seamless, real-time, and cost-effective remuneration options that bypass conventional banking channels, making them particularly attractive to companies with multinational operations. This shift is further supported by the increasing regulatory clarity in major economies, which is encouraging organizations to explore cryptocurrency-based payroll as a viable and compliant alternative.

Another significant driver is the rise of stablecoins and programmable payments, which have addressed many of the volatility and operational risks previously associated with cryptocurrency compensation. Stablecoins, pegged to fiat currencies, offer the stability required for payroll operations, while smart contract-based solutions enable automated, auditable, and conditional payments. This technological evolution is empowering both employers and employees to customize payment schedules, split payments across multiple currencies, and integrate payroll with decentralized finance (DeFi) platforms for additional financial services. The integration of such features is accelerating the adoption of crypto-native payroll, especially among tech-savvy and innovation-driven enterprises.

Additionally, the competitive landscape and the need for talent acquisition in high-growth sectors are pushing organizations to offer crypto-based payroll as a differentiator. Employees, particularly in the technology, blockchain, and creative industries, are increasingly seeking compensation in cryptocurrencies for reasons such as investment potential, financial autonomy, and ease of cross-border transactions. This trend is compelling companies to adopt crypto-native payroll solutions to attract and retain top talent, thereby fueling market expansion. Furthermore, the enhanced security, transparency, and traceability provided by blockchain technology are addressing concerns around fraud, compliance, and auditability, making crypto-native payroll solutions more appealing to enterprises of all sizes.

The integration of Payroll API solutions is becoming increasingly significant in the crypto-native payroll market. These APIs facilitate seamless communication between payroll systems and other financial platforms, enhancing the efficiency and accuracy of payroll processing. By leveraging Payroll API, organizations can automate data exchange, reduce manual errors, and ensure real-time updates across their financial systems. This capability is particularly beneficial for companies operating in multiple jurisdictions, as it simplifies compliance with diverse regulatory requirements and streamlines cross-border transactions. As the demand for integrated financial solutions grows, Payroll API is poised to play a crucial role in the evolution of crypto-native payroll systems, offering organizations a competitive edge in managing their payroll operations.

From a regional perspective, North America currently leads the crypto-native payroll market, accounting for the largest share due to early regulatory advancements, high digital literacy, and the presence of major blockchain innovators. Europe follows closely, driven by progressive regulatory frameworks and the rapid digitization of finan

🟦 What this is Canonical registry of all DEX liquidity pools, normalized into the BlockDB schema for deterministic cross-chain analysis. Fees are modeled separately as versioned terms, so fee changes over time are tracked precisely and are joinable back to the pool.

Key traits • Schema-stable, versioned, and lineage-verifiable • Deterministic pool UIDs across chains and factory contracts • Real-time and historical coverage with factory-level lineage • Fully joinable with reserves, prices, swaps, and fee-term timelines

🌐 Chains / 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. Coverage includes: • Uniswap V2, V3, V4 • Balancer V2, PancakeSwap, Solidly, Maverick, Aerodrome, and others

📑 Schema List the columns exactly as delivered. Names/types are stable.

liquidity_pools (base registry) • uid BIGINT NOT NULL - stable pool identifier (derived from address or pool_id) • tracing_id BYTEA - deterministic row-level hash (proof-of-derivation) • parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph • genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path) • genesis_block_number BIGINT NOT NULL - factory create event block • genesis_tx_index INTEGER NOT NULL - create event tx index • genesis_log_index INTEGER NOT NULL - create event log index • contract_address BYTEA NULL - 20-byte pool address (v2/v3-style) • pool_id BYTEA NULL - 32-byte pool id (v4-style / manager-based) • factory BYTEA NOT NULL - DEX factory / pool manager address • type_id INTEGER NOT NULL - pool type FK (constant-product, concentrated, stable/weighted, etc.) • pairnum NUMERIC(6) NULL - optional pair ordinal/descriptor • tokens BYTEA[] NOT NULL - array of 20-byte token addresses (order matches protocol convention) • asset_managers BYTEA[] NULL - per-token managers (e.g., Balancer) • amp NUMERIC(6) NULL - amplification for stable/weighted math • pool_type TEXT NULL - optional human-readable type label • weights NUMERIC(6,5)[] NULL - per-token weights in 0..1 (5 dp) • tick_spacing SMALLINT NULL - grid size for concentrated liquidity

liquidity_pool_fee_terms (versioned, non-overlapping) • pool_uid BIGINT NOT NULL - FK → liquidity_pools(uid) • tracing_id BYTEA - Row identity hash (proof-of-derivation) • parent_tracing_ids BYTEA - Salted hashes of contributing parents • genesis_tracing_ids BYTEA - Salted hashes of ultimate sources • genesis_block_number BIGINT NOT NULL - Fee-update event block • genesis_block_time TIMESTAMPZ NOT NULL - Fee-update event timestamp • genesis_tx_index INTEGER NOT NULL - Transaction index • genesis_log_index INTEGER NOT NULL - Log index • pool_fee NUMERIC(18,18) NOT NULL - Total fee fraction (e.g. 0.003 = 0.30 %) • user_fee_bps SMALLINT NULL - Optional user-side fee share (0–10 000) • protocol_fee_bps SMALLINT NULL - Optional protocol-side fee share (0–10 000) • fee_source TEXT NOT NULL - Provenance of fee rate (e.g. onchain:event) • fee_share_source TEXT NOT NULL - Provenance of fee split (e.g. onchain:param, docs)

Checks • At least one identifier present (contract_address or pool_id) and lengths enforced (20B/32B).

Notes • Fee terms are non-overlapping; each record defines a valid block-range. • Use liquidity_pool_fee_terms for historical fee reconstruction or to obtain the active fee at a given block.

🔑 Keys & joins • Primary key: uid • Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index) • Foreign keys: • (genesis_block_number, genesis_tx_index, genesis_log_index) → logs(block_number, tx_index, log_index) • factory → decentralized_exchanges(contract_address) • type_id → liquidity_pool_types(id)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Building the complete DEX pool registry for routing and analytics • Filtering pools by fee, type, or token pair • Integrating with reserves, price, and swap datasets for liquidity intelligence • MEV routing, arbitrage path optimization, and chain-wide pool analytics • Constructing pool-level AI or quantitative features

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage). Optional • Integrations to Amazon S3, Azure Blob Storage, Snowflake, and other enterprise platforms on request.

...

🟦 What this is Canonical registry of all verified Aerodrome V1 liquidity pools, normalized into the BlockDB schema for deterministic cross-chain analysis. Fees are modeled separately as versioned terms, so fee changes over time are tracked precisely and are joinable back to the pool.

This dataset provides the structural backbone for connecting Aerodrome V1 pool states with liquidity, price, and swap datasets.

Key traits: • Schema-stable, versioned, and lineage-verifiable • Deterministic pool UIDs across chains and factory contracts • Real-time and historical coverage with factory-level lineage • Fully joinable with reserves, prices, swaps, and fee-term timelines

🌐 Chains / Coverage ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request). Full backfill to chain genesis with reorg-aware real-time ingestion. Covers all verified Aerodrome V1 deployments across supported EVM networks.

📑 Schema List the columns exactly as delivered. Names/types are stable.

liquidity_pools (base registry) • uid BIGINT NOT NULL - stable pool identifier (derived from address or pool_id) • tracing_id BYTEA - deterministic row-level hash (proof-of-derivation) • parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph • genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path) • genesis_block_number BIGINT NOT NULL - factory create event block • genesis_tx_index INTEGER NOT NULL - create event tx index • genesis_log_index INTEGER NOT NULL - create event log index • contract_address BYTEA NULL - 20-byte pool address (v2/v3-style) • pool_id BYTEA NULL - 32-byte pool id (v4-style / manager-based) • factory BYTEA NOT NULL - DEX factory / pool manager address • type_id INTEGER NOT NULL - pool type FK (constant-product, concentrated, stable/weighted, etc.) • pairnum NUMERIC(6) NULL - optional pair ordinal/descriptor • tokens BYTEA[] NOT NULL - array of 20-byte token addresses (order matches protocol convention) • asset_managers BYTEA[] NULL - per-token managers (e.g., Balancer) • amp NUMERIC(6) NULL - amplification for stable/weighted math • pool_type TEXT NULL - optional human-readable type label • weights NUMERIC(6,5)[] NULL - per-token weights in 0..1 (5 dp) • tick_spacing SMALLINT NULL - grid size for concentrated liquidity

liquidity_pool_fee_terms (versioned, non-overlapping) • pool_uid BIGINT NOT NULL - FK → liquidity_pools(uid) • tracing_id BYTEA - Row identity hash (proof-of-derivation) • parent_tracing_ids BYTEA - Salted hashes of contributing parents • genesis_tracing_ids BYTEA - Salted hashes of ultimate sources • genesis_block_number BIGINT NOT NULL - Fee-update event block • genesis_block_time TIMESTAMPZ NOT NULL - Fee-update event timestamp • genesis_tx_index INTEGER NOT NULL - Transaction index • genesis_log_index INTEGER NOT NULL - Log index • pool_fee NUMERIC(18,18) NOT NULL - Total fee fraction (e.g. 0.003 = 0.30 %) • user_fee_bps SMALLINT NULL - Optional user-side fee share (0–10 000) • protocol_fee_bps SMALLINT NULL - Optional protocol-side fee share (0–10 000) • fee_source TEXT NOT NULL - Provenance of fee rate (e.g. onchain:event) • fee_share_source TEXT NOT NULL - Provenance of fee split (e.g. onchain:param, docs)

Checks • At least one identifier present (contract_address or pool_id) and lengths enforced (20B/32B).

Notes • Fee terms are non-overlapping; each record defines a valid block-range. • Use liquidity_pool_fee_terms for historical fee reconstruction or to obtain the active fee at a given block.

🔑 Keys & joins • Primary key: uid • Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index) • Foreign keys: • (genesis_block_number, genesis_tx_index, genesis_log_index) → logs(block_number, tx_index, log_index) • factory → decentralized_exchanges(contract_address) • type_id → liquidity_pool_types(id)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Building the complete pool registry for routing and analytics • Filtering pools by fee, type, or token pair • Integrating with reserves, price, and swap datasets for liquidity intelligence • MEV routing, arbitrage path optimization, and chain-wide pool analytics • Constructing pool-level AI or quantitative features

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage). Optional • Int...

🟦 What this is Canonical ERC-721 NFT collection reference with deterministic tracing at the row level. One row per deployed NFT contract, providing audit-grade lineage to the first recognition event and parent/genesis derivations.

Key traits • Schema-stable, versioned, and audit-ready • Historical + real-time ingestion from chain genesis • Verified on-chain metadata (name, symbol) from contract ABI reads

🌐 Chains / 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 the columns exactly as delivered. Keep names/types consistent with files. • contract_address BYTEA - PK; 20-byte ERC-20 contract address • tracing_id BYTEA - deterministic row-level hash (proof-of-derivation) • parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph • genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path) • genesis_block_number BIGINT - first block where the token was recognized • genesis_tx_index INTEGER - tx index for that event • genesis_log_index INTEGER - log index for that event • name TEXT - NFT collection name (from ABI call name()) • symbol TEXT - NFT symbol (from ABI call symbol()) • base_token_uri TEXT NULL - Base token URI (from ABI call baseTokenURI())

Notes • Use encode(contract_address,'hex') for hex presentation. • Metadata is obtained deterministically via ABI calls; records are included only when both name and symbol are successfully decoded. • Additional token-level data (e.g. token_id, token_uri) are stored in dependent tables such as erc721_items.

🔑 Keys & Joins • Primary key: contract_address • Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Token registry to normalize joins for swaps, transfers, pools, and prices • Amount scaling via decimals for analytics, PnL, and model features • App backends: display names/symbols and validate token addresses

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage). Optional • Integrations to Amazon S3, Azure Blob Storage, Snowflake, and other enterprise platforms on request.

🗂️ Files (time-partitioned in UTC, compressed) • Parquet • CSV • XLS • JSON

💡 Quality and operations • Reorg-aware ingestion. • 99.95% uptime target SLA. • Backfills to chain genesis. • Versioned, schema-stable datasets; changes are additive and announced.

🔄 Change policy Schema is stable. Any breaking change ships as a new version (e.g., erc721_tokens_v2) with migration notes. Content updates are additive (new rows/fields filled); types aren’t changed in place.

Snapshot img

E-Wallet Market Size 2025-2029

The E-wallet market size is forecast to increase by USD 169.86 billion at a CAGR of 21.9% between 2024 and 2029.

The market is experiencing significant growth, driven by the increasing number of online transactions. This trend is fueled by the convenience and accessibility of digital wallets, which enable users to make payments quickly and securely. Moreover, the integration of advanced technologies such as artificial intelligence, blockchain, and biometrics is enhancing the functionality and security of these wallets, further boosting their adoption. However, the market faces challenges, including high infrastructure and implementation costs. Blockchain technology and cryptocurrency payments offer new possibilities for transactions.
Additionally, they should focus on offering value-added services and building customer trust through robust security measures. Blockchain technology ensures secure and transparent financial transactions, while AI is utilized for enhanced fraud detection and prevention. By addressing these challenges and leveraging technological advancements, players in the market can seize opportunities and maintain a competitive edge. These expenses can hinder the expansion of E-Wallet services, particularly in emerging markets where financial infrastructure is less developed. Companies seeking to capitalize on market opportunities must navigate these challenges effectively by optimizing costs and exploring partnerships to share infrastructure and resources.

What will be the Size of the E-Wallet Market during the forecast period?

Explore in-depth regional segment analysis with market size data - historical 2019-2023 and forecasts 2025-2029 - in the full report.
Request Free Sample

In the dynamic market, payment processing and user experience are key differentiators. Financial technology companies continually enhance user interfaces to facilitate seamless digital payments. Customer acquisition strategies, including KYC regulations and loyalty programs, are essential for market penetration. Mobile wallet features, such as real-time payments, in-app purchases, and merchant services, cater to the growing demand for mobile commerce. Payment security and fraud prevention are critical concerns, with advanced authentication methods, API integration, and transaction tracking ensuring data encryption and compliance with security protocols. Financial services providers prioritize transaction speed, account management, and transaction history to meet business needs.

Transaction fees and payment infrastructure are significant factors in the market. Real-time payment processing and merchant services enable faster transaction settlements, while API integration and compliance with financial technology standards streamline business operations. As digital wallet apps continue to gain popularity, customer support and account management become essential components of a successful e-wallet offering. Payment gateway APIs and transaction tracking enable businesses to monitor and manage their financial transactions effectively. Contactless payments, for instance, enable seamless transactions through near field communication technology.

How is this E-Wallet Industry segmented?

The E-wallet industry research report provides comprehensive data (region-wise segment analysis), with forecasts and estimates in 'USD million' for the period 2025-2029, as well as historical data from 2019-2023 for the following segments.

Technology

  Proximity
  Remote


Application

  Retail and e-commerce
  Media and entertainment
  Hospitality and transportation
  Telecommunication
  Others


Type

  Semi-closed wallets
  Open wallets
  Closed wallets


Geography

  North America

    US
    Canada


  Europe

    Germany
    UK


  APAC

    China
    India
    Indonesia
    Japan
    South Korea


  South America

    Brazil


  Rest of World (ROW)

By Technology Insights

The Proximity segment is estimated to witness significant growth during the forecast period. The market is witnessing significant growth as users increasingly prefer contactless and convenient digital payment solutions. Proximity technology, which enables near-field communication (NFC) and other wireless transactions, dominates the market due to its ability to offer quick and secure payments through wearables or mobile devices. This technology is widely adopted across various sectors, including retail, transportation, and hospitality, providing greater convenience and security compared to traditional payment methods. Transaction fees, integration APIs, merchant services, virtual cards, data analytics, cash management, payment gateways, and payment processors are all key components of this dynamic landscape.

User account management is crucial in the market, ensuring secure access and transaction authorization through two-factor auth

🟦 What this is Canonical registry of all verified PancakeSwap V2 liquidity pools, normalized into the BlockDB schema for deterministic cross-chain analysis. Fees are modeled separately as versioned terms, so fee changes over time are tracked precisely and are joinable back to the pool.

This dataset provides the structural backbone for connecting PancakeSwap V2 pool states with liquidity, price, and swap datasets.

Key traits • Schema-stable, versioned, and lineage-verifiable • Deterministic pool UIDs across chains and factory contracts • Real-time and historical coverage with factory-level lineage • Fully joinable with reserves, prices, swaps, and fee-term timelines

🌐 Chains / Coverage ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request). Full backfill to chain genesis with reorg-aware real-time ingestion. Covers all verified PancakeSwap V2 deployments across supported EVM networks.

📑 Schema List the columns exactly as delivered. Names/types are stable.

liquidity_pools (base registry) • uid BIGINT NOT NULL - stable pool identifier (derived from address or pool_id) • tracing_id BYTEA - deterministic row-level hash (proof-of-derivation) • parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph • genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path) • genesis_block_number BIGINT NOT NULL - factory create event block • genesis_tx_index INTEGER NOT NULL - create event tx index • genesis_log_index INTEGER NOT NULL - create event log index • contract_address BYTEA NULL - 20-byte pool address (v2/v3-style) • pool_id BYTEA NULL - 32-byte pool id (v4-style / manager-based) • factory BYTEA NOT NULL - DEX factory / pool manager address • type_id INTEGER NOT NULL - pool type FK (constant-product, concentrated, stable/weighted, etc.) • pairnum NUMERIC(6) NULL - optional pair ordinal/descriptor • tokens BYTEA[] NOT NULL - array of 20-byte token addresses (order matches protocol convention) • asset_managers BYTEA[] NULL - per-token managers (e.g., Balancer) • amp NUMERIC(6) NULL - amplification for stable/weighted math • pool_type TEXT NULL - optional human-readable type label • weights NUMERIC(6,5)[] NULL - per-token weights in 0..1 (5 dp) • tick_spacing SMALLINT NULL - grid size for concentrated liquidity

liquidity_pool_fee_terms (versioned, non-overlapping) • pool_uid BIGINT NOT NULL - FK → liquidity_pools(uid) • tracing_id BYTEA - Row identity hash (proof-of-derivation) • parent_tracing_ids BYTEA - Salted hashes of contributing parents • genesis_tracing_ids BYTEA - Salted hashes of ultimate sources • genesis_block_number BIGINT NOT NULL - Fee-update event block • genesis_block_time TIMESTAMPZ NOT NULL - Fee-update event timestamp • genesis_tx_index INTEGER NOT NULL - Transaction index • genesis_log_index INTEGER NOT NULL - Log index • pool_fee NUMERIC(18,18) NOT NULL - Total fee fraction (e.g. 0.003 = 0.30 %) • user_fee_bps SMALLINT NULL - Optional user-side fee share (0–10 000) • protocol_fee_bps SMALLINT NULL - Optional protocol-side fee share (0–10 000) • fee_source TEXT NOT NULL - Provenance of fee rate (e.g. onchain:event) • fee_share_source TEXT NOT NULL - Provenance of fee split (e.g. onchain:param, docs)

Checks • At least one identifier present (contract_address or pool_id) and lengths enforced (20B/32B).

Notes • Fee terms are non-overlapping; each record defines a valid block-range. • Use liquidity_pool_fee_terms for historical fee reconstruction or to obtain the active fee at a given block.

🔑 Keys & joins • Primary key: uid • Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index) • Foreign keys: • (genesis_block_number, genesis_tx_index, genesis_log_index) → logs(block_number, tx_index, log_index) • factory → decentralized_exchanges(contract_address) • type_id → liquidity_pool_types(id)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Building the complete pool registry for routing and analytics • Filtering pools by fee, type, or token pair • Integrating with reserves, price, and swap datasets for liquidity intelligence • MEV routing, arbitrage path optimization, and chain-wide pool analytics • Constructing pool-level AI or quantitative features

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage). Optional ...

🟦 What this is Canonical registry of all verified PancakeSwap V3 liquidity pools, normalized into the BlockDB schema for deterministic cross-chain analysis. Fees are modeled separately as versioned terms, so fee changes over time are tracked precisely and are joinable back to the pool.

This dataset provides the structural backbone for connecting PancakeSwap V3 pool states with liquidity, price, and swap datasets.

Key traits • Schema-stable, versioned, and lineage-verifiable • Deterministic pool UIDs across chains and factory contracts • Real-time and historical coverage with factory-level lineage • Fully joinable with reserves, prices, swaps, and fee-term timelines

🌐 Chains / Coverage ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request). Full backfill to chain genesis with reorg-aware real-time ingestion. Covers all verified PancakeSwap V3 deployments across supported EVM networks.

📑 Schema List the columns exactly as delivered. Names/types are stable.

liquidity_pools (base registry) • uid BIGINT NOT NULL - stable pool identifier (derived from address or pool_id) • tracing_id BYTEA - deterministic row-level hash (proof-of-derivation) • parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph • genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path) • genesis_block_number BIGINT NOT NULL - factory create event block • genesis_tx_index INTEGER NOT NULL - create event tx index • genesis_log_index INTEGER NOT NULL - create event log index • contract_address BYTEA NULL - 20-byte pool address (v2/v3-style) • pool_id BYTEA NULL - 32-byte pool id (v4-style / manager-based) • factory BYTEA NOT NULL - DEX factory / pool manager address • type_id INTEGER NOT NULL - pool type FK (constant-product, concentrated, stable/weighted, etc.) • pairnum NUMERIC(6) NULL - optional pair ordinal/descriptor • tokens BYTEA[] NOT NULL - array of 20-byte token addresses (order matches protocol convention) • asset_managers BYTEA[] NULL - per-token managers (e.g., Balancer) • amp NUMERIC(6) NULL - amplification for stable/weighted math • pool_type TEXT NULL - optional human-readable type label • weights NUMERIC(6,5)[] NULL - per-token weights in 0..1 (5 dp) • tick_spacing SMALLINT NULL - grid size for concentrated liquidity

liquidity_pool_fee_terms (versioned, non-overlapping) • pool_uid BIGINT NOT NULL - FK → liquidity_pools(uid) • tracing_id BYTEA - Row identity hash (proof-of-derivation) • parent_tracing_ids BYTEA - Salted hashes of contributing parents • genesis_tracing_ids BYTEA - Salted hashes of ultimate sources • genesis_block_number BIGINT NOT NULL - Fee-update event block • genesis_block_time TIMESTAMPZ NOT NULL - Fee-update event timestamp • genesis_tx_index INTEGER NOT NULL - Transaction index • genesis_log_index INTEGER NOT NULL - Log index • pool_fee NUMERIC(18,18) NOT NULL - Total fee fraction (e.g. 0.003 = 0.30 %) • user_fee_bps SMALLINT NULL - Optional user-side fee share (0–10 000) • protocol_fee_bps SMALLINT NULL - Optional protocol-side fee share (0–10 000) • fee_source TEXT NOT NULL - Provenance of fee rate (e.g. onchain:event) • fee_share_source TEXT NOT NULL - Provenance of fee split (e.g. onchain:param, docs)

Checks • At least one identifier present (contract_address or pool_id) and lengths enforced (20B/32B).

Notes • Fee terms are non-overlapping; each record defines a valid block-range. • Use liquidity_pool_fee_terms for historical fee reconstruction or to obtain the active fee at a given block.

🔑 Keys & joins • Primary key: uid • Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index) • Foreign keys: • (genesis_block_number, genesis_tx_index, genesis_log_index) → logs(block_number, tx_index, log_index) • factory → decentralized_exchanges(contract_address) • type_id → liquidity_pool_types(id)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Building the complete pool registry for routing and analytics • Filtering pools by fee, type, or token pair • Integrating with reserves, price, and swap datasets for liquidity intelligence • MEV routing, arbitrage path optimization, and chain-wide pool analytics • Constructing pool-level AI or quantitative features

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage). Optional ...

🟦 What this is Canonical registry of all verified Uniswap V3 liquidity pools, normalized into the BlockDB schema for deterministic cross-chain analysis. Fees are modeled separately as versioned terms, so fee changes over time are tracked precisely and are joinable back to the pool.

This dataset provides the structural backbone for connecting Uniswap V3 pool states with liquidity, price, and swap datasets.

Key traits • Schema-stable, versioned, and lineage-verifiable • Deterministic pool UIDs across chains and factory contracts • Real-time and historical coverage with factory-level lineage • Fully joinable with reserves, prices, swaps, and fee-term timelines

🌐 Chains / Coverage ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request). Full backfill to chain genesis with reorg-aware real-time ingestion. Covers all verified Uniswap V3 deployments across supported EVM networks.

📑 Schema List the columns exactly as delivered. Names/types are stable.

liquidity_pools (base registry) • uid BIGINT NOT NULL - stable pool identifier (derived from address or pool_id) • tracing_id BYTEA - deterministic row-level hash (proof-of-derivation) • parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph • genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path) • genesis_block_number BIGINT NOT NULL - factory create event block • genesis_tx_index INTEGER NOT NULL - create event tx index • genesis_log_index INTEGER NOT NULL - create event log index • contract_address BYTEA NULL - 20-byte pool address (v2/v3-style) • pool_id BYTEA NULL - 32-byte pool id (v4-style / manager-based) • factory BYTEA NOT NULL - DEX factory / pool manager address • type_id INTEGER NOT NULL - pool type FK (constant-product, concentrated, stable/weighted, etc.) • pairnum NUMERIC(6) NULL - optional pair ordinal/descriptor • tokens BYTEA[] NOT NULL - array of 20-byte token addresses (order matches protocol convention) • asset_managers BYTEA[] NULL - per-token managers (e.g., Balancer) • amp NUMERIC(6) NULL - amplification for stable/weighted math • pool_type TEXT NULL - optional human-readable type label • weights NUMERIC(6,5)[] NULL - per-token weights in 0..1 (5 dp) • tick_spacing SMALLINT NULL - grid size for concentrated liquidity

liquidity_pool_fee_terms (versioned, non-overlapping) • pool_uid BIGINT NOT NULL - FK → liquidity_pools(uid) • tracing_id BYTEA - Row identity hash (proof-of-derivation) • parent_tracing_ids BYTEA - Salted hashes of contributing parents • genesis_tracing_ids BYTEA - Salted hashes of ultimate sources • genesis_block_number BIGINT NOT NULL - Fee-update event block • genesis_block_time TIMESTAMPZ NOT NULL - Fee-update event timestamp • genesis_tx_index INTEGER NOT NULL - Transaction index • genesis_log_index INTEGER NOT NULL - Log index • pool_fee NUMERIC(18,18) NOT NULL - Total fee fraction (e.g. 0.003 = 0.30 %) • user_fee_bps SMALLINT NULL - Optional user-side fee share (0–10 000) • protocol_fee_bps SMALLINT NULL - Optional protocol-side fee share (0–10 000) • fee_source TEXT NOT NULL - Provenance of fee rate (e.g. onchain:event) • fee_share_source TEXT NOT NULL - Provenance of fee split (e.g. onchain:param, docs)

Checks • At least one identifier present (contract_address or pool_id) and lengths enforced (20B/32B).

Notes • Fee terms are non-overlapping; each record defines a valid block-range. • Use liquidity_pool_fee_terms for historical fee reconstruction or to obtain the active fee at a given block.

🔑 Keys & joins • Primary key: uid • Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index) • Foreign keys: • (genesis_block_number, genesis_tx_index, genesis_log_index) → logs(block_number, tx_index, log_index) • factory → decentralized_exchanges(contract_address) • type_id → liquidity_pool_types(id)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Building the complete pool registry for routing and analytics • Filtering pools by fee, type, or token pair • Integrating with reserves, price, and swap datasets for liquidity intelligence • MEV routing, arbitrage path optimization, and chain-wide pool analytics • Constructing pool-level AI or quantitative features

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage). Optional • Integratio...

🟦 What this is Reserves and state for Uniswap V3 Dex Protocol liquidity pools, including current tick, full tick-range from a minimum of -887272 to a maximum of 887272, Q64.96 sqrt price, liquidity and computed token amounts. Built for mid-price, depth/slippage, and routing research. • Schema-stable, versioned, audit-ready • Historical snapshots and real-time updates

🌐 Chains / 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. Covers all Uniswap V3 factories across supported EVM chains.

📑 Schema liquidity_pools_reserves - pool-level snapshots • id BIGINT - identity primary key • pool_uid BIGINT - FK → liquidity_pools(uid) • tracing_id BYTEA - deterministic row-level lineage hash • parent_tracing_ids BYTEA - hashes of immediate parent sources • genesis_tracing_ids BYTEA - hashes of original on-chain sources • genesis_block_number BIGINT - block of observed state • genesis_block_time TIMESTAMPTZ - timestamp of the block • genesis_tx_index INTEGER - transaction index within the block • genesis_log_index INTEGER - log index within the transaction • current_tick INTEGER - active tick for concentrated-liquidity pools • current_sqrt_price NUMERIC(49,0) - Q64.96-encoded sqrt price (sqrtP = value / 2^96)

liquidity_pools_reserves_details - granular tick/bin distribution • snapshot_id BIGINT - FK → liquidity_pools_reserves(id) • pool_uid BIGINT - denormalized pool reference • tick INTEGER - single-tick record (Uniswap V3-style) • lower_tick INTEGER - lower bound of a range (position-based) • upper_tick INTEGER - upper bound of a range • liquidity NUMERIC(38,0) - engine-native liquidity metric (Uniswap V3 L) • amount0 NUMERIC(78,0) - token0 amount at this locator (raw units) • amount1 NUMERIC(78,0) - token1 amount at this locator (raw units)

Notes • All reserve and amount values are in raw on-chain token units. • Apply ERC-20 decimals from erc20_tokens when scaling for price or display.

🔑 Keys & Joins • Primary key: id • Lineage triple for joins to raw events: (genesis_block_number, tx_index, log_index) • Foreign keys: • pool_uid → liquidity_pools(uid) • (genesis_block_number, genesis_tx_index, genesis_log_index) → logs(block_number, tx_index, log_index)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Compute mid-price, tick-to-price conversions, and per-tick depth curves • Slippage and routing analytics for v3-style AMMs • Risk/monitoring (price jumps vs. liquidity distribution changes)

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage). Optional • Integrations to Amazon S3, Azure Blob Storage, Snowflake, and other enterprise platforms on request.

🗂️ Files (time-partitioned in UTC, compressed) • Parquet • CSV • XLS • JSON

💡 Quality and operations • Reorg-aware ingestion. • 99.95% uptime target with SLA. • Backfills to chain genesis. • Versioned, schema-stable datasets; changes are additive and announced.

🔄 Change policy Schema is stable. Any breaking change ships as a new version (e.g., liquidity_pools_reserves_uniswap_v3_v2) with migration notes. Content updates are additive (new rows/fields filled); types aren’t changed in place.

🟦 What this is Canonical registry of all verified SushiSwap V2 liquidity pools, normalized into the BlockDB schema for deterministic cross-chain analysis. Fees are modeled separately as versioned terms, so fee changes over time are tracked precisely and are joinable back to the pool.

This dataset provides the structural backbone for connecting SushiSwap V2 pool states with liquidity, price, and swap datasets.

Key traits • Schema-stable, versioned, and lineage-verifiable • Deterministic pool UIDs across chains and factory contracts • Real-time and historical coverage with factory-level lineage • Fully joinable with reserves, prices, swaps, and fee-term timelines

🌐 Chains / Coverage ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request). Full backfill to chain genesis with reorg-aware real-time ingestion. Covers all verified SushiSwap V2 deployments across supported EVM networks.

📑 Schema List the columns exactly as delivered. Names/types are stable.

liquidity_pools (base registry) • uid BIGINT NOT NULL - stable pool identifier (derived from address or pool_id) • tracing_id BYTEA - deterministic row-level hash (proof-of-derivation) • parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph • genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path) • genesis_block_number BIGINT NOT NULL - factory create event block • genesis_tx_index INTEGER NOT NULL - create event tx index • genesis_log_index INTEGER NOT NULL - create event log index • contract_address BYTEA NULL - 20-byte pool address (v2/v3-style) • pool_id BYTEA NULL - 32-byte pool id (v4-style / manager-based) • factory BYTEA NOT NULL - DEX factory / pool manager address • type_id INTEGER NOT NULL - pool type FK (constant-product, concentrated, stable/weighted, etc.) • pairnum NUMERIC(6) NULL - optional pair ordinal/descriptor • tokens BYTEA[] NOT NULL - array of 20-byte token addresses (order matches protocol convention) • asset_managers BYTEA[] NULL - per-token managers (e.g., Balancer) • amp NUMERIC(6) NULL - amplification for stable/weighted math • pool_type TEXT NULL - optional human-readable type label • weights NUMERIC(6,5)[] NULL - per-token weights in 0..1 (5 dp) • tick_spacing SMALLINT NULL - grid size for concentrated liquidity

liquidity_pool_fee_terms (versioned, non-overlapping) • pool_uid BIGINT NOT NULL - FK → liquidity_pools(uid) • tracing_id BYTEA - Row identity hash (proof-of-derivation) • parent_tracing_ids BYTEA - Salted hashes of contributing parents • genesis_tracing_ids BYTEA - Salted hashes of ultimate sources • genesis_block_number BIGINT NOT NULL - Fee-update event block • genesis_block_time TIMESTAMPZ NOT NULL - Fee-update event timestamp • genesis_tx_index INTEGER NOT NULL - Transaction index • genesis_log_index INTEGER NOT NULL - Log index • pool_fee NUMERIC(18,18) NOT NULL - Total fee fraction (e.g. 0.003 = 0.30 %) • user_fee_bps SMALLINT NULL - Optional user-side fee share (0–10 000) • protocol_fee_bps SMALLINT NULL - Optional protocol-side fee share (0–10 000) • fee_source TEXT NOT NULL - Provenance of fee rate (e.g. onchain:event) • fee_share_source TEXT NOT NULL - Provenance of fee split (e.g. onchain:param, docs)

Checks • At least one identifier present (contract_address or pool_id) and lengths enforced (20B/32B).

Notes • Fee terms are non-overlapping; each record defines a valid block-range. • Use liquidity_pool_fee_terms for historical fee reconstruction or to obtain the active fee at a given block.

🔑 Keys & joins • Primary key: uid • Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index) • Foreign keys: • (genesis_block_number, genesis_tx_index, genesis_log_index) → logs(block_number, tx_index, log_index) • factory → decentralized_exchanges(contract_address) • type_id → liquidity_pool_types(id)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Building the complete pool registry for routing and analytics • Filtering pools by fee, type, or token pair • Integrating with reserves, price, and swap datasets for liquidity intelligence • MEV routing, arbitrage path optimization, and chain-wide pool analytics • Constructing pool-level AI or quantitative features

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage). Optional • Inte...

🟦 What this is Canonical registry of all verified Uniswap V2 liquidity pools, normalized into the BlockDB schema for deterministic cross-chain analysis. Fees are modeled separately as versioned terms, so fee changes over time are tracked precisely and are joinable back to the pool.

This dataset provides the structural backbone for connecting Uniswap V2 pool states with liquidity, price, and swap datasets.

Key traits • Schema-stable, versioned, and lineage-verifiable • Deterministic pool UIDs across chains and factory contracts • Real-time and historical coverage with factory-level lineage • Fully joinable with reserves, prices, swaps, and fee-term timelines

🌐 Chains / Coverage ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request). Full backfill to chain genesis with reorg-aware real-time ingestion. Covers all verified Uniswap V2 deployments across supported EVM networks.

📑 Schema List the columns exactly as delivered. Names/types are stable.

liquidity_pools (base registry) • uid BIGINT NOT NULL - stable pool identifier (derived from address or pool_id) • tracing_id BYTEA - deterministic row-level hash (proof-of-derivation) • parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph • genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path) • genesis_block_number BIGINT NOT NULL - factory create event block • genesis_tx_index INTEGER NOT NULL - create event tx index • genesis_log_index INTEGER NOT NULL - create event log index • contract_address BYTEA NULL - 20-byte pool address (v2/v3-style) • pool_id BYTEA NULL - 32-byte pool id (v4-style / manager-based) • factory BYTEA NOT NULL - DEX factory / pool manager address • type_id INTEGER NOT NULL - pool type FK (constant-product, concentrated, stable/weighted, etc.) • pairnum NUMERIC(6) NULL - optional pair ordinal/descriptor • tokens BYTEA[] NOT NULL - array of 20-byte token addresses (order matches protocol convention) • asset_managers BYTEA[] NULL - per-token managers (e.g., Balancer) • amp NUMERIC(6) NULL - amplification for stable/weighted math • pool_type TEXT NULL - optional human-readable type label • weights NUMERIC(6,5)[] NULL - per-token weights in 0..1 (5 dp) • tick_spacing SMALLINT NULL - grid size for concentrated liquidity

liquidity_pool_fee_terms (versioned, non-overlapping) • pool_uid BIGINT NOT NULL - FK → liquidity_pools(uid) • tracing_id BYTEA - Row identity hash (proof-of-derivation) • parent_tracing_ids BYTEA - Salted hashes of contributing parents • genesis_tracing_ids BYTEA - Salted hashes of ultimate sources • genesis_block_number BIGINT NOT NULL - Fee-update event block • genesis_block_time TIMESTAMPZ NOT NULL - Fee-update event timestamp • genesis_tx_index INTEGER NOT NULL - Transaction index • genesis_log_index INTEGER NOT NULL - Log index • pool_fee NUMERIC(18,18) NOT NULL - Total fee fraction (e.g. 0.003 = 0.30 %) • user_fee_bps SMALLINT NULL - Optional user-side fee share (0–10 000) • protocol_fee_bps SMALLINT NULL - Optional protocol-side fee share (0–10 000) • fee_source TEXT NOT NULL - Provenance of fee rate (e.g. onchain:event) • fee_share_source TEXT NOT NULL - Provenance of fee split (e.g. onchain:param, docs)

Checks • At least one identifier present (contract_address or pool_id) and lengths enforced (20B/32B).

Notes • Fee terms are non-overlapping; each record defines a valid block-range. • Use liquidity_pool_fee_terms for historical fee reconstruction or to obtain the active fee at a given block.

🔑 Keys & joins • Primary key: uid • Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index) • Foreign keys: • (genesis_block_number, genesis_tx_index, genesis_log_index) → logs(block_number, tx_index, log_index) • factory → decentralized_exchanges(contract_address) • type_id → liquidity_pool_types(id)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Building the complete pool registry for routing and analytics • Filtering pools by fee, type, or token pair • Integrating with reserves, price, and swap datasets for liquidity intelligence • MEV routing, arbitrage path optimization, and chain-wide pool analytics • Constructing pool-level AI or quantitative features

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage). Optional • Integratio...

🟦 What this is Canonical registry of all verified SushiSwap V3 liquidity pools, normalized into the BlockDB schema for deterministic cross-chain analysis. Fees are modeled separately as versioned terms, so fee changes over time are tracked precisely and are joinable back to the pool.

This dataset provides the structural backbone for connecting SushiSwap V3 pool states with liquidity, price, and swap datasets.

Key traits • Schema-stable, versioned, and lineage-verifiable • Deterministic pool UIDs across chains and factory contracts • Real-time and historical coverage with factory-level lineage • Fully joinable with reserves, prices, swaps, and fee-term timelines

🌐 Chains / Coverage ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request). Full backfill to chain genesis with reorg-aware real-time ingestion. Covers all verified SushiSwap V3 deployments across supported EVM networks.

📑 Schema List the columns exactly as delivered. Names/types are stable.

liquidity_pools (base registry) • uid BIGINT NOT NULL - stable pool identifier (derived from address or pool_id) • tracing_id BYTEA - deterministic row-level hash (proof-of-derivation) • parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph • genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path) • genesis_block_number BIGINT NOT NULL - factory create event block • genesis_tx_index INTEGER NOT NULL - create event tx index • genesis_log_index INTEGER NOT NULL - create event log index • contract_address BYTEA NULL - 20-byte pool address (v2/v3-style) • pool_id BYTEA NULL - 32-byte pool id (v4-style / manager-based) • factory BYTEA NOT NULL - DEX factory / pool manager address • type_id INTEGER NOT NULL - pool type FK (constant-product, concentrated, stable/weighted, etc.) • pairnum NUMERIC(6) NULL - optional pair ordinal/descriptor • tokens BYTEA[] NOT NULL - array of 20-byte token addresses (order matches protocol convention) • asset_managers BYTEA[] NULL - per-token managers (e.g., Balancer) • amp NUMERIC(6) NULL - amplification for stable/weighted math • pool_type TEXT NULL - optional human-readable type label • weights NUMERIC(6,5)[] NULL - per-token weights in 0..1 (5 dp) • tick_spacing SMALLINT NULL - grid size for concentrated liquidity

liquidity_pool_fee_terms (versioned, non-overlapping) • pool_uid BIGINT NOT NULL - FK → liquidity_pools(uid) • tracing_id BYTEA - Row identity hash (proof-of-derivation) • parent_tracing_ids BYTEA - Salted hashes of contributing parents • genesis_tracing_ids BYTEA - Salted hashes of ultimate sources • genesis_block_number BIGINT NOT NULL - Fee-update event block • genesis_block_time TIMESTAMPZ NOT NULL - Fee-update event timestamp • genesis_tx_index INTEGER NOT NULL - Transaction index • genesis_log_index INTEGER NOT NULL - Log index • pool_fee NUMERIC(18,18) NOT NULL - Total fee fraction (e.g. 0.003 = 0.30 %) • user_fee_bps SMALLINT NULL - Optional user-side fee share (0–10 000) • protocol_fee_bps SMALLINT NULL - Optional protocol-side fee share (0–10 000) • fee_source TEXT NOT NULL - Provenance of fee rate (e.g. onchain:event) • fee_share_source TEXT NOT NULL - Provenance of fee split (e.g. onchain:param, docs)

Checks • At least one identifier present (contract_address or pool_id) and lengths enforced (20B/32B).

Notes • Fee terms are non-overlapping; each record defines a valid block-range. • Use liquidity_pool_fee_terms for historical fee reconstruction or to obtain the active fee at a given block.

🔑 Keys & joins • Primary key: uid • Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index) • Foreign keys: • (genesis_block_number, genesis_tx_index, genesis_log_index) → logs(block_number, tx_index, log_index) • factory → decentralized_exchanges(contract_address) • type_id → liquidity_pool_types(id)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Building the complete pool registry for routing and analytics • Filtering pools by fee, type, or token pair • Integrating with reserves, price, and swap datasets for liquidity intelligence • MEV routing, arbitrage path optimization, and chain-wide pool analytics • Constructing pool-level AI or quantitative features

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage). Optional • Inte...

🟦 What this is Canonical registry of all verified Uniswap V4 liquidity pools, normalized into the BlockDB schema for deterministic cross-chain analysis. Fees are modeled separately as versioned terms, so fee changes over time are tracked precisely and are joinable back to the pool.

This dataset provides the structural backbone for connecting Uniswap V4 pool states with liquidity, price, and swap datasets.

Key traits • Schema-stable, versioned, and lineage-verifiable • Deterministic pool UIDs across chains and factory contracts • Real-time and historical coverage with factory-level lineage • Fully joinable with reserves, prices, swaps, and fee-term timelines

🌐 Chains / Coverage ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request). Full backfill to chain genesis with reorg-aware real-time ingestion. Covers all verified Uniswap V4 deployments across supported EVM networks.

📑 Schema List the columns exactly as delivered. Names/types are stable.

liquidity_pools (base registry) • uid BIGINT NOT NULL - stable pool identifier (derived from address or pool_id) • tracing_id BYTEA - deterministic row-level hash (proof-of-derivation) • parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph • genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path) • genesis_block_number BIGINT NOT NULL - factory create event block • genesis_tx_index INTEGER NOT NULL - create event tx index • genesis_log_index INTEGER NOT NULL - create event log index • contract_address BYTEA NULL - 20-byte pool address (v2/v3-style) • pool_id BYTEA NULL - 32-byte pool id (v4-style / manager-based) • factory BYTEA NOT NULL - DEX factory / pool manager address • type_id INTEGER NOT NULL - pool type FK (constant-product, concentrated, stable/weighted, etc.) • pairnum NUMERIC(6) NULL - optional pair ordinal/descriptor • tokens BYTEA[] NOT NULL - array of 20-byte token addresses (order matches protocol convention) • asset_managers BYTEA[] NULL - per-token managers (e.g., Balancer) • amp NUMERIC(6) NULL - amplification for stable/weighted math • pool_type TEXT NULL - optional human-readable type label • weights NUMERIC(6,5)[] NULL - per-token weights in 0..1 (5 dp) • tick_spacing SMALLINT NULL - grid size for concentrated liquidity

liquidity_pool_fee_terms (versioned, non-overlapping) • pool_uid BIGINT NOT NULL - FK → liquidity_pools(uid) • tracing_id BYTEA - Row identity hash (proof-of-derivation) • parent_tracing_ids BYTEA - Salted hashes of contributing parents • genesis_tracing_ids BYTEA - Salted hashes of ultimate sources • genesis_block_number BIGINT NOT NULL - Fee-update event block • genesis_block_time TIMESTAMPZ NOT NULL - Fee-update event timestamp • genesis_tx_index INTEGER NOT NULL - Transaction index • genesis_log_index INTEGER NOT NULL - Log index • pool_fee NUMERIC(18,18) NOT NULL - Total fee fraction (e.g. 0.003 = 0.30 %) • user_fee_bps SMALLINT NULL - Optional user-side fee share (0–10 000) • protocol_fee_bps SMALLINT NULL - Optional protocol-side fee share (0–10 000) • fee_source TEXT NOT NULL - Provenance of fee rate (e.g. onchain:event) • fee_share_source TEXT NOT NULL - Provenance of fee split (e.g. onchain:param, docs)

Checks • At least one identifier present (contract_address or pool_id) and lengths enforced (20B/32B).

Notes • Fee terms are non-overlapping; each record defines a valid block-range. • Use liquidity_pool_fee_terms for historical fee reconstruction or to obtain the active fee at a given block.

🔑 Keys & joins • Primary key: uid • Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index) • Foreign keys: • (genesis_block_number, genesis_tx_index, genesis_log_index) → logs(block_number, tx_index, log_index) • factory → decentralized_exchanges(contract_address) • type_id → liquidity_pool_types(id)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Building the complete pool registry for routing and analytics • Filtering pools by fee, type, or token pair • Integrating with reserves, price, and swap datasets for liquidity intelligence • MEV routing, arbitrage path optimization, and chain-wide pool analytics • Constructing pool-level AI or quantitative features

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage). Optional • Integratio...

🟦 What this is Canonical registry of all verified Balancer V2 liquidity pools, normalized into the BlockDB schema for deterministic cross-chain analysis. Fees are modeled separately as versioned terms, so fee changes over time are tracked precisely and are joinable back to the pool.

This dataset provides the structural backbone for connecting Balancer V2 pool states with liquidity, price, and swap datasets.

Key traits • Schema-stable, versioned, and lineage-verifiable • Deterministic pool UIDs across chains and factory contracts • Real-time and historical coverage with factory-level lineage • Fully joinable with reserves, prices, swaps, and fee-term timelines

🌐 Chains / Coverage ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request). Full backfill to chain genesis with reorg-aware real-time ingestion. Covers all verified Balancer V2 deployments across supported EVM networks.

📑 Schema List the columns exactly as delivered. Names/types are stable.

liquidity_pools (base registry) • uid BIGINT NOT NULL - stable pool identifier (derived from address or pool_id) • tracing_id BYTEA - deterministic row-level hash (proof-of-derivation) • parent_tracing_ids BYTEA - salted hash(es) of immediate parent rows in the derivation graph • genesis_tracing_ids BYTEA - salted hash(es) of original sources (genesis of the derivation path) • genesis_block_number BIGINT NOT NULL - factory create event block • genesis_tx_index INTEGER NOT NULL - create event tx index • genesis_log_index INTEGER NOT NULL - create event log index • contract_address BYTEA NULL - 20-byte pool address (v2/v3-style) • pool_id BYTEA NULL - 32-byte pool id (v4-style / manager-based) • factory BYTEA NOT NULL - DEX factory / pool manager address • type_id INTEGER NOT NULL - pool type FK (constant-product, concentrated, stable/weighted, etc.) • pairnum NUMERIC(6) NULL - optional pair ordinal/descriptor • tokens BYTEA[] NOT NULL - array of 20-byte token addresses (order matches protocol convention) • asset_managers BYTEA[] NULL - per-token managers (e.g., Balancer) • amp NUMERIC(6) NULL - amplification for stable/weighted math • pool_type TEXT NULL - optional human-readable type label • weights NUMERIC(6,5)[] NULL - per-token weights in 0..1 (5 dp) • tick_spacing SMALLINT NULL - grid size for concentrated liquidity

liquidity_pool_fee_terms (versioned, non-overlapping) • pool_uid BIGINT NOT NULL - FK → liquidity_pools(uid) • tracing_id BYTEA - Row identity hash (proof-of-derivation) • parent_tracing_ids BYTEA - Salted hashes of contributing parents • genesis_tracing_ids BYTEA - Salted hashes of ultimate sources • genesis_block_number BIGINT NOT NULL - Fee-update event block • genesis_block_time TIMESTAMPZ NOT NULL - Fee-update event timestamp • genesis_tx_index INTEGER NOT NULL - Transaction index • genesis_log_index INTEGER NOT NULL - Log index • pool_fee NUMERIC(18,18) NOT NULL - Total fee fraction (e.g. 0.003 = 0.30 %) • user_fee_bps SMALLINT NULL - Optional user-side fee share (0–10 000) • protocol_fee_bps SMALLINT NULL - Optional protocol-side fee share (0–10 000) • fee_source TEXT NOT NULL - Provenance of fee rate (e.g. onchain:event) • fee_share_source TEXT NOT NULL - Provenance of fee split (e.g. onchain:param, docs)

Checks • At least one identifier present (contract_address or pool_id) and lengths enforced (20B/32B).

Notes • Fee terms are non-overlapping; each record defines a valid block-range. • Use liquidity_pool_fee_terms for historical fee reconstruction or to obtain the active fee at a given block.

🔑 Keys & joins • Primary key: uid • Lineage triple for joins to raw events: (genesis_block_number, genesis_tx_index, genesis_log_index) • Foreign keys: • (genesis_block_number, genesis_tx_index, genesis_log_index) → logs(block_number, tx_index, log_index) • factory → decentralized_exchanges(contract_address) • type_id → liquidity_pool_types(id)

🧬 Lineage & Reproducibility Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph: • tracing_id - this row’s identity • parent_tracing_ids - immediate sources • genesis_tracing_ids - original on-chain sources This supports audits and exact reprocessing to source transactions/logs/function calls.

📈 Common uses • Building the complete pool registry for routing and analytics • Filtering pools by fee, type, or token pair • Integrating with reserves, price, and swap datasets for liquidity intelligence • MEV routing, arbitrage path optimization, and chain-wide pool analytics • Constructing pool-level AI or quantitative features

🚚 Delivery By default • WebSocket (API/WSS) reorg-aware live emissions when a new update is available; <140 ms median latency on ETH streams (7-day). • SFTP server for archives and daily End-of-Day (EOD) snapshots. • Model Context Protocol (MCP) for AI workflows (pull slices, schemas, lineage). Optional • Integra...