Splitrule

Polymarket US fees, rules changes, and dated events.

Account

VENUE

Polymarket US

QCX LLC, trading under the assumed name Polymarket US. Designated contract market, designated July 9, 2025. Access is a direct account with identity verification plus your own key, and the public catalogue answers without one.

Read 2026-09-28. The CFTC's Designated Contract Markets list, under Industry Filings, records the assumed name against the QCX entity.

WATCHES

What Splitrule checks on this venue every day

Each day, a check reads one published page and compares it with the read recorded here. Each row below says whether the page was unchanged, moved, or could not be read at the last check.

Splitrule checks 4 pages on this venue. This page shows 1 of them.

SCHEDULE

What does it cost to trade on Polymarket US?

Dated reference observed 2026-09-17T14:24:51Z. This is not current fee authority. Formula estimates precede fill rounding, order caps, and volume rebates. These terms come from the venue's own published schedule, not from a summary of it. The fee is proportional to the price times one minus the price, so it peaks at 50¢ and falls toward the tails. Any flat per-contract quote is wrong on this venue by construction.

taker:  0.0695 x C x P x (1-P)          1.74¢ per contract at 50¢
maker:  rebate of 0.0125 x C x P x (1-P)   0.31¢ per contract at 50¢

The selected schedule takes effect 2026-09-17. The schedule names no settlement, membership or withdrawal fee. Splitrule reads that silence as unstated rather than as zero.

The forms, and where they were read

FEE PER CONTRACT

How much edge does a trade on this venue need before it is worth doing?

An event contract pays a dollar or nothing, which makes the answer exact rather than approximate. A fee of one cent per contract is one percentage point of true probability you have to be right by, on top of the price. So the minimum edge a trade demands is not a matter of opinion or of market conditions. It is the fee schedule, read out loud.

Nothing below reads a market. The prices are a grid of whole cents chosen here, and each figure is a property of the published schedule this page names.

What does going in and coming out cost?

A taker who buys and later sells at the same price has paid the fee twice before being right about anything. That arithmetic decides whether a spread is an opportunity or a bill. The fee is proportional to the price times one minus the price, so it is largest at 50¢ and smallest at the edges.

PriceTaker, heldTaker round tripMaker rebate
5¢0.33¢0.66¢0.06¢
10¢0.63¢1.25¢0.11¢
25¢1.30¢2.61¢0.23¢
50¢1.74¢3.48¢0.31¢
75¢1.30¢2.61¢0.23¢
90¢0.63¢1.25¢0.11¢
95¢0.33¢0.66¢0.06¢

The takeaway. A taker round trip at 50¢ costs 3.48 points of edge on this venue. The maker column is a rebate at every price when its coefficient is negative. A zero coefficient gives no maker rebate. The amounts depend on the selected schedule.

Polymarket US taker: edge needed, hold at 50¢ 1.7375¢

inputs

  • P = $0.50
  • coefficient = 0.0695
  • legs = 1 leg (hold to settlement)

formula

edge = coefficient x P x (1 - P) x legs x 100, in cents per contract

rounding

none. The frontier runs on the unrounded rate. Rounding is per fill, so a per-contract figure with a rounding step would describe one fill size, not a rate

provenance

  • docs.polymarket.us/fees, effective 12 AM ET, Thursday September 17, 2026
  • schedule dated 2026-09-17; read 2026-09-17T14:24:51Z
  • checked daily; last run 2026-09-23, and the Polymarket US fee page matched our recorded read, so this check confirms it is unchanged and keeps no copy of it
  • capture pmus-fees-2026-09-17T14-24-51Z (machine-local), dated reference, not current authority; static capture of the published schedule; 99-row fee table and five worked examples in the bytes

bound

exact on the published terms. A $1 payout makes a cent of fee identical to a point of true-probability edge, so this is the edge the trade demands, not an approximation of it

§ permalink to this receipt
Polymarket US taker: edge needed, round trip at 50¢ 3.4750¢

inputs

  • P = $0.50
  • coefficient = 0.0695
  • legs = 2 legs (in and out at the same price)

formula

edge = coefficient x P x (1 - P) x legs x 100, in cents per contract

rounding

none. The frontier runs on the unrounded rate. Rounding is per fill, so a per-contract figure with a rounding step would describe one fill size, not a rate

