PR&R / Research
Home / Guides / TWAP Settlement
Polymarket / Crypto

Polymarket's TWAP Settlement: Data & Strategy Analysis

From 7 August, Polymarket's crypto up/down markets stop settling on one closing price. They settle on a 30 or 60 second average instead. We re-priced 140,396 real markets to see what that changes. If you are winning at 90¢ with 30 seconds left, you used to lose 1 market in 50. Under the new rule, about 1 in 380.

Effective Aug 07, 2026 ~12 min read By PR&R Research View the datasets →
What the change is worth if you are already winning

Measured on real Polymarket order books from June 2026, across BTC, ETH, SOL, XRP, BNB and DOGE.

These are estimates. No TWAP-settled market has traded yet, so this is our reconstruction of what would have happened. Polymarket published the window lengths, 30 and 60 seconds, but not where the window starts and stops, so we assume it covers the last 30 or 60 seconds before the close. The numbers above come from a random sample of June, not from every market. Treat them as a good guide to the size of the change, not as exact odds.

// 001 / Overview

What is changing, and what we measured

The rule, the cutover date, and the headline numbers from four rebuilt months.

These markets all ask one question: is the coin higher or lower than when it opened? That doesn't change on 7 August. Nor does the opening price, or the payout. The only thing changing is which number gets compared to the open. Swap that one number and about 1 in 16 markets pays the other side.

Effective 7 August 2026, 00:00 UTC 5-minute markets settle on a 30-second average. 15-minute and 4-hour markets settle on a 60-second average. The window lengths are confirmed. Chainlink hasn't published the feed's sampling boundaries, so the exact window edge is an assumption, and we flag it everywhere it matters.

Nobody has traded a TWAP-settled market yet, so there's no history to backtest. What we do have is two months of real order books, June and July 2026, across six coins. We took all 140,396 of them and re-priced them under the new rule. The books are real. The settlement rule is the only thing we changed.

Most coverage of this says it stops manipulation. True, but that undersells it. The useful part is where the risk actually sat. Almost all of it was in markets finishing within a basis point or two of the open. If you were more than 10 bp ahead with ten seconds to go, this change does nothing for you.

Work through the sections on the left, or skip to the simulation and watch a cycle run one second at a time.

// 002 / What changes

A single price becomes an average

One number decides the old rule. Thirty numbers decide the new one.

TWAP means time-weighted average price. Instead of reading the price once, you read it every second for a while and take the average. That is the entire change.

Every one of these markets asks the same question: is the coin higher or lower than when the market opened? That does not change. The opening reference does not change. The payout does not change. The only thing changing is which number you compare against the open.

Both rules watch the same market A 5-minute BTC market opens at $62,000 The price wanders for five minutes. In the final second a large order pushes it up.
Until 7 Aug

Read ONE number

The settlement price is whatever the coin prints at the exact moment the market closes. One number decides it.

$62,050

That is $50 above the $62,000 open.

UP WINS
From 7 Aug

Average THIRTY numbers

The settlement price is the average of the coin's price across each of the final 30 seconds. Thirty numbers decide it.

$61,992

That is $8 below the $62,000 open.

DOWN WINS
The same shape on a real market: DOGE, 5 minutes, 10 June 2026
coin price, bp from openclose +8.4 bp30s avg -7.7 bp0.00.51.0share price — Up and Down, both rulesdashed = SNAPSHOT · solid = TWAPNEW → DOWN WINSOLD → UP WINS0s75s150s225s300s
Same market. Same prices. Opposite payout. The one-second spike decides the old rule; it is 1/30th of the new one.
// 003 / The settlement math

Two formulas, no model

Who wins is pure arithmetic. Nothing here is estimated.

In symbols: P(t) is the coin price at second t, the market opens at P(0) and closes at second C (300 on a 5-minute market, 900 on a 15-minute one). The averaging window is the last W seconds, either 30 or 60.

Deciding who wins needs no model at all. It's arithmetic:

