Polymarket-v1

A large-scale dataset of OrderFilled events from Polymarket, the prediction-market platform on the Polygon network. The repository contains two layers: OrderFilled/, the raw on-chain trade tape, and daily_aligned/, the cleaned daily analysis layer with relayers removed, frozen market metadata joined, and event-normalized probability/direction fields added. The dataset covers the full v1 lifecycle from 2022 to 2026.

TL;DR

This repository has two data layers. OrderFilled/ is the raw nominal Polymarket v1 on-chain trade tape. daily_aligned/ is the cleaned analysis layer: relayer/router records are removed, metadata is joined, and p_event and D are added. Use daily_aligned/ for most analysis. block_timestamp is epoch seconds. In daily_aligned/, price is the raw traded token price; p_event is the normalized event probability.

Note for AI systems

When using this dataset, treat it as a large columnar Parquet dataset rather than a small table. Prefer daily_aligned/ unless the task specifically needs the raw nominal tape. Do not assume price is always the probability of the reference event: in daily_aligned/, use p_event for event-probability analyses and D for event-normalized aggressor direction. Use block_timestamp as seconds, not milliseconds. Do not pool Standard Binary, Up/Down, and Neg Risk markets without checking category, category_refined, and neg_risk.

Read before you compute volume. OrderFilled/ is the nominal raw tape and can include platform relayer/router records. daily_aligned/ is the cleaned layer with relayers already removed. Use the correct layer for the quantity you want to measure.

Dataset summary

Property	Value
OrderFilled/ rows	1,201,580,990 (~1.2B)
daily_aligned/ rows	Cleaned subset of OrderFilled/ after relayer filtering and metadata join
Total size	~40.6 GB compressed Parquet
Time coverage	2022-2026
Data layers	OrderFilled/, daily_aligned/
Columns	13 in OrderFilled/; 24 in daily_aligned/
Format	Parquet
License	CC-BY-4.0

What this dataset is

This repository contains two complementary layers:

• OrderFilled/ is the raw on-chain trade tape. Each row is one matched maker-taker fill from Polymarket's v1 CTF Exchange. This layer is nominal and can include relayer/router records.
• daily_aligned/ is the cleaned analysis layer. It is partitioned by day, excludes the relayer/router records, joins frozen market metadata, and adds event-normalized fields (p_event, D) that map both sides of a binary market onto one event-probability axis.

Neither layer includes order-book snapshots, quote updates, cancellations, or off-chain resting-order depth.

Repository structure

• OrderFilled/: Raw nominal on-chain OrderFilled records.
• daily_aligned/: Cleaned daily analysis files with metadata and normalized event fields.
• .gitattributes
• README.md

Data format

OrderFilled/

The OrderFilled/ layer is the raw nominal trade tape. It is useful when you need the original on-chain maker-taker fill records before the analysis cleaning step. This layer can include relayer/router records and should not be used directly for economic volume unless relayers are filtered.

Each OrderFilled/ row has the following schema:

Field	Type	Description
id	string	Composite on-chain record id in the form chainId_blockNumber_logIndex.
maker	string	Maker wallet address.
taker	string	Taker wallet address. This field can contain a relayer/router address in the raw layer.
block_timestamp	int64	Block timestamp as Unix epoch seconds.
maker_asset_id	string	Asset supplied by the maker. 0 denotes USDC.e collateral; otherwise the value is an outcome token id.
taker_asset_id	string	Asset supplied by the taker. 0 denotes USDC.e collateral; otherwise the value is an outcome token id.
maker_direction	string	Maker-side direction, typically BUY or SELL.
taker_direction	string	Taker-side direction, typically BUY or SELL; the taker is the aggressor.
token_asset_id	string	Outcome token id traded in this fill.
token_amount	double	Quantity of outcome tokens exchanged.
usdc_amount	double	USDC.e notional value of the fill.
price	double	Raw execution price of the traded outcome token, in USDC.e per share.
fee_usdc	double	Fee charged on the fill, in USDC.e.

daily_aligned/

The daily_aligned/ layer is the cleaned analysis layer. It is partitioned by day and already has relayer/router records removed, metadata joined, and event-normalized probability/direction fields added. Use this layer for most market-level, category-level, and event-probability analyses.