provenance

  • docs.polymarket.us/fees, effective 12 AM ET, Thursday September 17, 2026
  • schedule dated 2026-09-17; read 2026-09-17T14:24:51Z
  • checked daily; last run 2026-09-23, and the Polymarket US fee page matched our recorded read, so this check confirms it is unchanged and keeps no copy of it
  • capture pmus-fees-2026-09-17T14-24-51Z (machine-local), dated reference, not current authority; static capture of the published schedule; 99-row fee table and five worked examples in the bytes

bound

exact on the published terms. A $1 payout makes a cent of fee identical to a point of true-probability edge, so this is the edge the trade demands, not an approximation of it

§ permalink to this receipt
Polymarket US maker: edge needed, hold at 50¢ -0.3125¢

inputs

  • P = $0.50
  • coefficient = -0.0125 (a rebate, signed)
  • legs = 1 leg (hold to settlement)

formula

edge = coefficient x P x (1 - P) x legs x 100, in cents per contract

rounding

none. The frontier runs on the unrounded rate. Rounding is per fill, so a per-contract figure with a rounding step would describe one fill size, not a rate

provenance

  • docs.polymarket.us/fees, effective 12 AM ET, Thursday September 17, 2026
  • schedule dated 2026-09-17; read 2026-09-17T14:24:51Z
  • checked daily; last run 2026-09-23, and the Polymarket US fee page matched our recorded read, so this check confirms it is unchanged and keeps no copy of it
  • capture pmus-fees-2026-09-17T14-24-51Z (machine-local), dated reference, not current authority; static capture of the published schedule; 99-row fee table and five worked examples in the bytes

bound

exact on the published terms. A $1 payout makes a cent of fee identical to a point of true-probability edge, so this is the edge the trade demands, not an approximation of it

§ permalink to this receipt

The schedule panel above carries the terms these figures come from, and the rounding rule that decides who is right on a small fill. Run your own numbers on any market’s own page, under the filter.

Fees and programs on other venues

Public fee schedules and incentive programs from the venues' own documents and regulatory filings, checked October 5, 2026. Contracts differ between venues, so equal fees do not make two markets equivalent. A stated scenario cannot establish anyone’s eligibility or rewards.

Myriad

Order-book taker fee

Current. Takers pay feeBPS(p) = peakBPS × min(p, 1 − p) / 0.5 of the trade value. The documented peak is 1.5% at a price of 0.50. Each market publishes its own 100-bucket schedule. Makers pay no fee. No rounding rule is published.

Sources: Order Book (trading guide), read October 2, 2026; API Reference, read October 2, 2026.

AMM fees

Current. Each market sets three fractions of the trade value per side: liquidity providers, treasury and distributor. The guide states 0% to 2% on buys. Shares received depend on pool state.

Sources: AMM (trading guide), read October 2, 2026; API Reference, read October 2, 2026.

Application charge

Current. The venue's own app adds $0.0085 per transaction for blockchain gas. Other interfaces can charge their own frontend fee from 0% to 5%.

Sources: AMM (trading guide), read October 2, 2026; API Reference, read October 2, 2026.

Order-book maker rebate

Active. Described as the arrangement at launch. No end date is published.

Eligibility: Makers whose resting limit orders fill on order-book markets.

Payout: 100% of taker fees revert to makers, paid periodically. The allocation rule, period and minimum are not published.

Limit orders near the midpoint also weigh more in weekly Points distributions. Points are not a cash rebate.

Sources: Order Book (trading guide), read October 2, 2026.

Hyperliquid

Outcome trading fees

Current. Opening a position has no fee. Closing and settlement can carry a fee, but the base outcome rate is not published, and the HIP-4 overview says fees are currently zero for initial testing. A template outcome multiplies any base rate by scale + max(scale, 1). Makers get no rebates. Builder codes can add an interface fee in the quote token.

Sources: Fees: outcome tokens, read October 2, 2026; HIP-4: Outcome markets, read October 2, 2026; HIP-4 deployer actions (labelled testnet-only), read October 2, 2026.

Fee schedules Splitrule does not show

