Rez

@Tudmotu Right, because it's impossible to do anything meaningful onchain without using 16.78M gas in one tx. Not sure you serious. Also, contract deployment can even exceed the tx gas limit with glamsterdam.

x.com/i/article/2051…

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.

Privacy isn't a feature you bolt on, it's an architectural property that only works when the underlying chain infrastructure is built for it. @tempo Zones is exactly the kind of primitive enterprises have been waiting for, and we're excited to be building alongside the team.