Research note
N / 260916

Why Does the Polymarket Order Book Suddenly Jump? BTC, TWAP, and Execution Timing

Research on short-horizon Polymarket order-book repricing, BTC spot/TWAP dynamics, and why this information may be more useful for execution than standalone direction prediction.

When automating Polymarket BTC 5-minute trading, one behavior appears again and again:

The order book looks calm—and then the target side suddenly becomes more expensive.

If this happened only occasionally, it could be dismissed as ordinary noise.

But when it appears repeatedly near market boundaries, a more useful question emerges:

Does the relationship between real-time BTC price and the settlement-reference state begin changing before the Polymarket order book reprices?

We recently aligned second-level BTC data, TWAP state, and real Polymarket order-book snapshots to study exactly that.

The result was more interesting than simply asking whether it predicts Up or Down.


1. Two Price States Do Not Move in Perfect Lockstep

For BTC 5-minute research, we separate two layers:

real-time traded price
→ where the market is trading now

TWAP-like reference state
→ a smoothed view of recent prices

They are strongly related.

But they cannot be identical at every instant.

When BTC moves quickly, the real-time market reflects the new level immediately, while a time-averaged state absorbs that change gradually.

This creates:

short-lived divergence between spot and the smoothed reference.

We had already studied whether this divergence contains information about later market structure.

The new question was different:

Does it relate to how the Polymarket order book reprices?


2. Order-Book Jumps Are Not Completely Random

After aligning the data, one high-level relationship appeared consistently:

When the real-time market moves materially relative to the smoothed reference state, the target side of the Polymarket order book often reprices as well.

The most useful interpretation is not long-horizon forecasting.

It is:

very short-horizon execution behavior.

This looks more like:

the market is repricing now

than:

the next market must resolve UP

Those are very different claims.


3. Why This Looks More Like an Execution Signal

Suppose a Polymarket bot has already produced a direction using its full strategy.

It now has another decision:

Buy now, or wait?

If the market is relatively calm, waiting may still have value.

More information can develop while the execution price remains reasonable.

But if the real-time market has started moving rapidly in the target direction and the order book is following, waiting may simply make the same exposure more expensive.

So the microstructure information may be most useful for answering:

Has execution become urgent?

not:

What is the trading direction?


4. Why It Should Not Be Turned Directly Into a Direction Rule

In a short sample, rapid market movement often aligns with the eventual result.

That creates an obvious temptation:

If it can anticipate repricing, can it directly predict the final outcome?

Multi-year validation does not support such a simple conclusion.

Markets can:

  • continue after a fast move;
  • reverse;
  • temporarily overprice;
  • behave differently across volatility regimes.

So:

explaining why the order book jumps

and

predicting how the five-minute market will resolve

are different tasks.

A microstructure feature can be useful for the first and only modestly informative for the second.


5. Why the Problem Becomes More Important Near the Boundary

Far from the boundary, the bot has time.

A short-lived repricing can reverse or normalize.

Closer to the boundary:

  • there is less time to recover;
  • consensus can form faster;
  • cheap liquidity can disappear quickly;
  • one rapid repricing event can materially change execution cost.

That connects directly to our separate execution-cost research:

Effective entry cost tends to become more sensitive as the market approaches the boundary.

Order-book jumps and entry-cost inflation are two views of the same execution problem.


6. What Can This Research Actually Help With?

At the moment, we see three practical research directions.

1. Execution urgency

After a direction already exists, estimate whether the system should act more quickly.

2. Wait-or-act decisions

Estimate whether waiting a little longer still has value.

3. Confirmation

Use short-horizon market movement as supporting evidence around an existing decision—not as a replacement for the full strategy.

These are:

execution and confirmation tasks.

They are not a new standalone directional strategy.


We also checked the short-horizon movement structure using different reference sources.

Their absolute levels are not identical.

But the short-term movement patterns were similar enough to suggest that the observed repricing relationship was not simply an artifact of one reconstruction method.

That does not mean the sources are interchangeable.

The traded market and the settlement reference still represent different layers.


Conclusion

This research did not produce a “formula for predicting order-book jumps.”

It produced a more practical insight:

Some microstructure information may be valuable not because it tells a bot which side to buy, but because it tells the bot when waiting is becoming expensive.

That matters for Polymarket automation.

A production system ultimately has to deal with more than:

prediction

It has to deal with:

prediction
→ participation
→ execution
→ a live order book that keeps moving

Separating those problems may be more useful than searching for one universal directional indicator.



Disclaimer: This article publishes only aggregated market-microstructure findings. It does not disclose production trigger conditions, time windows, thresholds, weights, or execution parameters.