Prathwik retweeted
JUST IN: Riemann Hypothesis has been solved.
alpo.ge/remark.pdf
Prathwik retweeted
How you present your work, how you talk about it, even how you present yourself has always mattered. But today, it’s what sets you and your product apart.
A great product alone isn’t enough anymore.
Excited to try out the new CLOB!
The performance numbers look very promising. Hopefully no more bugs!
At the end of August, I said our Polymarket DeFi CLOB couldn't be saved, and we were rewriting it from scratch in Rust 🦀
Today I'm excited to announce Nex, our new exchange built from the ground up.
We've been sprinting on it since August. A Nex instance has been running in shadow mode on production traffic for the last week, side by side with the current exchange. It mirrors every order the current exchange gets, so we can measure latency, stability under load, and validate matching correctness against live production flow.
The numbers below are internal exchange timings, not e2e (those are coming soon), but we wanted to show how big the difference is.
p99 current CLOB → Nex:
- Place order: 1.55s → 3.76ms (412x faster)
- Cancel orders: 627.92ms → 3.20ms (196x faster)
- Cancel market orders: 810.16ms → 5.14ms (158x faster)
- Cancel all*:
↳ Response (current CLOB) vs complete (Nex): 35.70ms → 3.14ms (11x faster)
↳ Full cancel all: ~636ms-2.04s → 3.14ms (~200-650x faster)
p95 current CLOB → Nex:
- Place order: 341.84ms → 1.59ms (215x faster)
- Cancel orders: 78.22ms → 1.58ms (50x faster)
- Cancel market orders: 84.89ms → 2.27ms (37x faster)
- Cancel all*:
↳ Response (current CLOB) vs complete (Nex): 6.20ms → 1.58ms (4x faster)
↳ Full cancel all: ~606ms-2.01s → 1.58ms (~380-1,270x faster)
*Cancel all: the current CLOB responds immediately and cancels in the background, so when you get the response, your orders aren't cancelled yet. Nex responds only after everything is actually cancelled. Full cancel all on the current CLOB depends on how many orders you have, but it usually adds another 600ms-2s.
We also rewrote our WebSockets in Rust. This is the feed you see the market through: book changes, price moves, your fills. Fall behind it, and you're trading on old prices, and your quotes get picked off.
- Write latency p99: 44.5-88.1ms → 0.099ms (~449-889x faster)
- Slow readers/sec: 48.7-75.6 → 0.01 (~4,870-7,560x fewer, basically 0)
Scale: The current CLOB in stable state can handle 10k commands/s with 15k bursts → Nex can handle 100k commands/s with 150k bursts. 10x more, and with a few optimisations we can get to 200k commands/s with 250k bursts; with more low-level core changes, we can get to 1M commands/s over the next year. Not needed yet, but the headroom is there.
Startup time: 5 mins → 15s (20x faster)
The old CLOB had many race conditions and wasn't deterministic. Nex is deterministic by design and removes the race conditions in the old CLOB.
We also skipped some easy wins for launch to get this out faster that could make p95 and p99 another 5x faster, and we'll start work on that in Q1 next year to keep pushing these numbers down.
We wanted to build this without any breaking changes for MMs or builders; Nex has no breaking changes to requests or responses, so we just need to swap out the binary on our side and it will go live.
We want everyone to be on this journey with us, with the ability to relay feedback and test it against the existing CLOB, so we've opened a Nex Sandbox. Fill out the form and test it yourself: docs.polymarket.com/nex
We'll run 4 weeks of shadow mode on production traffic to make sure everything is perfect, then if everything is good, we will go live mid-December. We can roll out WebSocket improvements without the full exchange, so we may do that sooner.
We've been rebuilding every system around the exchange for months, and we've seen huge benefits, but the exchange is the heart of Polymarket DeFi. Nex fixes most of the pain traders have had.
Really proud of the team on this one.
Make Polymarket fast, finally. It's coming.
1
13
402
Prathwik retweeted
After a year of trading, I'm finally in the prediction market millionaire club -- and then some.
In the midterm elections I printed over $370,000, for a +50% gain on my portfolio.
I started with $20K and zero trading experience. Thanks to everyone who's joined me on this weird journey. ❤️🪿
Prathwik retweeted
Just arrived in Mumbai!
Looking forward to seeing familiar faces and new faces and all the wonderful Ethereum and open/secure/private/decentralized tech projects that everyone is working on over the next week.
Prathwik retweeted
Polymarket Incident Breakdown (Oct 29)
We have traced 2.724M pUSD across 721 source wallets in transactions paying the recipient embedded in a DebugBear-hosted drainer.
1. The Payload & Delivery: The malicious code was served from [cdn.debugbear.com/C7xcKKrjUn…](cdn.debugbear.com/C7xcKKrjUn…) inside the real DebugBear namespace.
2. Attack Mechanism (Browser-Side Compromise)T
The script reads Polymarket wallet/auth state, walks React internals to hook the live trading client and signer, and uses EIP-712 DepositWallet batch signatures alongside Polymarket’s own relayer. No seed-phrase extraction occurs in this payload.
It executes via two theft paths (targeting portfolios and positions over $10):
External wallets: Positions are transferred directly.
Magic accounts: Positions are sold first, then collateral is swept.
3. Routing & On-Chain ProofThe coded route stays on Polygon (pUSD → USDC.e → POL or USDC → recipient) using quotes via api.fun.xyz, with a direct USDC.e transfer as a fallback.
4. Money Trail
18:17 UTC: Embedded recipient 0x3F991...Ffc18 held 28.636M POL (representing converted proceeds, not a separate loss total) and forwarded 25 position IDs to 0x5a276...0c0b.
18:21 UTC: The second wallet (0x5a276...0c0b) sold/redeemed those positions and held 4,262.36 pUSD.
5.Polymarket’s public production build at 17:59 UTC includes "remove debugbear rum script", confirming removal in the observed build.
More data coming
Polymarket users are being drained!
Leading theory on the cause is a security breach of DebugBear. Polymarket loads their scripts on the frontend
Trading is currently paused
2
10
558
Affected users will be refunded according to Polymarket
xitter.gq/PolymarketTrade/status…
We've identified & fixed an issue impacting our international platform, Polymarket.com. One of our 3rd party providers was compromised, and we have referred this to relevant law enforcement.
Anyone who has been impacted will be made whole.
Out of an abundance of caution, we have temporarily halted trading & are working to bring the platform back online.
1
3
154
During the time I spent away from X, I adopted Stevie with a friend.
He’s a Shih Tzu cross breed dog and he’s soo adorable and soo much fun.
8
16
584
Prathwik retweeted
Polymarket WebSocket freezes, explained.
We ran 4 clients side by side for 32.3 hours on 20 markets and checked every trade against the Data API.
Here's what broke 🧵
Another warning to never install anything unless you trust it entirely, especially if you're into Crypto
This was more sophisticated than typical scams as it uses an established Steam game to drain your funds
Stay safe out there!
Prathwik retweeted
It's kinda funny that the only site my money wasn't safe on was @Polymarket.
The hacker couldn't drain my @Kalshi money because you need to do selfie verification before you can withdraw.
And the hacker couldn't steal my money from all other crypto sites that I use because they use whitelist addresses to withdraw and 2FA.
I still can't fathom how it's 2026 and Polymarket still doesn't have the basic security features to protect your money.
when i used to be poor af, i used to think money is gonna fix all my problems
whenever anyone said money can’t fix their problems, i used to get the ick. i used to joke around that they just didn’t have enough money
now, i have some money and yet all my problems still remain. all of them
so no, money can’t fix your problems. i soo wish things were that easy
14
26
1,524


























