We offer three easy-to-understand packages to fit your business needs. Visit intrinio.com/pricing to compare packages.

Bronze

The Bronze package is ideal for developing your idea and prototyping your platform with high-quality EOD options prices sourced from OPRA.

When you’re ready for launch, it’s a seamless transition to our Silver package for delayed options prices, Greeks and implied volatility, and unusual options activity, plus delayed equity prices.

• Latest EOD OPRA options prices

Exchange Fees & Requirements:

This package requires no paperwork or exchange fees.

Bronze Benefits:

• Web API access
• 300 API calls/minute limit
• File downloads
• Unlimited internal users
• Unlimited internal & external display
• Built-in ticketing system
• Live chat & email support

Silver

The Silver package is ideal for clients that want delayed options data for their platform, or for startups in the development and testing phase. You’ll get 15-minute delayed options data, Greeks, implied volatility, and unusual options activity, plus the latest EOD options prices and delayed equity prices.

You can easily move up to the Gold package for real-time options and equity prices, additional access methods, and premium support options.

• 15-minute delayed OPRA options prices, Greeks & IV
• 15-minute delayed OPRA unusual options activity
• Latest EOD OPRA options prices
• 15-minute delayed equity prices
• Underlying security reference data

Exchange Fees & Requirements:

If you subscribe to the Silver package and will not display the data outside of your firm, you’ll need to fill out a simplified exchange agreement and send it back to us. There are no exchange fees and we can provide immediate access to the data.

If you subscribe to the Silver package and will display the data outside of your firm, we’ll work with your team to submit the correct paperwork to OPRA for approval. Once approved, OPRA will bill exchange fees directly to your firm – typically $600-$2000/month depending on your use case. These fees are the same no matter what data provider you use. Per-user reporting is not required, so there are no variable per user fees.

Silver Benefits:

• Assistance with OPRA paperwork
• Web API access
• 2,000 API calls/minute limit
• File downloads
• Access to third-party datasets via Intrinio API (additional fees required)
• Unlimited internal users
• Unlimited internal & external display
• Built-in ticketing system
• Live chat & email support
• Concierge customer success team
• Comarketing & promotional initiatives

Gold

The Gold package is ideal for funded companies that are in the growth or scaling stage, as well as institutions that are innovating within the fintech space. This full-service solution offers real-time options prices, Greeks and implied volatility, and unusual options activity, as well as the latest EOD options prices and real-time equity prices.

You’ll also have access to our wide range of modern access methods, third-party data via Intrinio’s API with licensing assistance, support from our team of expert engineers, custom delivery architectures, and much more.

• Real-time OPRA options prices, Greeks & IV
• Real-time OPRA unusual options activity
• Latest EOD OPRA options prices
• Real-time equity prices
• Underlying security reference data

Exchange Fees & Requirements:

If you subscribe to the Gold package, we’ll work with your team to submit the correct paperwork to OPRA for approval. Once approved, OPRA will bill exchange fees directly to your firm – typically $600-$2000/month depending on your use case. These fees are the same no matter what data provider you use. Per-user reporting is required, with an associated variable per user fee.

Gold Benefits:

• Assistance with OPRA paperwork
• Web API access
• 2,000 API calls/minute limit
• WebSocket access (additional fee)
• Customizable access methods (Snowflake, FTP, etc.)
• Access to third-party datasets via Intrinio API (additional fees required)
• Unlimited internal users
• Unlimited internal & external display
• Built-in ticketing system
• Live chat & email support
• Concierge customer success team
• Comarketing & promotional initiatives
• Access to engineering team

Platinum

Don’t see a package that fits your needs? Our team can design a premium custom package for your business.

We offer three easy-to-understand equity data packages to fit your business needs. Visit intrinio.com/pricing to compare packages.

Bronze

The Bronze package is ideal for developing your idea and prototyping your platform with high-quality EOD equity pricing data, standardized financial statement data, and supplementary fundamental datasets.

When you’re ready for launch, it’s a seamless transition to our Silver package for additional data sets, 15-minute delayed equity pricing data, expanded history, and more.

• Historical EOD equity prices & technicals (10 years history)
• Security reference data
• Standardized & as-reported financial statements (5 years history)
• 7 supplementary fundamental data sets

Bronze Benefits:

• Web API access
• 300 API calls/minute limit
• Unlimited internal users
• Unlimited internal & external display
• Built-in ticketing system
• Live chat & email support