Markets also shows stored market data from OG (Crypto.com), Limitless, Predict.fun, Novig, Kalshi, Opinion, and Pascal. It shows the odds that The Odds API, a data supplier, reports for ProphetX, BetOpenly, Betfair Exchange (UK), and Matchbook. Activity shows the dated public reports of Novig, ProphetX, and ForecastEx. Splitrule calculates no fee for these sources. A market row shows the source’s own fee text when the source gives one, and says so when it gives none.

Ask these questions through Splitrule’s research tools in Claude or ChatGPT

RULES DRIFT

What Polymarket US changed in its own rules text, over 41 intervals, 2026-07-31 to 2026-09-13

Venues publish the rules a market settles by, and they edit them. Nobody publishes the history. This is 41 intervals of that history for one venue, read field by field.

One venue. Every figure below is Polymarket US and says nothing about any other venue. Nothing on this screen is folded together with a reading from anywhere else.

The axis runs from 2026-07-31 to 2026-09-13, joined as 41 intervals from 42 usable captures. The store contains 7 quarantined captures from failed walks. Across the full source history, 4 intervals span 7 quarantined captures. 0 quarantined captures precede the source history, and 0 follow it.

The census is rebuilt daily and this page quotes ONE build of it, named in every receipt.

WHAT MOVED

Wording changed. Resolution sources did not move.

Over 886,138 carried market-intervals, 16316 carried a change of any kind. Wording changed, void language changed, deadlines moved and rules text changed length bracket. Not one market changed the source its outcome is read from.

Wording changed, void language changed, deadlines moved and rules text changed length bracket, and nothing else did Wording changed, void language changed, deadlines moved and rules text changed length bracket, and nothing else did Wording only 13343 Void language 2511 Deadline moved 321 Length bracket 141 13343 Wording only 100.0% of the longest bar, 13343 2511 Void language 18.8% of the longest bar, 13343 321 Deadline moved 2.4% of the longest bar, 13343 141 Length bracket 1.1% of the longest bar, 13343
Every value in the chart above: Wording changed, void language changed, deadlines moved and rules text changed length bracket, and nothing else did
ValueWhat it isShare
13343Wording only100.0% of the longest bar, 13343
2511Void language18.8% of the longest bar, 13343
321Deadline moved2.4% of the longest bar, 13343
141Length bracket1.1% of the longest bar, 13343
Top class per changed market-interval, so the 4 bars are disjoint and sum to 16316. The other 9 classes the extractor can fire are all zero here too.

The day-scale rate is 16152 changes over 775,542 carried market-intervals, in the 33 intervals at least 20 hours wide and measured end to end by one instrument: 2.0827%. An all-interval rate would mix 0.01-hour and 120-hour intervals under one denominator.

One day-scale interval crosses an instrument boundary. Its 144 changes over 15,693 carried market-intervals stay outside the single-era rate. Each interval contributes once, regardless of its transition count. From 2026-08-12T14:30:28.312Z to 2026-08-13T14:30:27.981Z, instrument era 1 to 2: 144 changes over 15,693 carried market-intervals. The registry transition at 2026-08-12T23:11:16Z, era 1 to 2, records VENUE-EDIT. The probe attributes the observed changes to the venue rather than to the instrument change.

Day-scale amendment rate 2.0827%

inputs

  • changed market-intervals = 16,152
  • carried market-intervals = 775,542
  • intervals at least 20h wide, single-era = 33 of 41
  • intervals at least 20h wide crossing an instrument boundary = 1

formula

16,152 / 775,542 = 2.0827%

rounding

four decimal places, display only; the counts are integers and are not rounded

provenance

  • census artifact verification/rules-versions/drift-census.polymarket-us.json, extractor x2
  • built 2026-09-13T15:07:55.052Z by vps, sha256 cfb10665bcca2d15…
  • captures 2026-07-31T22:03:53.939Z to 2026-09-13T14:32:12.073Z, Polymarket US only

bound

a first reading over 41 intervals (2026-07-31 to 2026-09-13) on one venue, and the subset matters: the all-interval rate mixes 0.01-hour intervals with 120-hour ones under one denominator, so it is not quoted here. One day-scale interval crosses an instrument boundary. Its 144 changes over 15,693 carried market-intervals stay outside the single-era rate. Each interval contributes once, regardless of its transition count. Including these boundary counts, the rate is 2.0596%. The adjacent receipt names each capture interval and recorded transition.