OLD settlement priceSsnap = P(C)
NEW settlement price Stwap = ( P(C−W) + … + P(C−1) ) / W
Winner, either ruleUp if S > P(0), otherwise Down

That's the whole of it, and nothing in it is estimated. We ran both formulas over every cycle in our archive and compared the winners. That's where 6.22% and 4.35% come from.

The harder question, what the order book would have looked like, does need a model, because nobody ever quoted these markets under the new rule. That's the next section.

// 004 / How we rebuilt the books

Moving a real book onto a new rule

Nobody quoted these markets under TWAP, so we shifted the real book instead of inventing one.

Nobody ever quoted these markets under the new rule, so there is no real book to show. Rather than invent a theoretical one, we move the real one:

Simulated Up real_Up(t) + [ fairtwap(t) − fairsnap(t) ]
Simulated Down real_Down(t) − [ fairtwap(t) − fairsnap(t) ]

The bracketed term is the only thing that moves: the shift. Everything the real market got wrong (its spread, its lag, its bias, its depth) carries across untouched, because it is still the same book, just re-centred on a new rule.

The shift itself comes from asking, at each second and under each rule, what is the chance Up wins given only what has happened so far? Under the snapshot rule the best forecast of the settlement price is simply the current price. Under TWAP, once you are inside the window, part of the average is already locked in. Those seconds have happened and cannot change. That single fact is what drives everything that follows.

The shift is quantised, not the price Tick size on Polymarket is set per market and can change while a market is live, so a bot has to read it rather than hardcode it. In the crypto up/down books we captured, every quote sits on a 0.001 grid spanning 0.001 to 0.999, so that is the grid we snap to. Rounding the shifted price would corrupt the spread and the ladder spacing, so the shift is snapped and added whole. The book keeps its exact structure and only its centre moves.
// 005 / Reversal risk

Almost all of the risk sits in a small band

How often a market you have already called still pays the other side.

About 6% of markets reverse. That average hides the shape completely. Reversals sit almost entirely in markets that finish close to the open. Across the 11,496 markets we sampled from five June days, of the 448 that moved 50 bp or more, not one reversed. The biggest move that still reversed was 31.6 bp.

The tables on this tab and the next come from that five-day sample, so they run slightly hotter than the full month: 6.40% and 4.71% here, against 6.22% and 4.35% across all of June.

Reversal risk as the market runs down5-minute markets
0%4%9%14%18%OLD rule 2.10%NEW rule 0.00%90s left67s left45s left22s left1s left
At each point: if you called the winner right now, how often would the market settle the other way? The axis stops at 1 second left. There is nothing to plot at zero, because by then the market has settled.
Reversal risk as the market runs down15-minute markets
0%3%6%9%12%OLD rule 1.88%NEW rule 0.00%120s left90s left60s left30s left1s left
Time left5m, OLD5m, NEW 15m, OLD15m, NEW
30 seconds10.40%5.04%5.47%1.60%
10 seconds5.64%1.03%3.45%0.17%
5 seconds3.70%0.21%2.58%0.03%
1 second2.10%0.00%1.88%0.00%
Read the bottom row twice. With one second left to trade, a call under the old rule was still wrong 2.10% of the time, roughly one in every 48, because the old rule settles on a price that hasn't happened yet. Under the new rule the same call is wrong 0.00% of the time: 29 of the 30 averaged seconds are already fixed, and for the last one to overturn the result it would have to move about 258 bp, roughly 29 times a typical 5-minute move. It never happened once in 8,628 cycles.
// 006 / Who it actually affects

The average falls apart into something usable

Reversals are not spread evenly. Almost all of them sit in one narrow band.

The headline figures on the previous tab are unconditional: every cycle counted once, knife-edge markets mixed in with markets that were decided two minutes ago. Once we split that same moment by how far the price had actually travelled, the average falls apart into something you can trade on.