Silver

The Silver package is ideal for startups that are in development, testing, or in the beta launch phase. Hit the ground running with 15-minute delayed and historical intraday and EOD equity prices, plus our standardized and as-reported financial statement data with nine supplementary data sets, including insider transactions and institutional ownership.

When you’re ready to scale, easily move up to the Gold package for our full range of data sets and full history, real-time equity pricing data, premium support options, and much more.

• 15-minute delayed & historical intraday equity prices
• Historical EOD equity prices & technicals (full history)
• Security reference data
• Standardized & as-reported financial statements (10 years history)
• 9 supplementary fundamental data sets

Silver Benefits:

• Web API access
• 2,000 API calls/minute limit
• Access to third-party datasets via Intrinio API (additional fees required)
• Unlimited internal users
• Unlimited internal & external display
• Built-in ticketing system
• Live chat & email support

Gold

The Gold package is ideal for funded companies that are in the growth or scaling stage, as well as institutions that are innovating within the fintech space. This full-service solution offers our complete collection of equity pricing data feeds, from real-time to historical EOD, plus standardized financial statement data and nine supplementary feeds.

You’ll also have access to our wide range of modern access methods, third-party data via Intrinio’s API with licensing assistance, support from our team of expert engineers, custom delivery architectures, and much more.

• Real-time equity prices
• Historical intraday equity prices
• Historical EOD equity prices & technicals (full history)
• Security reference data
• Standardized & as-reported financial statements (full history)
• 9 supplementary fundamental data sets

Gold Benefits:

• No exchange fees
• No user reporting or variable per-user exchange fees
• High liquidity (6%+)
• Web API & WebSocket access
• 2,000 API calls/minute limit
• Customizable access methods (Snowflake, FTP, etc.)
• Access to third-party datasets via Intrinio API (additional fees required)
• Unlimited internal users
• Unlimited internal & external display
• Built-in ticketing system
• Live chat & email support
• Access to engineering team
• Concierge customer success team
• Comarketing & promotional initiatives

Platinum

Don’t see a package that fits your needs? Our team can design premium custom packages for institutions.

Context

According to Investopedia:

FAANG is an acronym referring to the stocks of the five most popular and best-performing American technology companies: Facebook, Amazon, Apple, Netflix and Alphabet (formerly known as Google). In addition to being widely known among consumers, the five FAANG stocks are among the largest companies in the world, with a combined market capitalization of over $4.1 trillion as of January 2020. Some have raised concerns that the FAANG stocks may be in the midst of a bubble, whereas others argue that their growth is justified by the stellar financial and operational performance they have shown in recent years.

Regardless of the myriad of accolades, comments, and even controversies surrounding the FAANG stocks, they are nevertheless a data science/mining treasure and the bellwether of the NASDAQ index, if not the entire US technology sector.

This Kaggle dataset contains over 20 years of daily historical data for the five FAANG constituents, as retrieved from this free stock API. It is a public-domain dataset that gives the data science practitioners (a.k.a., you!) the full flexibility to derive second-order insights and investment heuristics from it.

Content

Over 20 years of daily historical data (2000-01-01 to 2020-10-01) for the five FAANG stocks: Facebook, Amazon, Apple, Netflix, and Alphabet/Google. For completeness, both raw and adjusted prices are included, along with historical split events and dividend payouts (check out here for how stock market API providers perform price adjustments).

Acknowledgements

Data source: https://www.alphavantage.co/

Our vast historical bar database supports multi asset tick, n-minute and EOD time series price data from major markets. We provide Rest API or custom file services to meet requirements.

Connect with us and provide your request details in order to work out a data solution that meets your requirements.

Pt Eod Technology Export Import Data. Follow the Eximpedia platform for HS code, importer-exporter records, and customs shipment details.

Adore Silver Eod Export Import Data. Follow the Eximpedia platform for HS code, importer-exporter records, and customs shipment details.

This dataset provides comprehensive stock market data sourced from Polygon API and Finviz. It includes two main components:

