Deep Web3

SYSTEMS.
PEOPLE.
POSSIBILITIES.

Menu

Go beneath
the surface.

Polymarket’s Nex matching engine: faster internal benchmarks, but no live cutover yet

As reported on November 13, 2026, Polymarket engineering VP Josh Stevens said its new matching engine, Nex, had run in shadow mode against production traffic for one week. Written from scratch in Rust, Nex was still being tested rather than serving as the live replacement for Polymarket’s existing central limit order book (CLOB) engine.

Stevens reported substantial gains in internal tests. The figures below are internal benchmarks, not independently verified production results:

Measure Existing system Nex
p99 order-placement latency 1.55 seconds 3.76 milliseconds
Order-cancellation latency 627.92 milliseconds 3.20 milliseconds
p99 WebSocket write latency 44.5–88.1 milliseconds 0.099 milliseconds
Steady-state instruction throughput 10,000 per second 100,000 per second
Startup time 5 minutes 15 seconds

Stevens also put Nex’s peak throughput at 150,000 instructions per second. He said its deterministic design eliminates race conditions present in the old system and that request and response formats will not change in a breaking way for market makers or developers. Those design claims, like the performance figures, were reported by Stevens; the notice provides no independent test methodology.

At the time of the report, the plan was to keep Nex in shadow mode for another four weeks and, if testing went well, launch it in mid-December. WebSocket improvements might arrive earlier. Polymarket had also opened a Nex sandbox for user testing. Neither the planned launch nor the benchmark gains should be read as a confirmed outcome of a live cutover.