PolygonLiquidityPoolsEventsDecoded Uniswap V3 liquidity events on Polygon since December 2021: Mint, Burn, Collect and Flash, one row per event, in the standard events schema.
univ3_liquidity_eventsWe decode Uniswap V3 liquidity from Polygon's event logs ourselves and keep only the events emitted by pools the Uniswap V3 factory (0x1f98431c8ad98523631ae4a59f267346ea31f984) created. QuickSwap V3 and other forks emit the same event signatures from other factories and are left out. The table uses the same 44 columns as the events table of our Ethereum dataset, with nothing renamed or derived: Log_Signature_Name is the event, Call_Signature_Name is the method that ran, and Arguments holds the decoded values. A row is one event.
Mint(sender, owner, tickLower, tickUpper, amount, amount0, amount1) adds liquidity to a tick range, Burn removes it and leaves the tokens owed, Collect pays out owed principal and fees, and Flash records a flash loan and its fee. Log_SmartContract is the pool. Swaps are not in this dataset; they are in the Polygon DEX Trades export, which joins on the transaction hash.
One row per Mint, Burn, Collect or Flash event emitted by pools the Uniswap V3 factory (0x1f98431c8ad98523631ae4a59f267346ea31f984) created, in the standard events schema.
polygon/uniswap_v3_liquidity/univ3_liquidity_events<start_block>_<end_block>.parquetSend this dataset’s full schema to an assistant and ask it anything. It reads the plain-text brief first, so the answer comes from the real column list rather than a guess.
Opens a new chat with the question filled in. Nothing about you is sent to Bitquery, and the assistant sees only the public brief.
Parquet files in a Requester Pays S3 bucket or a Cloudflare R2 bucket, chosen at checkout. On S3 you download with your own AWS account and AWS bills the transfer; on R2 you download with a read-only API key and pay no egress. Layout:
# univ3_liquidity_events
polygon/uniswap_v3_liquidity/univ3_liquidity_events<start_block>_<end_block>.parquetEvery window includes 44 columns. Only the time range changes.
univ3_liquidity_events table, 44 columnsOne Parquet table, univ3_liquidity_events, with 44 columns in the standard Ethereum events schema. A row is one Mint, Burn, Collect or Flash event emitted by pools the Uniswap V3 factory (0x1f98431c8ad98523631ae4a59f267346ea31f984) created, from successful transactions and non-reverted calls only. Data starts on 22 December 2021.
About 12,000,000 rows and 2.0 GB of ZSTD Parquet from 22 December 2021 to 1 October 2026, estimated from sampled days. On 1 October 2026 the table had about 3,000 rows. Pools from the Uniswap factory emit about half of all V3-style liquidity events on Polygon; the other half comes from forks and is left out. Across sampled days the all-fork count ran from 7,084 (1 April 2022) to 31,903 (1 April 2024) and 15,241 (1 April 2026).
Arguments is a JSON array with one entry per decoded argument: index, name, path, type and the value slots. Addresses and bytes are hex strings; uint128 and uint256 amounts are decimal strings in raw token units, so divide by the token's decimals yourself; small integers such as ticks sit in the integer slots. Call_Value and Fee_SenderFee are already in ETH or POL.
No. Swaps are in the Polygon DEX Trades dataset. Join on Transaction_Hash and the pool to see a swap next to the liquidity change around it.
QuickSwap V3 and other forks emit the same event signatures from other factories and are left out. Events from failed transactions and reverted calls are left out, so each row is a change that took effect.
Same protocol and schema, different chain. The Ethereum dataset also carries the position NFT events and pool creations; this one has the pool liquidity events only.
The export is one ClickHouse query over our decoded Polygon events, filtered to the contracts above. We checked the sample's row count against the independent count by event signature, confirmed each row has a decoded Arguments array and no duplicate (Transaction_Hash, Call_Index, Log_Index) key, and verified the Parquet schema matches the published Uniswap V3 Liquidity files column for column.
With DuckDB: SELECT Log_Signature_Name, count(*) FROM read_parquet('univ3_liquidity_events/*.parquet') GROUP BY 1. pandas, Polars, Spark and ClickHouse read the same files.
As flat Parquet files under a stable layout, one prefix per table, with a JSON manifest listing each file and its sha256. We prepare the files within 7 business days of purchase and email you the location. You choose at checkout where to collect them: a Requester Pays S3 bucket, downloaded with your own AWS account, or a Cloudflare R2 bucket with a read-only API key and no egress fees. Files stay available for 7 days from delivery.
Yes. The table links to a public sample file with 446 real rows from 1 October 2026, blocks 94,750,000 to 94,759,999. No email address required.
SolanaLast 12 monthsEvery swap and every pool event across every indexed DEX program on Solana, in one schema, decoded and USD-priced at block time.
PolymarketFull history · dailyPolymarket fills, position splits, merges and payouts, and market results on Polygon since September 2025, with market titles, outcomes and USD values.
SolanaLast 12 months
Every bonding-curve trade, token creation, migration and pool on Pump.fun, plus per-token OHLCV, decoded and USD-priced.
Tell us the chain, tables and date range.