poi

355 posts

poi

poi

@poip2i

Katılım Ağustos 2023
76 Takip Edilen161 Takipçiler
Insider Paper
Insider Paper@TheInsiderPaper·
BREAKING: Shots fired in Times Square - reports
English
127
375
1.9K
314.6K
poi
poi@poip2i·
fucking hell claude has become dogshit.
English
1
0
7
637
Variance Lover
Variance Lover@variance_lover·
Open letter to @Polymarket and especially @shayne_coplan: I've been trading on Polymarket for a long time. I am one of the biggest traders on the entire platform and I interact with it on a daily basis. And at this point I'm seriously questioning whether the team has simply given up. I'm not even trying to be dramatic. Wtf is actually going on? Has everyone made enough money that nobody cares anymore? Is the team completely overwhelmed? Are priorities completely broken? Is there no leadership? Is it incompetence? Because the current state of the platform is honestly embarrassing. Every maintenance seems to follow the exact same script: announce 10 minutes of downtime start 20 minutes late stay down for an hour deploy changes that break multiple existing systems leave the bugs in production for weeks And somehow nobody seems concerned. Example: ~1.5 weeks ago an update broke tick sizes. The matching engine started rejecting orders that matched the correct tick size after a tick size change was published. This was immediately visible after deployment. It's still broken. Nobody seems to care. Then for the last two days Polymarket's own RTDS feed, the feed used for all crypto markets, has been broken. The issue was marked "resolved" 10 hours ago. It still isn't resolved! Did anyone spend literally 5 seconds checking whether data was actually being published before closing the incident? Because it sure doesn't feel like it. Communication is somehow even worse than the bugs. Half the changes never get announced. The other half are hidden in random Discord side conversations. Major trading-impacting changes get silently rolled out with zero documentation. You ask support. They say they'll ask the team. Then you never hear back. Or you get the same canned response you've already received three times. The team keeps saying communication will improve. It never does. Then there's the rebate and fee situation. Taker tiers were supposed to launch on May 28. A week later they still weren't live. Nobody acknowledged the delay. The docs still said May 28. To this day there still hasn't been a single taker rebate payment. And the official position is apparently that missed rebates won't be back-paid. How is that acceptable? How are traders supposed to adjust strategies, thresholds, and risk when nobody knows what fees they are actually paying, what rebates they are actually earning, or how much of the promised rewards the platform simply decides not to distribute? That isn't transparency and it is clearly destroying trust. The craziest part is that every update creates fresh opportunities for exploiters. Just in the last couple weeks we've had: queue position jump exploits taker delay bypass exploits ghost fill exploits various matching and infrastructure bugs order spam exploits Millions of dollars have been extracted from legitimate users through platform failures. The response? Increase rate limits. Seriously. A huge amount of latency issues today are caused by order spam that is directly incentivized by broken infrastructure and exploitable mechanics. Fixing the root causes would help. Instead we get band-aids. Which raises another question: Does Polymarket have a testing environment? Does it have staging? Can updates be rolled back? Because from the outside it honestly looks like production is the testing environment. Every maintenance introduces new failures. Every maintenance gets partially reverted. Every maintenance creates more issues than it solves. This shouldn't be happening at a company valued in the billions. Meanwhile manipulation that has been repeatedly reported for months continues largely unchecked while manipulators keep extracting money from normal users. And surprise: Volume is declining. Prediction markets as a whole are growing. Yet Polymarket just posted its second consecutive month of declining volume. Meanwhile Kalshi has become the clear market leader in many categories and is now outperforming Polymarket by large multiples in areas where Polymarket used to dominate. Honestly? It's not hard to see why. Every serious trader I've spoken to says the same thing: Kalshi feels stable. Polymarket feels like you're one deployment away from disaster. I know multiple people who would happily trade Polymarket full-time if they trusted the platform. They don't. Not because of competition. Because they don't trust Polymarket itself. My trust in this platform is at an all-time low. And I genuinely don't understand what is happening internally. Maybe the response will be that the team is busy with the World Cup or other initiatives. Fine. Then stop shipping half-finished features. Stop deploying untested fixes. Stop breaking live trading. Slow down. Focus on fewer things. Do them properly. The most concerning part is that so many decisions feel like they were made by people with no actual trading experience. The product decisions show it. The infrastructure decisions show it. The market structure decisions show it. Building the future of prediction markets requires understanding how markets actually function. Right now it often feels like nobody is steering the ship. I want Polymarket to succeed. But from the perspective of someone who uses the platform every day, this is bordering on unusable. @Polymarket @shayne_coplan What is going on?
English
110
55
715
71K
Josh
Josh@devjoshstevens·
Hey, thanks for writing this out. You do have some valid points on everything you said. I have touched on some of these points before in tweets, but I joined a few months ago as VP of Engineering, DeFi, to set standards for how we build at Polymarket. We, as a team, have hired many new senior people over the last few months, and we feel the difference internally and how we are starting to work together. The CLOB was built over 4 years ago and has inherited technical debt due to wrong core low-level decisions; fixing these core parts isn't easy when you have so many parts to consider and continue to serve a huge amount of traffic. Note that the success of Polymarket would not have been possible without the speed of development, so no blame on these systems at all; it happens. We now have a dedicated trading team working solely on the CLOB, fixing and rebuilding those core components from the ground up. Every issue you raised was an issue before and has been fixed / is known and being fixed. A few things which have been improved over the last 2 months: 1. Full observability into the systems with traces and alerts 2. Eliminated ghost fills for takers that were causing a high failure rate for trades. 3. We improved the core matching engine latency via faster summary generations by 41.2% 4. Introduced a new validation layer that helps us keep the core engine healthy; with this one, the p90 improved by 32% during highly volatile periods. Also, we currently support 50% more user requests on the engine. Here are the things coming in the next weeks and months: 1. Feature flags in the clob to allow us to turn on and off features when doing critical deployments, eliminating unnecessary downtime for users while still allowing the team to safely ship 2. Revamped rate limit system that is maker-focused, improving latencies for both takers and makers. As we improve latency on the core engine, we're seeing more requests, which is causing degradation, so revamping the rate limits is key. 3. We are moving to an async flow on our current engine to support higher throughput. 4. Introduce new order types that allow makers to preserve their queue positions. 5. Decreasing the startup time so deployments can be easily put out and reverted if needed quickly 6. Way more improvements to the internal systems but can't list them all Taker delay bypass exploits - This was implemented incorrectly initially, allowing cancellations for already delayed orders. We prevent this by preventing these cancellations and properly reserving the capital for all taker-delayed orders. Ghost fill exploits - The clob is synced with the user's deposit wallet state, so whenever the user wants to perform a clob action, it is informed in advance, helping it consolidate the state. There is still a small amount of ghost fills (0.001%), as we still support the old wallet types and have edge case race conditions, but this will be fully eliminated once all users are on the deposit wallets and with the new async architecture. Order spam exploits - Atm, we keep an open rate limit model; this means that users get the same limit across markets. We want to introduce a token-based system to make it harder for bad actors to exceed current limits. RTDS: We missed observability on this, and that's on us. We fixed it, and now we have proper alerts. Sorry about that. Stability is something we are actively solving; as said, it's our core focus with the trading team. We're growing the team by 2x and bringing in very senior ex-exchange engineers to rethink and rebuild a bunch of things. Our plan is to be the best exchange in the world, and we have a long way to go, but we will get there with the core improvements we are making highlighted above. Most of our trading changes at the moment are fixes, and we alert Discord because it's our main place people trade alongside some signals; most don't require documentation, mainly because there are no breaking changes and it's a fix to address tech debt. We do need to work on communication; we're trying to improve this with Friday updates and improvements to our core documentation and Discord/Signal channels. We are also working on better communication overall, with restarts and downtimes being announced in advance. Also, we have a direct line to you on Signal; we should chat more there. The team is always on call to help with any issues you face. Taker tiers was something we slipped on, and we should have done better with the communication around when it is coming. We have started splitting certain tasks like this into smaller pods, with ownership and accountability for each. A lot has got better internally, but there is loads of room to improve, and this is a good example of how core communication could have fixed this; sorry about that. We, of course, have staging, but most, if not all, of our issues only occur under production load. We just finished a full, dedicated environment powered by a Tenderly VNET, allowing us to run proper load tests and simulate production load before we put stuff out. We have hired a head of QA who is also working on proper e2e automated tests on the CLOB to catch these issues in CI before they go out. Moral of the story: we really do care about building the best systems in the world. Polymarket moves very fast, and it wouldn't be here today without it, but we know that improving core stability is key to us thriving, and we're working on that right now, step by step. You are a smart person; you know that fixing these foundations cannot happen overnight, but we are on it and hear you.
English
12
7
112
6.4K
xxd
xxd@Xxd58213555Xxd·
@AndrssTerranova @Pirat_Nation 你对社会主义有什么误解,社会主义体制下 不可能给员工分红,连涨工资都是奢望,社会主义国家没有工会,那只是摆设,员工罢工属于是违法,中国人在国外参与罢工,回到中国会被关进监狱,这就叫社会主义,你敢想象吗?正是因为资本主义,工人才有罢工的权利,才能得到应得的报酬
中文
2
0
10
849
Pirat_Nation 🔴
Pirat_Nation 🔴@Pirat_Nation·
Samsung has reached a deal to pay up to $26.6 billion (40 trillion won) in bonuses to its semiconductor employees after last-minute union negotiations averted a strike. Under the new 10-year profit-sharing program, average payouts are estimated at $340,000 to $400,000 per worker. The bonuses come from strong demand for AI memory chips, and Samsung now expects its 2026 profits to grow almost seven times higher to around $218 billion. This deal is like the one at SK Hynix
Pirat_Nation 🔴 tweet mediaPirat_Nation 🔴 tweet media
English
144
309
4.3K
432.7K
poi
poi@poip2i·
Ig if massie actually won, everyone would have been okay and moved on with it but now they atleast have to face the fact that money holds more power than actual votes for politicians.
English
0
0
0
41
Ingrid Caroline
Ingrid Caroline@mungkinpentingg·
I can literally hear my stomach reacting
English
942
2.9K
18K
3.7M