1. Aggregated Data:

   • In this sheet contains day-wise data for a specific stock ticker with columns for:
   • DATE: Date of the stock data
   • DAY: Day of the week for the stock
   • TICKER: Stock symbol
   • Prev Close: Previous day's close price at 16:00
   • PM Hi: Highest price during pre-market hours (4:00 - 9:29)
   • PM Hi Time: Time of the highest pre-market price
   • PM total vol to PM High: Total volume up to the highest pre-market price
   • PM Volume: Total volume during pre-market hours
   • Open $: Opening price at 9:30
   • Open 1 min Vol: Total volume in the first minute after opening
   • Open 2 min Vol: Total volume in the first two minutes after opening
   • ∑ Vol: PM to intra Hi: Total volume from pre-market to highest intra-day price
   • ∑ Vol: Open to intra Hi: Total volume from market open to highest intra-day price
   • HOD: High of the day from 9:29 to 16:00
   • HOD Time: Time of the high of the day
   • HOD 1 Min Vol: Volume in the minute when the high of the day occurred
   • EOD $: End-of-day price at 16:00
   • Volume: Total volume from 4:00 to 19:00
   • Market Cap: Market capitalization (sourced from Finviz)
   • Float: Float shares (sourced from Finviz)
   • Shares O/S: Outstanding shares (sourced from Finviz)
   • Short Float %: Percentage of shares shorted (sourced from Finviz)
   • Inst Own %: Institutional ownership percentage (sourced from Finviz)
   • Insider Own %: Insider ownership percentage (sourced from Finviz)

2. Ticker-Specific Sheets:

   • Each sheet contains minute-wise data for a specific stock ticker with columns for:
     • Time: Timestamp of the record
     • Low Price: Lowest price during the minute
     • High Price: Highest price during the minute
     • Open Price: Opening price during the minute
     • Close Price: Closing price during the minute

Tags: #StockMarketData #FinancialData #MinuteWiseData #PolygonAPI #Finviz #StockAnalysis #TradingData #MarketMetrics #StockSymbols #FinancialAnalysis

Agritek Semena Eod Export Import Data. Follow the Eximpedia platform for HS code, importer-exporter records, and customs shipment details.

Extensive and dependable pricing information spanning the entire range of financial markets. Encompassing worldwide coverage from stock exchanges, trading platforms, indicative contributed prices, assessed valuations, expert third-party sources, and our enhanced data offerings. User-friendly request-response, bulk access, and tailored desktop interfaces to meet nearly any organizational or application data need. Worldwide, real-time, delayed streaming, intraday updates, and meticulously curated end-of-day pricing information.

Eod Panama Sa Export Import Data. Follow the Eximpedia platform for HS code, importer-exporter records, and customs shipment details.

Dataset Overview Canonical Raw Data represents the ground-truth layer of DeFi and on-chain intelligence. Each sub-dataset captures data at a distinct level of the EVM execution stack - from the raw blocks to raw contract functions results. Each record includes a deterministic _tracing_id, forming the root lineage reference for all derived BlockDB datasets

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.

Included Datasets

1. BlockDB Canonical Raw Blocks (Lineage-Verified) Canonical block-level data including block hashes, parent relationships, miner addresses, gas parameters, and recomputed receipt roots for integrity verification.

2. BlockDB Canonical Raw Transactions (Lineage-Verified) Full transaction-level coverage across all EVM networks, including sender/receiver, input data, gas details, and other fields.

3. BlockDB Canonical Raw Logs (Lineage-Verified) Log events emitted by contracts, normalized across protocols.

4. BlockDB Discovered Smart Contracts Catalog of deployed smart contracts discovered through emmitted logs.

5. BlockDB Discovered Smart Contract Function Results Structured outputs of executed on-chain function calls (e.g., eth_call, view functions).

Lineage Each record of these datasets includes a deterministic _tracing_id, forming the root lineage reference for all derived BlockDB datasets (swaps, liquidity, and token prices). This ensures verifiable traceability, reproducibility, and proof-of-derivation for every downstream record.

Common Use Cases • Establish a canonical on-chain ground truth across multiple EVM chains • Power downstream datasets (tokens, swaps, liquidity, prices) with verified base-layer inputs • Build data lineage visualizations or chain-state replayers for validation and analytics

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

Eod Trade Inc Export Import Data. Follow the Eximpedia platform for HS code, importer-exporter records, and customs shipment details.

Dataset Overview Each row represents a unique log emitted during transaction execution: • Canonical positioning: (block_number, tx_index, log_index) • Emitting contract address • Primary event topic (topic_zero) • Additional topics (data_topics) • Raw event data payload

All fields are stored exactly as produced by the node, with direct RLP verifiability for topics, data, and contract address.