Distance from open, 10s leftCyclesShare OLD reversesNEW reverses
under 1 bp, a coin flip5436.3% 34.62%9.21%
1 – 2 bp5896.8%22.92%3.90%
2 – 5 bp1,53617.8%8.72%0.91%
5 – 10 bp2,15024.9%1.26%0.09%
10 – 20 bp2,21825.7%0.14%0.00%
over 20 bp, already decided1,59218.5%0.00%0.00%
all cycles (the headline)8,628100% 5.64%1.03%

If your position is more than 10 bp ahead with ten seconds to go you were already safe under the old rule and the change does nothing for you. If it is under a basis point ahead, you were facing a 34.62% chance of losing a position you thought you had won, and the new rule cuts that to 9.21%.

// 007 / True edge

One number a bot can trade on

What the market charges versus what actually happens from a position like this.

Everything above reduces to a single comparison: what the market is charging you versus what actually happens from a position like this. The difference is the edge.

1. Which side is ahead the side the PROJECTED settlement favours
2. What the market chargesimplied_p = price of that side
3. What history says p_twap = P(leader wins | timeframe, seconds left, projected distance)
4. The edgetrue_edge = p_twap − implied_p
5. Upside if right1 − implied_p
Step 1 is where a naive implementation goes wrong. Key it on the projected settlement, (locked seconds + current price for the rest) / W, not on the spot price. During a late reversal spot sits above the open while the projection sits below it, so keying on spot inverts the answer exactly on the cases that matter most.
Read these grids as estimates These are the least certain numbers in the article, for three reasons. They're measured on a five-day sample of June (11,496 markets), not the full two months. They assume the averaging window is the last 30 or 60 seconds before the close, which is the part Chainlink hasn't published. And they're measured on order flow that traded under the old rule, so they describe the price path, not how anyone will quote once the rule changes. Treat a cell as a guide to the shape, not a number to size a position on.
P(leading side wins) under TWAPEstimated, 5-minute
5-minute marketshotter = the leader is safer · columns are the PROJECTED settlement's distance from the open<1 bp1-2 bp2-5 bp5-10 bp10-20 bp20+ bp90s left53.0%63.1%72.5%87.3%96.1%98.9%60s left55.8%62.6%81.2%93.4%98.1%99.7%30s left65.6%80.5%92.7%99.2%99.9%99.9%20s left74.3%90.1%97.8%100.0%100.0%100.0%10s left87.2%98.3%99.8%100.0%100.0%100.0%5s left96.2%99.9%100.0%100.0%100.0%100.0%2s left98.8%100.0%100.0%100.0%100.0%100.0%P(leader holds)50.0%100.0%
Every cell here is built from at least 2,673 observations, so the broad shape is solid. Individual cells still move by a few tenths of a point run to run.
P(leading side wins) under TWAPEstimated, 15-minute
15-minute marketshotter = the leader is safer · columns are the PROJECTED settlement's distance from the open<1 bp1-2 bp2-5 bp5-10 bp10-20 bp20+ bp180s left53.3%58.0%70.9%83.0%92.8%98.5%120s left56.9%70.3%76.7%88.6%96.0%99.0%60s left55.0%70.8%88.5%98.1%99.9%99.9%30s left71.9%91.8%98.5%99.8%100.0%100.0%20s left79.1%98.4%100.0%100.0%100.0%100.0%10s left95.3%100.0%100.0%100.0%100.0%100.0%5s left99.3%100.0%100.0%100.0%100.0%100.0%2s left99.8%100.0%100.0%100.0%100.0%100.0%P(leader holds)50.0%100.0%
Read down the column for your projected distance from the open, across to your time remaining. The 15-minute grid hardens earlier in relative terms because a 15m market at 30 seconds left already has half its window locked, while a 5m market has none. This grid is the thinner of the two: its smallest displayed cell rests on 493 observations, so the extreme corners carry real sampling noise.
Worked example · 5-minute market · 30 seconds left · dominant side at $0.90
1Which side is ahead? the projected TWAP leader, 5–10 bp clear
2What is the book charging? $0.90  →  implied 90.0%
3What does history say? 99.25%
TRUE EDGE 99.25% − 90.00% = +9.3 points
4Upside if you are right $0.10 on $0.90  →  +11.1% on stake
Signal BUY

