This is due to a bad state not staying in sync with the chain all the time, causing a trade not to be taken down when it would revert. The percentage of affected trades is small, but it's more prominent in markets with lower liquidity, like weather. We are working on a fix for this now. This fix will also fix the reward issue, as it’s related to it.

If you want to build perps for both retail and pro users, we’re hiring experienced perps backend engineers at Polymarket. If you’re interested, DM me what you worked on before. Rust experience ideal.

False. We are launching a new beta product and allowing a select group of users to try it out, with KYC required only during this beta period. No KYC is being added to any part of existing with this launch. Once this product is out of beta no KYC will be required to use it.

No polymarket or UMA contracts have been exploited. All user funds are safe, and using 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.

Looking for the best design engineers in the world to work on Polymarket. is your canvas and your job is making it 1% better every day. Full creative control, own every pixel. DM me your GitHub/portfolio and show me why you're the best in the world.

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.

If ghostfill issues drove you away from Polymarket, whether up/down markets or any markets I completely understand. But please give it another shot. It’s now working better than ever, and if there’s anything in the UI that could make your experience even better, we want to hear it. We’re building the best defi prediction product user-first, one improvement at a time.

The release everyone was waiting for is now live. Ghost fills dropped from a peak of 30% to 0.17% with the rollout, and will continue trending toward 0% throughout the day. We know this issue was hurting everyone's experience and we're truly sorry for that but it should now be night and day. This was a significant core protocol change and we're incredibly proud of the whole team for executing it. We'll keep improving our systems, step by step, until we're the best exchange in the world.

This is my 3rd week as VP of Engineering DeFi at @Polymarket , and I'm going to be straight: the traction @Polymarket has seen has massively outpaced our infrastructure, and we haven't done nearly enough to scale to keep up. I hear you, and fixing this is our entire focus. We're a major company now, and we need to engineer like one. Here's exactly what we're doing: - Onchain data latency. We're working on making this near-instant so the experience is incredible. - Chain migration. We need more block space, cheaper gas and much smaller block times so settlement is instant. - Transactions are getting cancelled. We understand this is one of the most frustrating issues right now, and we have a complete fix coming very soon. - Massive focus on the website to make it faster, more responsive, and with better UX. - We added observability everywhere. Proper alerting so we catch issues ourselves, market makers should not be the ones telling us something is down. That's been unacceptable, and we know it. - E2e tests throughout, starting with the CLOB, so issues get caught in CI before anything ships. - CLOBv2 is not a rewrite. It won't improve performance or stability on its own; it's an upgrade that unlocks us to move fast right after. We'll do better with communication next time. - We are rebuilding the CLOB from the ground up. Most important thing we're doing. Without it, we can't be the best DeFi exchange in the world. We know it, we're on it, it's mission critical. - Unified TypeScript SDK for all APIs, which is shipping soon. - Unified API. One WS connection for everything, with a schema that's actually readable. - New Polymarket contract in the works that unlocks things that are simply impossible on the current protocol. - New hires: Head of QA Automation, Head of Dev Tooling, Head of Internal Tooling, Head of Data Engineering. - Smaller, dedicated teams. Fewer focus points per person, clearer ownership. People do what they're good at and are accountable for it. - Working closely with customer support to give them real debugging tools so any user issue gets properly diagnosed, not lost. - Proper communication with marketing and market makers so everyone knows what's coming and when, and MM can submit feature requests with a clear path to get them into engineering and shipped. - Working with 4 security teams daily to ensure we're super secure and that funds are always safe. - Perps incoming. Brand new contracts and a backend built from scratch in Rust. We're proud of this one. - A lot of other fixes are running in parallel right now. Starting next Friday, I will be posting weekly engineering updates. I joined because I genuinely believe in what @Polymarket is trying to do. @shayne_coplan built this so the world has somewhere to go to find out what's actually going to happen, not what the media thinks, not what a pundit says, but what thousands of people are willing to put money on. But right now, our engineering isn't living up to that. We've let people down, and I'm not going to dress that up. I came here to fix it, and that's exactly what we're going to do. The next few months are going to speak for themselves. Stay with us.

Excited to join @Polymarket as VP of Engineering. I haven’t seen a hungrier team in my career, the talent density here is insane. We’re building the future of how people understand the world. What should we build next? What’s broken? What’s missing? Drop it below. P.s we are hiring world class people in NYC DMs open