§ permalink to this receipt
Changes in one boundary-crossing interval 144 of 15,693

inputs

  • day-scale intervals crossing a boundary = 1
  • changed / carried across them = 144 / 15,693
  • capture interval 2026-08-12T14:30:28.312Z to 2026-08-13T14:30:27.981Z, 24h, era 1 to 2, changed / carried = 144 / 15,693
  • registry transition 2026-08-12T23:11:16Z, era 1 to 2, probe verdict = VENUE-EDIT, cause commits = 540d5d9, 6823258

formula

an interval is a boundary crossing when its two captures fall in different instrument eras; eras come from verification/rules-versions/instrument-boundaries.json. Each day-scale crossing contributes once, even when it contains several registry transitions

rounding

none — counts

provenance

  • census artifact verification/rules-versions/drift-census.polymarket-us.json, extractor x2
  • built 2026-09-13T15:07:55.052Z by vps, sha256 cfb10665bcca2d15…
  • captures 2026-07-31T22:03:53.939Z to 2026-09-13T14:32:12.073Z, Polymarket US only
  • capture interval 2026-08-12T14:30:28.312Z to 2026-08-13T14:30:27.981Z, 24h, era 1 to 2, changed / carried = 144 / 15,693
  • registry transition 2026-08-12T23:11:16Z, era 1 to 2, probe verdict = VENUE-EDIT, cause commits = 540d5d9, 6823258

bound

One day-scale interval crosses an instrument boundary. Its 144 changes over 15,693 carried market-intervals stay outside the single-era rate. Each interval contributes once, regardless of its transition count. From 2026-08-12T14:30:28.312Z to 2026-08-13T14:30:27.981Z, instrument era 1 to 2: 144 changes over 15,693 carried market-intervals. The registry transition at 2026-08-12T23:11:16Z, era 1 to 2, records VENUE-EDIT. The probe attributes the observed changes to the venue rather than to the instrument change. Probe verdicts describe recorded transitions, not a new probe of these capture endpoints. Boundary crossings stay outside the single-era rate regardless of attribution

§ permalink to this receipt
Carried market-intervals 886,138

inputs

  • intervals = 41
  • axis span = 2026-07-31 to 2026-09-13
  • widest / narrowest interval = 120h / 0.01h

formula

one carried market-interval is one market present in BOTH captures of one interval, summed over the 41 intervals; a market added or removed inside an interval cannot have changed across it

rounding

none — a count

provenance

  • census artifact verification/rules-versions/drift-census.polymarket-us.json, extractor x2
  • built 2026-09-13T15:07:55.052Z by vps, sha256 cfb10665bcca2d15…
  • captures 2026-07-31T22:03:53.939Z to 2026-09-13T14:32:12.073Z, Polymarket US only

bound

markets recur across intervals by construction, so this is market-intervals and never markets: the same market carried through all 41 intervals contributes 41. Added 385,196 and removed 306,136 are counted separately and never netted

§ permalink to this receipt
Resolution sources changed 0 of 886,138

inputs

  • SOURCE-SWAP = 0
  • SOURCE-VANISHED = 0
  • SOURCE-APPEARED = 0
  • VOID-LANGUAGE-CHANGE = 2511
  • carried market-intervals = 886,138

formula

SOURCE-SWAP fires when the set of source hostnames in the rules text moves with both sides non-empty; SOURCE-VANISHED and SOURCE-APPEARED read that same set emptying or filling from empty, each while the prose itself remains; VOID-LANGUAGE-CHANGE fires when the frozen void-marker set moves in either direction

rounding

none — counts

provenance

  • census artifact verification/rules-versions/drift-census.polymarket-us.json, extractor x2
  • built 2026-09-13T15:07:55.052Z by vps, sha256 cfb10665bcca2d15…
  • captures 2026-07-31T22:03:53.939Z to 2026-09-13T14:32:12.073Z, Polymarket US only

bound

the extractor reads hostnames and frozen markers out of the prose, so a source that changed without its hostname changing would not fire. It is a floor on stability, not a proof of it

§ permalink to this receipt

Interval by interval, on a date axis. In this chart, 4 intervals span 7 quarantined captures. Outside this chart, 0 intervals span 0 quarantined captures.