Every log includes a deterministic _tracing_id that links the record to its genesis event and upstream transaction, forming the foundation for decoded events, swaps, liquidity, NFT events, and custom protocol decoders in downstream BlockDB products.

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: • block_number BIGINT – Block number that contains the emitting transaction • tx_index INTEGER – Zero-based index of the transaction within the block • log_index INTEGER – Zero-based position of the log within the transaction • contract_address BYTEA – 20-byte address of the contract that emitted the log • topic_zero BYTEA – 32-byte primary topic hash identifying the event type (NULL for anonymous events) • data_topics BYTEA[] – Array of additional topics (topics[1..n]), as raw bytes • data BYTEA – Raw event data payload as emitted on-chain • _tracing_id BYTEA – Deterministic lineage identifier of this log record • _created_at TIMESTAMPTZ – Record creation timestamp • _updated_at TIMESTAMPTZ – Record last update timestamp

Notes • Primary key: (block_number, tx_index, log_index) guarantees canonical ordering and uniqueness. • Foreign key: (block_number, tx_index) links each log directly to its canonical transaction record. • Indexes on contract_address, topic_zero, and (contract_address, topic_zero) support fast protocol- or event-specific scans. • Binary values can be rendered as hex via encode(column, 'hex') in SQL for display or downstream joins.

Lineage & Integrity Direct RLP-verifiable fields: contract_address, topic_zero, data_topics, data, and log_index are all directly or indirectly validated against node RLP.

_tracing_id provides a deterministic, cryptographic handle for each log row, enabling: • Provenance tracking from raw logs to decoded events and higher-level features • Reproducible analytics and signal extraction • Cross-system consistency checks (RPC vs. indexers vs. internal warehouses)

Common Use Cases • Building decoded event layers (swaps, LP actions, mints, burns, governance events, NFT activity) • Reconstructing DEX activity and liquidity flows directly from raw logs • Protocol-specific analytics (AMMs, lending, perpetuals, bridges, staking) from first principles • Detecting MEV patterns, liquidations, and arbitrage events at log-level resolution

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

Dataset Overview 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.

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 the columns exactly as delivered. • contract_address BYTEA - PK; 20-byte ERC-20 contract address • block_number BIGINT - first block where the token was recognized • block_time TIMESTAMPTZ - UTC timestamp when the block was mined • tx_index INTEGER - tx index for that event • log_index INTEGER - log index for that event • name TEXT - asset name • symbol TEXT - token symbol or ticker • decimals SMALLINT - number of decimal places • _tracing_id BYTEA - deterministic row-level hash • _parent_tracing_ids BYTEA[] - hash(es) of immediate parent rows in the derivation graph • _genesis_tracing_ids BYTEA[] - hash(es) of original sources (genesis of the derivation path) • _created_at TIMESTAMPTZ - Record creation timestamp. • _updated_at TIMESTAMPTZ - Record last update timestamp

Notes • Use encode(contract_address,'hex') for hex presentation. • Metadata for each token type is retrieved deterministically via ABI decoding or registry sources. • If the ABI read was unsuccessful, the token is not present in this table.

Lineage 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 Use Cases • 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

Quality • Each row includes a cryptographic hash linking back to raw on-chain events for auditability. • Tick-level resolution for precision. • Reorg-aware ingestion ensuring data integrity. • Complete backfills to chain genesis for consistency.

Dataset Overview Reserves for even-distribution Balancer V3 protocol pools. One row holds the current reserve vector (up to 8 tokens). Useful for price, slippage, TVL, and routing logic.

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. Covers all Balancer V3 Vaults across supported EVM chains.

Schema List the columns exactly as delivered.

