We know the website has been getting slow - as market creation exploded, the UI was flooding Gamma with API calls (it had no market paging 🤯). We've shipped a new internal gateway API built in Rust and rebuilt the pages from scratch on top of it, now serving combos (8x faster) and sports (4x faster). Next up, we're working on the event, esports, categories, and home pages to make them load instantly, too. The website will keep getting faster every week. You all deserve a website that feels instant. Left is before (no cache), and right is after (now live)

One of our complaints from traders: the UI optimised orders for speed, not correctness. Some flows updated positions before the exchange responded, then corrected them later if the order was partially filled or failed, but this caused late updates, incorrect states, and failed sells. Now that our indexing and data API is much more performant, we changed this so that market buys and sells wait for the trade response; fills, partial fills, rejections and errors show immediately. This also improves correctness and sell success rate, making it safer and better to trade.

We have built our Polymarket indexing systems in-house, powered by rindexer in Rust. We now see onchain data events up to 14 blocks (28 seconds) faster, and we index within 0-10ms of block broadcasting, making it nearly instant. This means trades, positions, and balances will update much faster. We will use Goldsky as a data backup, but we now primarily run on our own indexing infrastructure.

We just shipped a major rewrite of our developer docs. Clearer integration guides, unified SDK documentation, practical API examples, and a much better path from first request to production. We would love to hear what you think. docs.polymarket.com

No polymarket or UMA contracts have been exploited. All user funds are safe, and using Polymarket.com is safe, so business as usual. We had a 6-year-old private key that was compromised. This was in the internal top-up config, which is why funds were being sent to it. We have rotated this key, revoked all prod permissions and are moving all PKs to KMS keys from now on.

What a day, but on a more positive note, we did a release this morning, and the latency on the CLOB is now 500% better. You should see a huge difference. Thanks for waiting for the fix. It was a hard one because it was at the lowest level of the services. We have many other fixes coming in the next weeks to take this down even further.

Introducing the unified TypeScript and Python SDKs, now in beta. One consistent surface for Polymarket discovery, market data, trading, account data, and realtime streams. Python ships with both async and sync clients, so you can choose the model that fits your app. Docs: docs.polymarket.com/dev-tool… Coming soon: unified API, Rust SDK, and React SDK. Our goal is to build the best developer tooling for Polymarket integrations. Feedback welcome: drop it in the discord dev channel, reply here, or DM me.

Much of Polymarket's core trading infrastructure was built years ago and is now being rearchitected to handle today's scale. ClobV2 with deposit wallet was the top non-negotiable priority because it's what prevents ghost fills the added latency you've seen since v2 mostly comes from new order and wallet validation infrastructure. With that protection in place, reducing latency to the fastest we ever had it is now our single biggest focus. Over the next two weeks we have a series of releases dedicated to bringing latency down. Broadly, they target: - Rewriting one of the slowest internal steps in the order flow. - Smarter handling of activity bursts, aiming at reducing backed-up queues. - Reworking the order book and its data flow. The single biggest latency reduction in the plan. The first release in this series went live today. Expect the next latency releases toward the end of this week and next week.