2 of the 28 intervals carried no rules change at all

2 of the 28 intervals carried no rules change at all Instrument changed 8 Aug 10 Aug 12 Aug 14 Aug 16 Aug 18 Aug 20 Aug 22 Aug 24 Aug 26 Aug 28 Aug 30 Aug 1 Sep 3 Sep 5 Sep 7 Sep 9 Sep 11 Sep 13 Sep 09 Aug 14:33 (24.05h): 4 markets changed.4 10 Aug 14:30 (23.95h): 13 markets changed.13 10–12 Aug 14:30 (2 days, 48h): 50 markets changed, no usable capture between its endpoints, 1 quarantined capture inside.50 13 Aug 14:30 (24h): 144 markets changed, the census instrument changed inside this interval.144 14 Aug 14:30 (24h): 1 market changed.1 15 Aug 14:32 (24.04h): 2 markets changed.2 16 Aug 14:31 (23.98h): 9 markets changed.9 17 Aug 14:30 (23.99h): 30 markets changed.30 18 Aug 14:30 (24h): 18 markets changed.18 19 Aug 14:30 (24h): 8 markets changed.8 20 Aug 14:30 (23.99h): 5 markets changed.5 21 Aug 14:30 (24h): 5 markets changed.5 22 Aug 15:00 (24.5h): 2 markets changed.2 22–24 Aug 14:30 (47.5h): 3 markets changed, no usable capture between its endpoints, 1 quarantined capture inside.3 25 Aug 14:30 (24h): 61 markets changed.61 26 Aug 14:30 (24h): 3 markets changed.3 27 Aug 14:30 (24.01h): 1 market changed.1 28 Aug 15:01 (24.5h): 21 markets changed.21 28–30 Aug 14:31 (47.5h): 0 markets changed, no usable capture between its endpoints, 1 quarantined capture inside.0 31 Aug 15:47 (25.28h): 26 markets changed.26 01 Sep 14:30 (22.71h): 22 markets changed.22 02 Sep 14:31 (24.02h): 7 markets changed.7 03 Sep 14:31 (24h): 5 markets changed.5 04 Sep 14:31 (23.99h): 13 markets changed.13 05 Sep 14:31 (24h): 8 markets changed.8 05–07 Sep 14:32 (48.01h): 0 markets changed, no usable capture between its endpoints.0 08 Sep 14:32 (24.01h): 12 markets changed.12 08–13 Sep 14:32 (5 days, 120h): 15,766 markets changed, no usable capture between its endpoints, 4 quarantined captures inside.15,766
View chart data
The 28 intervals the chart draws, oldest first: 2 of the 28 intervals carried no rules change at all
Interval (end, UTC, and width)Markets changedNote
09 Aug 14:33 (24.05h)4
10 Aug 14:30 (23.95h)13
10–12 Aug 14:30 (2 days, 48h)50No usable capture between endpoints. 1 quarantined capture inside
13 Aug 14:30 (24h)144Instrument changed
14 Aug 14:30 (24h)1
15 Aug 14:32 (24.04h)2
16 Aug 14:31 (23.98h)9
17 Aug 14:30 (23.99h)30
18 Aug 14:30 (24h)18
19 Aug 14:30 (24h)8
20 Aug 14:30 (23.99h)5
21 Aug 14:30 (24h)5
22 Aug 15:00 (24.5h)2
22–24 Aug 14:30 (47.5h)3No usable capture between endpoints. 1 quarantined capture inside
25 Aug 14:30 (24h)61
26 Aug 14:30 (24h)3
27 Aug 14:30 (24.01h)1
28 Aug 15:01 (24.5h)21
28–30 Aug 14:31 (47.5h)0No usable capture between endpoints. 1 quarantined capture inside
31 Aug 15:47 (25.28h)26
01 Sep 14:30 (22.71h)22
02 Sep 14:31 (24.02h)7
03 Sep 14:31 (24h)5
04 Sep 14:31 (23.99h)13
05 Sep 14:31 (24h)8
05–07 Sep 14:32 (48.01h)0No usable capture between endpoints
08 Sep 14:32 (24.01h)12
08–13 Sep 14:32 (5 days, 120h)15,766No usable capture between endpoints. 4 quarantined captures inside
Each mark counts the markets whose rules text changed between one usable capture and the next. It stands at the capture that closed the interval, and the span under the axis shows the hours that interval covers. 5 of the 28 intervals span 36 hours or more. Their spans are hatched, and each label names the first and last capture dates, and the length in days when the hours make whole days. Each count covers the whole span, not one day. A count over 0.01h and a count over 120h are not comparable. Each interval is stamped with the moment it ended, never the moment it began: the newest interval, 08–13 Sep 14:32 (5 days, 120h), covers the 120 hours before that stamp. The scale tops out at 144 changes, so one bar is cut and marked with a break. Its label carries its full count. Dates are UTC. This chart draws the newest 28 of 41 intervals. The 13 older intervals before them, 2026-07-31 to 2026-08-08, carried 77 changed market-intervals.
Axis depth 41 intervals