The same position one minute earlier, at 60 seconds left with the same 5 to 10 bp lead, is only worth 93.4%, which makes $0.90 a +3.4 trade barely worth the spread. The edge is created by the window opening, not by the price.

Should you take this quote?True edge in points, 30s left, 5-minute
True edge in points, 30 seconds left, 5-minute markethotter = better trade · dark = the book charges more than history justifies<1 bp1-2 bp2-5 bp5-10 bp10-20 bp20+ bpbook at $0.80-14.4+0.5+12.7+19.2+19.9+19.9book at $0.85-19.4-4.5+7.7+14.3+14.9+14.9book at $0.90-24.4-9.5+2.7+9.3+9.9+9.9book at $0.93-27.4-12.5-0.3+6.2+6.9+6.9book at $0.95-29.4-14.5-2.3+4.3+4.9+4.9book at $0.97-31.4-16.5-4.3+2.3+2.9+2.9edge = history − price-31.4+19.9
Above roughly 5 bp clear the edge is nearly the whole gap to $1. Below 2 bp there is almost never an edge: at $0.90 with a sub-1 bp lead you are taking a −24.4 point trade, because the market is nowhere near decided and the book is charging you as if it were.
// 008 / Build it into your bot

The formulas, and code you can paste

Two calculations. One runs from the open, one runs every second of the window.

There are only two calculations, and neither needs a model. The first tells you what the market is heading for. The second tells you how much it would take to change it.

Try it

Drag the marker through a made-up BTC cycle. Watch the formula fill in as the averaging window swallows more of the outcome, and note what happens to the projection when the price spikes in the last few seconds.

Fictional BTC 5-minute market opens at $62,000
61,44961,75862,06862,377 open $62,000 the 30s that get averaged 0s75s150s225s300s
Drag to move through the cycle. The shaded strip is the 30 seconds that get averaged.
Coin price Opening price, the line that decides the winner Where the settlement is currently heading
270s30 seconds left
Price right now 
Seconds locked in 
Seconds still to come 
projected settlement
 
 
vs the $62,000 open 
 
 
Settles at$61,74930-second average
Old rule would settle at$62,254the closing price
ResultUp under the old rule, Down under the new one

1. The projection, every second

Before the averaging window opens, the best guess at the settlement price is just the current price. Once you are inside the window, the seconds that have already passed are fixed. They cannot change. Only the seconds still to come ride on where price goes next, and your best guess for those is also the current price:

Before the windowprojected = price
Inside the window projected = ( locked_sum + price × seconds_still_to_come ) / W
Who is winningUp if projected > open, otherwise Down

locked_sum is just a running total: add the price once per second from the moment the window opens. W is 30 on a 5-minute market, 60 on a 15-minute or 4-hour one.

This is the part people get wrong Key your signal on projected, never on spot. During a late reversal spot sits one side of the open while the projection sits the other side. That is the exact case this rule change exists to handle, so keying on spot inverts your answer precisely where it matters most.

2. What it would take to flip

With k seconds locked and W−k to go, the remaining seconds would have to average this for the other side to win:

Required average ( W × open − locked_sum ) / ( W − k )

Compare that to a normal move for the coin. On the DOGE cycle in the simulation, with 2 seconds left the price needed to travel 231 bp to change the result, against a typical 5-minute move of about 9 bp. That market was decided, whatever the book said.

3. Turning it into a probability

The projection tells you who is ahead, not how safe they are. For that we ship the measured table straight out of this study: for a given seconds-remaining and distance from the open, the share of real June cycles where the leading side went on to win. Look up your row and column and compare it to what the book charges. That difference is your edge.

