I might be the only person in the world that likes looking at Rust code. I think it's super pretty.

We are public with Polymarket perps, but we haven't really been pushing its growth yet. Before that, we want our system to be prepared for any level of growth - in October, we will have our v2 engine live for perps, which will make it one of the fastest perps exchanges in crypto. 🦀

Introducing Polymarket Data, a public source for U.S. & International exchange data. Polymarket U.S. hit 1b+ total volume (contracts) for the weekend, consecutive daily ATHs: - Saturday: 510m+ - Sunday: 525m+ We're just getting started.

volume, open interest & all trades are available through our API, and all of it is backed from Onchain auditable data - docs.polymarket.com/api-refe… - docs.polymarket.com/api-refe… - docs.polymarket.com/api-refe…

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)

We rewrote our data API in Rust 🦀, yielding 50% faster p50s and 90% faster p99s. It uses our in-house indexing tables - Polymarket UI now uses them throughout, which means trades, positions, and balances will load much faster. The API is open for anyone to consume on the /v2 route. Docs: docs.polymarket.com/api-refe…

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.

some users were affected during last week’s CLOB downtime we want to make this right, and goodwill credits are going out today around 3,000 wallets got goodwill credits automatically. if you think you were affected and did not receive a payment, reach out to me at suhail@polymarket.com with your details by friday september 18 and we will personally review more details: poly.market/clob-outage-deta…

Polymarket Perps is live. Up to 20x leverage on crypto, stocks, commodities, & more. Deepest liquidity, lowest fees. Long BTC, predict the Fed, short the S&P reaction — only on Polymarket⁠.com 👉 polymarket.com/perps

Honest post: the Polymarket DeFi CLOB is full of tech debt. It grew fast, got hacked together, and most of the team inherited it that way. Since joining and building out the team, we have scaled it 10x and made it 3x faster, but it’s not enough; the core foundations of how it’s been built are wrong in almost every way. You try to fix one thing, and another thing goes wrong; the conclusion now is that the codebase can’t be saved long-term. The exchange is the heart of Polymarket; everything runs through it. If we want to be the best exchange in the world, it must be fast, stable, and scalable. We can’t keep patching the old one, where these core foundations are generally missing throughout, so we’re rewriting it from scratch in Rust. Early numbers: 10-20x faster on p99 than today, 200,000 orders per second (15x what we have now, with room to reach 400,000+), and stability under load. This will put us faster than most exchanges, including CEXs. Building it in Rust gives us memory safety with no garbage collector. No GC means no random pauses and no random latency spikes; the tail latency in the benchmarks is the tail latency you get in production, alongside a strict compiler that enforces correctness up front. Data races and memory corruption (the bugs that take exchanges down) can’t exist in the first place. Polymarket has to take it seriously that we are an exchange; this is people’s money, not a joke. To succeed, we have to fix this; otherwise, we will fail. It’s as simple as that. I joined to build the best software in the world, not to maintain some of the worst, and I will do everything I can to make Polymarket a serious exchange. We are aiming to have the exchange ready sometime in Q4 (mid to end). I'll communicate progress as we go so you all know the status. Breaking changes will be minimal for all integrators and will be communicated in advance. We will maintain the existing CLOB and keep trying to improve it as we build this side by side. We can’t wait to throw away the existing CLOB; we dislike it as much as you all do. Make Polymarket fast, finally.

Session keys are now in beta on the trading APIs. A session key can trade on your deposit wallet behalf but can never withdraw - making third-party integrations dramatically better, and unlocking ability to build features that weren’t possible before. A few builders are testing it now. Opening to every builder soon, with session key support coming to the Polymarket UI later. Want early access for your users? DM me. docs.polymarket.com/trading/…

Polymarket presents the first-ever Niu Lai watch party in Niu York 🗽 📅 Thursday, Aug 20 · 8PM 📍 Location TBD 👉Pull up: luma.com/7hivcavz #牛来 #NiuLai

Crypto vendors hide fees in creative ways. Let's break down how these flows actually work. First, to be clear, Polymarket has: 1. The lowest fees. 2. The fastest settlement. 3. The highest limits. Here's how. First, how do most crypto orchestrators work today? A user attempts a trade. The orchestrator scans the market for the "best rate," picks a route on the user's behalf, and executes. Sounds great. So what's the problem? Issue 1) Markets are dynamic, and pricing can be poor If you rely on orchestration alone, you will give users bad pricing at some point - markets aren't always efficient. USDT to USDC trades at a floating market price, not a fixed one. As of writing, depositing USDT on Hyperliquid carries an 8.7bp markup & Relay costs 15.5bp. The same transaction on Polymarket costs 5.5bp. The bigger the transaction, the worse pricing gets. A $10M USDT deposit through an orchestrator means brutal slippage, slow settlement, or no quote at all - funds stuck. And it is worst exactly when it matters most. Markets dislocate hardest during high volatility, so users get their worst pricing during a big airdrop, election, IPO, or sports game. To give users a good experience, someone has to eat the cost when markets aren't efficient. Apps will say "we have zero fees" - but when markets dislocate, retail gets their face ripped off. Btw – it is not possible to offer 1:1 USDT to USDC for deposits & withdrawals in any size without be arbitraged. Issue 2) Most bridges can't guarantee SLAs Say a user is depositing $10M into Polymarket. Try any leading router rn and you'll struggle to find a quote for a $10M USDT transaction. Should those transactions just get stuck? What happens during the Super Bowl, when everyone bridges at once? We've seen liquidity on major bridges drop below $50k. Should users just not be able to deposit? What happens when rebalancing goes down on a major chain? It happened to BNB recently - funds couldn't get off the chain. Should every BNB user eat 1h+ delays? Every cross-application bridge (i.e., ALL bridges today) is exposed to these failures. To give users a good experience, you need an app-specific bridge with real capital behind it - in Polymarket's case, >$10M dedicated to instant transactions for its users alone. Apps will say "we can bridge from any chain" - then fall over when markets dislocate. How does Fun + Polymarket solve this? Fun + Polymarket routing combines three capabilities: 1. An OTC desk. 2. A world-class aggregator. 3. An app-specific bridge. The result: 1. Best pricing from Relay, Across, LayerZero, CCTP, and others - at all times. Thanks to our relationships with Polymarket, Aave, Lighter & others Fun is one of the largest transaction originators in crypto. This size enables highly preferential pricing. 2. Fun steps in and takes the loss if routers can't deliver SLA-level pricing. 3. Fun holds $10M to fill the transaction if routers can't deliver the size. This thread doesn't even mentioned the other infra to make crypto tx's great: transaction retries, gas retries, slippage monitoring, broad token & chain support, fast pickup times, RPC fallbacks, streaming fallbacks, and more. @Polymarket and @Fun have iterated on this tech for two years. I'm proud of the work, and grateful for the partners we've built alongside. I admire what the Kalshi team has built - this isn't a hit piece, and John is well-intentioned. But it is simply inaccurate to imply Polymarket has inferior crypto rails. Polymarket supports larger orders, faster, with tighter settlement and greater uptime than any other crypto platform today.