inputs

  • captures on the machine = 49
  • viable / quarantined = 42 / 7
  • first capture 2026-07-31, last capture 2026-09-13
  • 20260811T143013 read 1 distinct market against a floor of 10,911
  • 20260823T145057 read 6,500 distinct markets against a floor of 10,911
  • 20260829T143216 read 23,500 distinct markets against a floor of 10,911
  • 20260909T143254 read 100,000 distinct markets against a floor of 10,911
  • 20260910T143316 read 100,000 distinct markets against a floor of 10,911
  • 20260911T143216 read 100,000 distinct markets against a floor of 10,911
  • 20260912T143254 read 100,000 distinct markets against a floor of 10,911

formula

2026-07-31T22:03:53.939Z to 2026-09-13T14:32:12.073Z, joined as 41 consecutive intervals

rounding

the interval count is an integer and the dates are the capture stamps, to the day; interval hours below carry two decimal places, display only

provenance

  • census artifact verification/rules-versions/drift-census.polymarket-us.json, extractor x2
  • built 2026-09-13T15:07:55.052Z by vps, sha256 cfb10665bcca2d15…
  • captures 2026-07-31T22:03:53.939Z to 2026-09-13T14:32:12.073Z, Polymarket US only

bound

The store contains 7 quarantined captures from failed walks. Across the full source history, 4 intervals span 7 quarantined captures. 0 quarantined captures precede the source history, and 0 follow it. In this chart, 4 intervals span 7 quarantined captures. Outside this chart, 0 intervals span 0 quarantined captures. The widest interval in the full source history is 120 hours.

§ permalink to this receipt
Changes in sports 16174 of 16,316

inputs

  • sports carried = 761,534
  • sports changed = 16174
  • culture carried = 23,908
  • culture changed = 0

formula

sports rate 2.1239% over its own carried population, not over the venue's

rounding

four decimal places, display only

provenance

  • census artifact verification/rules-versions/drift-census.polymarket-us.json, extractor x2
  • built 2026-09-13T15:07:55.052Z by vps, sha256 cfb10665bcca2d15…
  • captures 2026-07-31T22:03:53.939Z to 2026-09-13T14:32:12.073Z, Polymarket US only

bound

changes landed in 2 of the 10 categories (sports 16,174, politics 142), and the sports share is nearly uninformative on its own because sports is 85.9385% of the carried population. What survives is narrower: culture carried 23,908 market-intervals and changed none

§ permalink to this receipt

WHAT THIS AXIS CANNOT SEE

38.8360% of the markets this store has ever seen were never carried

A change is only visible on a market present in BOTH captures of an interval. Of the 367,994 distinct markets across 42 captures, 142,914 appear in exactly one, and that one is neither the first capture nor the last. A market seen once is never carried, so no edit to its rules text can fire here. A further 46,094 markets are seen once at one end of the window, where a single appearance says more about the window than about the market, and they are excluded from that count.

Per interval the same bound reads differently, over a different population: 385,196 of 1,271,334 rows in a later capture had no earlier row to compare against, 30.2986%. The first share counts distinct markets across the whole axis. The second counts rows inside 41 intervals. They are two measurements and they do not combine.

Where this venue edits. Every one of the 16316 changed market-intervals sits in 2 of the 10 categories the venue labels (sports 16,174, politics 142). The other 8 carried 36,803 market-intervals between them across the same 41 intervals and changed none. The category label is the venue's own. Splitrule derives no taxonomy of its own from the text.