A closed-form alternative is in the code below, but it is worse. Against the measured numbers it is off by about 3 points on average and up to 16 at the extremes, because a plain random walk understates how often a big lead survives early and overstates how safe a thin one is late. Use the table where you have it.

What about the first 5, 10 or 15 seconds?

Honest answer: at that point the settlement average has not started, so your best estimate of it is simply the current price. There is no early signal hiding in the opening seconds. What they are good for is the volatility estimate you feed into everything else, and the spread of the book while it is still cheap to get filled. The edge in this rule change lives in the last W seconds, not the first.

Paste-ready Both files are dependency-free and carry the measured table inline, about 6 KB. Python: twap-report/tools/twap_estimator.py   JavaScript: twap-report/tools/twap-estimator.js
Verified against all eight worked cycles in this article: the projection converges to the settled TWAP exactly, and both versions agree to floating-point.
The loop, in nine lines
1est = TwapEstimator("5m", open_price) once, at the open
2s = est.update(t, price) once per second
3s.projected where it is heading
4s.leader Up or Down
5s.p_leader measured chance that holds
s.edge(book_price) p_leader − what you pay
Trade when edge > your threshold
Before you size anything on this The probability table is measured on a five-day June sample under the OLD rule's order flow, and the whole thing assumes the averaging window is the last 30 or 60 seconds before the close, which Polymarket has not published. The projection itself is exact arithmetic and does not depend on that assumption; the probabilities do. Paper-trade it first, and test what happens to your edge if the window shifts by a second either way.
// 009 / Simulation

Watch the edge appear, tick by tick

Pick a market, press play, and watch both order books diverge as the window fills.

Pick a market and press play. The cycle runs one tick per second: the first chart draws the coin price, the second draws both order books at once. The dashed lines are the book priced for snapshot settlement, the solid lines are the same book priced for TWAP. The strip above recomputes every tick from the measured table, so you can watch the edge open up as the window fills.

Try DOGE · 5m and scrub to the last ten seconds: spot goes above the open while the projected TWAP stays below it, the book is still lagging at 0.87, and the signal fires.

0s
Projected TWAP vs open
Spot vs open
Book price (implied p)
Historical TWAP p
True edge
Upside if right
Signal
Coin price, basis points from the open  
Both order books: Up and Down dashed = SNAPSHOT · solid = TWAP
// 010 / Examples

Eight real cycles, before and after

Measured data. The dashed lines traded, the solid lines are the same book re-priced.

Every panel below is measured data. The faded lines are the real order book as it traded; the solid lines are the same book re-priced for the TWAP rule.

DOGE · 5m · late-cycle reversalSnapshot vs TWAP
0.00.51.0Down 0.99Up 0.010s75s150s225s300s
The books track each other almost exactly for four and a half minutes, because the rule change does nothing, then they tear apart inside the window. Up ends at 0.89 under the old rule and 0.01 under the new one.
ETH · 15m · late-cycle reversalSnapshot vs TWAP
0.00.51.0Down 1.00Up 0.000s225s450s675s900s
SOL · 5m · decisive trend (control)Snapshot vs TWAP
0.00.51.0Down 1.00Up 0.000s75s150s225s300s
The control case. A one-way market moved 175 bp and both rules agree, so the two books are visually identical. If the transform distorted decisive markets, it would show here.
MarketDateSnapshot (bp)TWAP (bp) Snapshot winnerTWAP winnerChanged
DOGE · 5m2026-06-10+8.34-7.68UpDownyes
ETH · 5m2026-06-17-17.88+1.50DownUpyes
BTC · 5m2026-06-18+0.00-0.27UpDownyes
SOL · 5m2026-06-17-175.18-166.20DownDownno
ETH · 15m2026-06-10+31.55-2.94UpDownyes
SOL · 15m2026-06-12-0.03+3.59DownUpyes
DOGE · 15m2026-06-12+219.21+208.68UpUpno
XRP · 15m2026-06-10+13.53-8.84UpDownyes
// 011 / Caveats