liquidity_pools_reserves - pool-level snapshots • id BIGINT - identity primary key • pool_uid BIGINT - FK → liquidity_pools(uid) • block_number BIGINT - first block where the token was recognized • block_time TIMESTAMPTZ - UTC timestamp when the block was mined • tx_index INTEGER - tx index for that event • log_index INTEGER - log index for that event • reserves NUMERIC(78,0)[] - raw reserves per token (V2-style or Balancer pools) • current_tick INTEGER - active tick for concentrated-liquidity pools • current_sqrt_price NUMERIC(49,0) - Q64.96-encoded sqrt price (sqrtP = value / 2^96) • current_bin INTEGER - bin index for bin-style AMMs • _tracing_id BYTEA - deterministic row-level hash • _parent_tracing_ids BYTEA[] - hash(es) of immediate parent rows in the derivation graph • _genesis_tracing_ids BYTEA[] - hash(es) of original sources (genesis of the derivation path) • _created_at TIMESTAMPTZ - Record creation timestamp. • _updated_at TIMESTAMPTZ - Record last update timestamp

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 • bin_id INTEGER - bin index (for bin-style AMMs) • liquidity NUMERIC(38,0) - engine-native liquidity metric (e.g., 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 table when scaling for price or display. • One of the payloads must be present per liquidity_pools_reserves row.

Lineage 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 Use Cases • Price, TVL, and slippage calculations across pools and chains • Routing and arbitrage research (depth, fee tiers, fragmentation) • Market-structure analytics and liquidity regime detection • Backtesting and AI modeling with verifiable pool states • Monitoring dashboards for protocol health, volatility, and liquidity shifts

Quality • Each row includes a cryptographic hash linking back to raw on-chain events for auditability. • Tick-level resolution for precision. • Reorg-aware ingestion ensuring data integrity. • Complete backfills to chain genesis for consistency.

Dataset Overview Canonical registry of all verified Balancer 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 Balancer V3 pool states with liquidity, price, and swap datasets.

Chains and 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 V3 deployments across supported EVM networks.

Schema List the columns exactly as delivered.

liquidity_pools (base registry) • uid BIGINT NOT NULL - stable pool identifier (derived from address or pool_id) • block_number BIGINT - first block where the token was recognized • block_time TIMESTAMPTZ - UTC timestamp when the block was mined • tx_index INTEGER - tx index for that event • log_index INTEGER - log index for that event • 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 • _tracing_id BYTEA - deterministic row-level hash • _parent_tracing_ids BYTEA[] - hash(es) of immediate parent rows in the derivation graph • _genesis_tracing_ids BYTEA[] - hash(es) of original sources (genesis of the derivation path) • _created_at TIMESTAMPTZ - Record creation timestamp. • _updated_at TIMESTAMPTZ - Record last update timestamp

liquidity_pool_fee_terms (versioned, non-overlapping) • pool_uid BIGINT NOT NULL - FK → liquidity_pools(uid) • block_number BIGINT - first block where the token was recognized • block_time TIMESTAMPTZ - UTC timestamp when the block was mined • tx_index INTEGER - tx index for that event • log_index INTEGER - log index for that event • 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) • _tracing_id BYTEA - deterministic row-level hash • _parent_tracing_ids BYTEA[] - hash(es) of immediate parent rows in the derivation graph • _genesis_tracing_ids BYTEA[] - hash(es) of original sources (genesis of the derivation path) • _created_at TIMESTAMPTZ - Record creation timestamp. • _updated_at TIMESTAMPTZ - Record last update timestamp

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.

Lineage 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 Use Cases • 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

Quality • Each row includes a cryptographic hash linking back to raw on-chain events for auditability. • Tick-level resolution for precision. • Reorg-aware ingestion ensuring data integrity. • Complete backfills to chain genesis for consistency.

Dataset Overview 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.

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

Schema List the columns exactly as delivered.

liquidity_pools (base registry) • uid BIGINT NOT NULL - stable pool identifier (derived from address or pool_id) • block_number BIGINT - first block where the token was recognized • block_time TIMESTAMPTZ - UTC timestamp when the block was mined • tx_index INTEGER - tx index for that event • log_index INTEGER - log index for that event • 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 • _tracing_id BYTEA - deterministic row-level hash • _parent_tracing_ids BYTEA[] - hash(es) of immediate parent rows in the derivation graph • _genesis_tracing_ids BYTEA[] - hash(es) of original sources (genesis of the derivation path) • _created_at TIMESTAMPTZ - Record creation timestamp. • _updated_at TIMESTAMPTZ - Record last update timestamp

liquidity_pool_fee_terms (versioned, non-overlapping) • pool_uid BIGINT NOT NULL - FK → liquidity_pools(uid) • block_number BIGINT - first block where the token was recognized • block_time TIMESTAMPTZ - UTC timestamp when the block was mined • tx_index INTEGER - tx index for that event • log_index INTEGER - log index for that event • 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) • _tracing_id BYTEA - deterministic row-level hash • _parent_tracing_ids BYTEA[] - hash(es) of immediate parent rows in the derivation graph • _genesis_tracing_ids BYTEA[] - hash(es) of original sources (genesis of the derivation path) • _created_at TIMESTAMPTZ - Record creation timestamp. • _updated_at TIMESTAMPTZ - Record last update timestamp

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.