A changed count does not say what changed. The two movers moved different things: sports — 13342 where wording changed, 2511 where void language changed, 321 where deadlines moved; politics — 141 where rules text changed length bracket, 1 where wording changed. A deadline shift replaces one date or clock token in text that otherwise holds. A length-bracket change is prose that crossed a size boundary while every tracked field held. The count column reads both as one changed market-interval, and the class column is what separates them.

Category (venue label)Carried market-intervalsChangedTop class per change
sports761,53416,174PROSE-EDIT-ONLY 13342, VOID-LANGUAGE-CHANGE 2511, DEADLINE-SHIFT 321
politics87,801142LENGTH-CLASS-CHANGE 141, PROSE-EDIT-ONLY 1
culture23,9080—
macro3,0540—
finance3,0030—
technology2,7670—
crypto2,0290—
climate1,1610—
science4770—
geopolitics4040—

When the changes happened. The 16316 changed market-intervals are not spread evenly across the 41 intervals: sports changed in 35 of them, politics in 1. All 142 politics changes fall in one interval, from 2026-08-12 to 2026-08-13. In the other 40 intervals politics changed none.

Which changes moved a term of the contract. A change counts here when it moved one of four tracked token sets. The four are a source host, a source reference, a deadline or clock token, and a void marker. Sports: 2,832 of 761,534 carried market-intervals. Politics: 0 of 87,801 carried market-intervals.

A zero there is not a finding that a category held still. Politics carries 142 of the 16316 changes in this corpus, and none of them moved a term this instrument reads as a term. Of those, 141 crossed a text-size bracket while all four term sets stayed byte-identical. Text that names no date, host, URL or void marker is consistent with boilerplate. It is equally consistent with an operative sentence this extractor cannot read. The corpus cannot tell the two apart. This is a lower bound on what changed, never an estimate of it.

In 41 capture intervals of Polymarket US rules text — 886,138 carried market-intervals between 2026-07-31 and 2026-09-13 — Splitrule recorded zero resolution-source swaps and zero sources removed or added. All 2,832 term-moving edits it did record sat in sports markets.

Changes that moved a term 2,832 of 886,138

inputs

  • changed market-intervals that moved a tracked term = 2,832
  • changed market-intervals of any kind = 16,316
  • carried market-intervals = 886,138
  • by category = sports 2,832
  • changed and moved no tracked term = 13,484

formula

a change is TERM-MOVING when it moved one of four tracked token sets: a source host, a source reference, a deadline or clock token, or a void marker. Summed over the 41 intervals, 2,832 of the 16,316 changed market-intervals did, over 886,138 carried

rounding

none — counts

provenance

  • census artifact verification/rules-versions/drift-census.polymarket-us.json, extractor x2
  • built 2026-09-13T15:07:55.052Z by vps, sha256 cfb10665bcca2d15…
  • captures 2026-07-31T22:03:53.939Z to 2026-09-13T14:32:12.073Z, Polymarket US only

bound

markets recur across intervals by construction, so this is market-intervals and never markets: a market that moved a deadline in two intervals is counted twice, and the distinct-market count is not this number and is not in the census. It is also a LOWER BOUND on materiality and never an estimate of it: a criterion rewritten in prose that names no new date, host, URL or void marker does not fire, and 141 of the 16,316 changes are exactly that shape: they crossed a text-size bracket with all four token sets byte-identical. That text is consistent with boilerplate and equally consistent with an operative sentence this extractor cannot read, and the corpus cannot tell the two apart

§ permalink to this receipt

Where the Splitrule instrument moved. The day-scale rate above counts 16152 changes over 775,542 carried market-intervals, and every one of them is sports. It contains no politics change. Category absence from that rate alone does not locate its changes in a boundary interval.

One day-scale interval crosses an instrument boundary. Its 144 changes over 15,693 carried market-intervals stay outside the single-era rate. Each interval contributes once, regardless of its transition count. From 2026-08-12T14:30:28.312Z to 2026-08-13T14:30:27.981Z, instrument era 1 to 2: 144 changes over 15,693 carried market-intervals. The registry transition at 2026-08-12T23:11:16Z, era 1 to 2, records VENUE-EDIT. The probe attributes the observed changes to the venue rather than to the instrument change.