What this does and does not show

The assumptions, the limits, and what the underlying datasets actually are.

  • Spreads do not tighten here. Under TWAP market makers face far less end-of-cycle gap risk, and Polymarket is adding $1M in liquidity rewards to encourage tighter quotes. These books hold spreads at their observed values, so any strategy that pays the spread will look worse here than it should after August. Treat backtested spread costs as a floor, not an estimate.
  • No behavioural response is modelled. This is the same order flow re-priced, not a simulation of how traders will act once the rule changes. Everyone gets this arithmetic; the lock-in edge is real but it is not proprietary and it will compress.
  • The window edge is an assumption. The lengths (30s and 60s) are confirmed. Chainlink does not publish the feed's sampling boundaries, and whether the market open also becomes an average is unstated. A strategy whose edge lives entirely in the last second or two of the window is resting on an unverified detail. Test its sensitivity to a ±1 second shift before sizing it.
  • The closing second is an assumption too. The old rule reads one price at the close, and the feed does not say whether that is the last second inside the cycle or the first tick of the next one. On a quiet close it makes no difference. On a violent one it decides the market. We rejected one candidate example for this article because 78% of its move landed in its final second, so which of the two seconds you read flipped its result. Every example that survived was re-tested against both readings and against shifting the averaging window five seconds either way. If your edge depends on that single tick, it is resting on something nobody has published.
  • The probability tables are measured under the old rule's order flow. The price path is rule-independent, so the arithmetic holds, but the thinnest cells (under 1 bp, few seconds left) rest on a few hundred samples. Treat that column as directional.

Where each claim comes from

Checked against Polymarket's own documentation on 3 August 2026. We have split this by what the docs actually confirm, because two of the numbers this article leans on are not in them.

ClaimStatusSource
TWAP windows of 30 and 60 seconds existConfirmed Polymarket docs, Chainlink TWAP
Chainlink does not publish the feed's sampling boundaries, weighting, rounding or missing-input behaviour, and warns against reproducing the value without a spec Confirmed, quoted verbatimPolymarket docs, Chainlink TWAP
RTDS, the real-time data service, launches 4 August 2026Confirmed Polymarket docs, Chainlink TWAP
Tick size is per market, changes while a market is live, and must be read rather than assumedConfirmedPolymarket docs, Place Orders
5-minute markets use the 30s window; 15-minute and 4-hour use the 60s window Not in the docs. From the announcement and press coverage Polymarket Devs announcement
Settlement changes at 00:00 UTC on 7 August 2026 Not in the docs. From the announcement and press coverage Polymarket Devs announcement
The averaging window is the last W seconds strictly before the close Our assumption. This is the exact thing Chainlink says it has not published PR&R
The market open stays a single snapshot rather than becoming an average Our assumption. Not addressed anywhere in the docsPR&R
Quotes in these books sit on a 0.001 grid, 0.001 to 0.999 Measured on our own capture, not a documented constantPR&R
Every reversal, probability and order-book figure in this article Measured from the datasets described belowPR&R
The two that matter most The window mapping and the cutover date both come from Polymarket's announcement rather than its technical documentation, and the window edge is ours. If any of the three turns out differently, the arithmetic in this article still holds but the numbers move. Re-check them against the docs before you trade on this.
Sources Polymarket documentation, Chainlink TWAP Prices · Real-Time Data · Place Orders · Orderbook. Announcement via Polymarket Devs, corroborated by Crypto Briefing and Prediction News. All checked 3 August 2026.
Underlying data. Four rebuilt datasets covering June and July 2026 across BTC, ETH, SOL, XRP, BNB and DOGE, at both the 5-minute and 15-minute timeframes. Labels come from Polymarket's own RTDS settlement feed, with Binance-derived alternates shipped alongside so the source choice stays a visible column rather than a decision buried in a script.
Join Discord