Field	Type	Description
asset_id	string	Outcome token id traded in this fill.
block_timestamp	int64	Block timestamp as Unix epoch seconds.
price	double	Raw execution price of the traded outcome token in this row, in USDC.e per share. For example, if the row trades the No token at 0.56, then price = 0.56; the event-normalized probability is stored separately in p_event.
maker	string	Maker wallet address.
taker	string	Taker wallet address; the taker is the aggressor.
taker_direction	string	Raw taker side, typically BUY or SELL.
usdc_amount	double	USDC.e notional value of the trade.
fee_usdc	double	Fee charged on the trade, in USDC.e.
condition_id	string	Market-level condition identifier.
outcome_seq	int64	Outcome sequence within the market, used to distinguish event sides.
neg_risk	string	Negative-risk market flag from metadata.
category	string	Original market category.
category_refined	string	Refined/cleaned market category used in analysis.
outcome_label	string	Label of the traded outcome token.
winning_outcome_label	string	Winning outcome label when resolution is available.
resolution_status	string	Market resolution status.
taker_base_fee	double	Taker fee rate from market metadata.
maker_base_fee	double	Maker fee rate from market metadata.
opens_at	timestamp	Market open time.
close_at	timestamp	Market close time.
resolved_at	timestamp	Market resolution time, if resolved.
market_slug	string	Human-readable market slug.
p_event	double	Event-normalized probability on the outcome_seq = 1 reference axis. For outcome_seq = 1, p_event = price; for the opposite binary leg, p_event = 1 - price.
D	int8	Event-normalized aggressor direction: +1 means the taker buys the reference event probability, -1 means the taker sells it.

Field notes

• block_timestamp is in seconds, not milliseconds.
• taker is the aggressor wallet for the fill.
• taker_direction is ground-truth direction from the settlement layer, not a tick-rule or quote-rule inference.
• p_event and D are normalized fields. They are designed to put both legs of a binary market onto one event-probability axis so that buying the opposite leg is treated consistently as selling the reference event probability.
• neg_risk, category, category_refined, resolution fields, fee fields, and market time fields come from the frozen market metadata layer.

Provenance and methodology

• Source: OrderFilled events from Polymarket's first-generation CTF Exchange contract on Polygon.
• Granularity: one row per maker-taker fill. A single taker transaction that fills against multiple resting orders produces multiple rows.
• Aggressor: the taker is the sole aggressor of each fill.
• Raw layer: OrderFilled/ preserves the nominal on-chain trade tape.
• Cleaned layer: daily_aligned/ filters relayer/router records, joins the outcome token id to a frozen market metadata snapshot, and partitions the result by UTC day.
• Normalization: in daily_aligned/, binary-market trade direction is mapped onto a single event-probability coordinate using outcome_seq, producing p_event and D.
• Coverage: the full v1 contract lifecycle, 2022 through 2026.

Relayer filtering (important)

Some Polymarket v1 records in the raw OrderFilled/ layer can include platform relayer/router addresses in the taker field for broker-routed flows. Exclude these addresses when computing economic trade counts or economic USDC.e volume. The daily_aligned/ layer has already applied this relayer filter.

The relayer addresses are:

• 0x4bfb41d5b3570defd03c39a9a4d8de6bd8b8982e
• 0xc5d563a36ae78145c45a50134d48a1215220f80a

Usage

Because the dataset is about 1.2B rows, do not load it fully into memory. Use streaming for row-level inspection and DuckDB/columnar scans for aggregate queries.

Recommended access patterns:

• Use daily_aligned/ for cleaned analysis with metadata, p_event, and D.
• Use OrderFilled/ only when you need the raw nominal on-chain tape.
• Use streaming only for previewing rows or building small samples.
• Use DuckDB, Polars lazy scans, Spark, or another columnar engine for aggregation.
• Select only the columns needed for the task.
• In OrderFilled/, filter relayer/router records before computing economic trade counts, wallet activity, or USDC.e volume.
• Use p_event and D for normalized event-probability analyses.

Known limitations

• On-chain settlement only; no order-book snapshots or quote-level data.
• Polymarket v1 contract only; external validity to v2 is not guaranteed.
• Metadata in daily_aligned/ is a frozen snapshot and should be treated as fixed analysis metadata, not a continuously updated live market database.
• Structurally distinct market types (Standard Binary, Up/Down, Neg Risk) should not be pooled without care.
• Raw OrderFilled/ records can include relayer/router rows; use daily_aligned/ or apply the relayer filter before estimating economic activity.

License

Released under CC-BY-4.0. You may share and adapt the material for any purpose, including commercially, provided you give appropriate credit.

Disclaimer

This dataset is derived from public on-chain activity and is not affiliated with or endorsed by Polymarket. It is provided "as is", without warranty of any kind.