Lineage 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 Use Cases • 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

Quality • Each row includes a cryptographic hash linking back to raw on-chain events for auditability. • Tick-level resolution for precision. • Reorg-aware ingestion ensuring data integrity. • Complete backfills to chain genesis for consistency.

Dataset Overview The Level-2 (L2) stablecoin liquidity impact dataset provides quantized liquidity grids around the mid-price (typically ±10%) for all major USD-pegged stablecoin pairs. Each row represents a depth snapshot at a defined basis-point spacing (e.g. 10 bps), describing how much stablecoin can be executed before the price deviates by a certain percentage.

These grids allow analysts and developers to model depth curves, slippage, and peg resilience with high precision, fully reproducible from on-chain data.

Key traits • Focused on USD and major fiat-pegged tokens (USDC, USDT, DAI, FRAX, LUSD, crvUSD, etc.) • Schema-stable, versioned, and audit-ready • Real-time (WSS) and historical/EOD delivery • Fully verifiable lineage back to pool events and raw on-chain logs

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. Coverage includes all major DEX protocols holding stablecoin pairs: • Uniswap V2, V3, V4 • Curve, Balancer, Aerodrome, Solidly, Maverick, Pancake, and others

Schema List the columns exactly as delivered. • snapshot_id BIGINT - unique identifier for each grid snapshot. • pool_uid BIGINT - reference to the liquidity pool (liquidity_pools.uid). • block_number BIGINT - block number of the originating event. • tx_index INTEGER - transaction index within that block. • log_index INTEGER - log index within the transaction. • token_in BYTEA - 20-byte ERC-20 address of the input token. • token_out BYTEA - 20-byte ERC-20 address of the output token. • current_price NUMERIC(78,18) - mid-price (token_out per 1 token_in, decimals-adjusted). • grid_step_bps SMALLINT - spacing between grid points, in basis points. • grid_radius_bps INTEGER - total radius of the grid window, in basis points. • grid_points SMALLINT - number of grid points; must equal radius/step + 1. • _tracing_id BYTEA - deterministic row-level hash • _parent_tracing_ids BYTEA[] - hash(es) of immediate parent rows in the derivation graph • _genesis_tracing_ids BYTEA[] - hash(es) of original sources (genesis of the derivation path) • _created_at TIMESTAMPTZ - Record creation timestamp. • _updated_at TIMESTAMPTZ - Record last update timestamp

token_to_token_l2_points • snapshot_id BIGINT - reference to the parent snapshot (token_to_token_l2_snapshots.snapshot_id). • point_index SMALLINT - sequential index (0 … grid_points − 1). • offset_bps_abs INTEGER - absolute offset from the mid-price, in basis points. • size_in NUMERIC(78,18) - executable input amount required to reach this offset. • size_out NUMERIC(78,18) - corresponding output amount at that offset. • price_at_point NUMERIC(78,18) - average price (out / in) including impact.

(For hex display: encode(token_in,'hex'), encode(token_out,'hex').)

Lineage 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 Use Cases • Stablecoin peg analysis through liquidity depth modeling • Execution algorithm calibration (impact-aware order sizing) • Market-making and slippage profiling • Cross-chain peg risk and liquidity fragmentation studies • MEV and arbitrage signal extraction • AI/ML feature generation for depeg and volatility prediction

Quality • Each row includes a cryptographic hash linking back to raw on-chain events for auditability. • Tick-level resolution for precision. • Reorg-aware ingestion ensuring data integrity. • Complete backfills to chain genesis for consistency.

Dataset Overview Each transaction entry reflects the exact canonical form of the transaction as included in a block, including sender/recipient addresses, gas usage, execution status, transaction type, and (when applicable) created contract addresses.