Markets never carried 142,914 of 367,994

inputs

  • distinct markets over the whole store = 367,994
  • seen in exactly one capture = 189,008
  • ...of those, in neither the first capture nor the last = 142,914
  • captures joined = 42

formula

a market is CARRIED when it is present in both captures of an interval, and a drift class fires only on a carried market; a market that appears in exactly one capture is therefore never carried and no edit to its rules text can ever fire: 38.8360%

rounding

four decimal places on the share, display only; the counts are exact

provenance

  • census artifact verification/rules-versions/drift-census.polymarket-us.json, extractor x2
  • built 2026-09-13T15:07:55.052Z by vps, sha256 cfb10665bcca2d15…
  • captures 2026-07-31T22:03:53.939Z to 2026-09-13T14:32:12.073Z, Polymarket US only

bound

a market seen once in the FIRST or the LAST capture is an edge effect of where the window stops rather than a market that lived and died between two walks, so the 46,094 of those are counted and excluded from the value. This bounds the instrument, not the venue: the walk reads every open market the catalogue returns, and the same store carries rotating categories whose markets ARE caught when the venue lists them across two walks

§ permalink to this receipt
Rows with nothing to compare against 385,196 of 1,271,334

inputs

  • later-capture rows = carried 886,138 + added 385,196 = 1,271,334
  • rows with no prior row = 385,196
  • intervals = 41

formula

summed over every interval: rows in the later capture of the interval whose market was absent from the earlier one, over all rows in the later capture: 30.2986%

rounding

four decimal places on the share, display only; the counts are exact

provenance

  • census artifact verification/rules-versions/drift-census.polymarket-us.json, extractor x2
  • built 2026-09-13T15:07:55.052Z by vps, sha256 cfb10665bcca2d15…
  • captures 2026-07-31T22:03:53.939Z to 2026-09-13T14:32:12.073Z, Polymarket US only

bound

this is a share of ROWS INSIDE INTERVALS and the never-carried share is a share of DISTINCT MARKETS over the whole axis. The two shares have different numerators, different denominators and different questions. Neither is a restatement of the other

§ permalink to this receipt

Both shares are Splitrule's measurement of its own reach, not a statement about the venue.

ADJUDICATED EVENTS

Every event Splitrule adjudicated, newest first

An event is one thing that happened at one venue, over one named interval, with the cause adjudicated rather than asserted. Each one has its own page, its own permanent address, and a derivation under every number on it.

This feed is a record, not an alert. It says what Splitrule saw and adjudicated. It does not promise to catch the next one, and it monitors no market for any reader. Subscribe at feed.xml.

Events are rare by construction. Splitrule publishes one when a probe adjudicates a cause, and never to fill a page.

SPREAD BY HOUR

How wide has the book been, hour by hour?

Splitrule keeps every scheduled read of the open catalogue. The band below shows the spread by hour of day as quantiles. An hour without a measurement shows as a gap.

The history charts need JavaScript. The numbers behind them are served as plain JSON at /api/history.json, which needs none.

CROSS-LISTED

How many questions on this venue Splitrule has confirmed elsewhere

A confirmed mark means that Splitrule found the same question on another venue. Hover over the count for its denominator, its row limit and its capture. This panel names no other venue and shows no market text or price. A confirmed mark does not establish hedge eligibility.

Cross-listed not read [SERVED DAILY]
source
Splitrule’s daily cross-listing check. Counts only, no market names.
cadence
Daily at 13:20 UTC. Marked stale after 72 hours.
coverage
After a live read, the card adds how many published rows have a confirmed match, and the capture.

What these three words mean

confirmed
The capture found the same question at another venue. The resolution dates agree, and the numbers in the two titles agree when both carry numbers.
unresolved
The capture could not decide. One side published no resolution date, or the two dates fall between the bound that confirms and the bound that rejects.
rejected
The capture found a difference. The two titles carry numbers that do not agree, or the resolution dates are further apart than the bound allows.

DISPUTES

Resolution disputes on record

These incidents come from an oracle system that Splitrule does not cover. The record is collapsed because it gives context, not a reading of this venue. Each entry says which of the two it is.

Open the dispute record

The dispute record needs JavaScript. It is editorial content with public citations.