BTC · 5 minutes
The full Polymarket feed exactly as the collector received it, stored as parquet: one row per message, with its microsecond receive timestamp. A day arrives as the Polymarket market plus the exchange files for the same coin, all on one clock.
- Available
- 2026-03-24 → 2026-10-09
- Days on sale
- 200
- Size
- 225 GB
- Per day
- 1.1 GB
- Rows
- 60.7B
- Format
- parquet, one file per source per UTC day
What one day contains
The Polymarket 5 minutes up-down market for BTC, plus the exchange data for the same coin on the same clock. The exchange files are included in the price — they belong to the coin, not to the market, so whichever of the two markets you buy, they come with it.
- polymarket.btc.5m — the market itself
- binance.btc — Binance
- bybit.btc — Bybit
- okx.btc — OKX
- coinbase.btc — Coinbase
- chainlink.btc — Chainlink
What the data looks like
One parquet table per source, one row per message. Every file starts with the same four
columns — seq_local, ts_local (receive time, microseconds since the
epoch), kind_local, source_local — followed by the source's own
fields, named as the venue names them.
polymarket.btc.5m event_type · asset_id · side · price · size · best_bid · best_ask · … binance.btc e · s · T · p · q · b · a · u · … bybit.btc topic · s · ts · side · p · q · u · … okx.btc channel · instId · action · ts · px · sz · seqId · … coinbase.btc channel · type · product_id · price · size · best_bid · best_ask · … chainlink.btc topic · symbol · timestamp · value · …
Merge every source into one time-ordered stream by sorting on
ts_local.
Coverage
Share of the UTC day in which the file holds at least one row, by receive time. It says how much of the day arrived — not how much of it was worth trading: an illiquid pair is quiet because nobody traded, and Chainlink publishes once a second or two by design, so it sits near 92% on a perfectly good day.