All records include a deterministic _tracing_id that links each row to its genesis source event, enabling full reconstruction of execution flow and downstream derivations.

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: • tx_hash BYTEA - 32-byte Keccak-256 transaction hash • from_address BYTEA - 20-byte sender address • to_address BYTEA - 20-byte recipient address (NULL for contract creation) • block_number BIGINT - Block number containing the transaction • tx_index INTEGER - Zero-based index of the transaction within the block • created_contract_address BYTEA - 20-byte contract address created by this transaction (if applicable) • gas_used BIGINT - Gas consumed during transaction execution • effective_gas_price_wei NUMERIC(38,0) - Final gas price paid in wei • status_success BOOLEAN - TRUE if successful, FALSE if reverted, NULL for pre-Byzantium blocks • root BYTEA - Post-transaction state root for pre-Byzantium blocks (NULL otherwise) • tx_type SMALLINT - Transaction type (e.g., 1 = legacy, 2 = EIP-1559) • _tracing_id BYTEA - Deterministic lineage identifier for this transaction • _created_at TIMESTAMPTZ - Record creation timestamp • _updated_at TIMESTAMPTZ - Record last update timestamp

Notes • All binary values can be converted to hex via encode(column, 'hex') for readability. • Unique constraint ensures canonical (block_number, tx_index) ordering. • tx_index and block inclusion can be directly verified with canonical RLP.

Lineage Each tx record includes a deterministic _tracing_id, forming the root lineage reference for all derived BlockDB datasets (swaps, liquidity, and token prices). This ensures verifiable traceability, reproducibility, and proof-of-derivation for every downstream record.

Common Use Cases • Ground-truth layer for swaps, liquidity, and token analytics • Backtesting models using canonical transaction flow • Gas market analysis (EIP-1559, congestion modeling, MEV impact) • Contract deployment tracking and behavior analysis

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

Dataset Overview Canonical, lineage-verified dataset of on-chain liquidity reserves capturing the complete state of AMM pools at block-level and real-time granularity. Each record represents a verifiable snapshot of a pool’s state - either its aggregate reserve vector or its fine-grained tick/bin liquidity distribution - linked deterministically to the on-chain event that produced it.

Supports all major AMM architectures - from even-distribution (V2-style) to concentrated (V3/V4-style) and bin/range-based models - with full reproducibility from raw logs.

Key traits • Protocol-aware coverage for V2, V3, V4, and hybrid AMM variants • Historical snapshots and reorg-aware real-time updates • Full tick-range from a minimum of -887272 to a maximum of 887272 • Highest granularity possible: Log-by-Log • Schema-stable, versioned, and audit-ready • Deterministic, traceable lineage from pool creation to latest reserve update

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. Covers major protocols: Uniswap V2/V3/V4, SushiSwap V2/V3, PancakeSwap V2/V3, Aerodrome V1/Slipstream, Curve, Balancer, TraderJoe, Maverick, Solidly, and others.

Schema List the columns exactly as delivered.

liquidity_pools_reserves - pool-level snapshots • id BIGINT - identity primary key • pool_uid BIGINT - FK → liquidity_pools(uid) • block_number BIGINT - first block where the token was recognized • block_time TIMESTAMPTZ - UTC timestamp when the block was mined • tx_index INTEGER - tx index for that event • log_index INTEGER - log index for that event • reserves NUMERIC(78,0)[] - raw reserves per token (V2-style or Balancer pools) • current_tick INTEGER - active tick for concentrated-liquidity pools • current_sqrt_price NUMERIC(49,0) - Q64.96-encoded sqrt price (sqrtP = value / 2^96) • current_bin INTEGER - bin index for bin-style AMMs • _tracing_id BYTEA - deterministic row-level hash • _parent_tracing_ids BYTEA[] - hash(es) of immediate parent rows in the derivation graph • _genesis_tracing_ids BYTEA[] - hash(es) of original sources (genesis of the derivation path) • _created_at TIMESTAMPTZ - Record creation timestamp. • _updated_at TIMESTAMPTZ - Record last update timestamp

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 • bin_id INTEGER - bin index (for bin-style AMMs) • liquidity NUMERIC(38,0) - engine-native liquidity metric (e.g., 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 table when scaling for price or display. • One of the payloads must be present per liquidity_pools_reserves row.

Lineage 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 Use Cases • Price, TVL, and slippage calculations across pools and chains • Routing and arbitrage research (depth, fee tiers, fragmentation) • Market-structure analytics and liquidity regime detection • Backtesting and AI modeling with verifiable pool states • Monitoring dashboards for protocol health, volatility, and liquidity shifts

Quality • Each row includes a cryptographic hash linking back to raw on-chain events for auditability. • Tick-level resolution for precision. • Reorg-aware ingestion ensuring data integrity. • Complete backfills to chain genesis for consistency.