@AlterEgo_eth Interesting thread! Did you find any github bots with solid latency optimization? The strategy is irrelevant for me, I am just interested to see how they optimized the latency factors, especially for python
@devjoshstevens Every time your devs screw up another update, many users lose money. I saw one user who lost 30k today because during the Clob restart the heartbeat was not working and didn’t cancel his orders. This why users are leaving and volume is dropping because we just cannot rely on you
The other thing is that you guys are still not being honest / transparent with your users. Clob v2 was marketed as a whole fix to the ghost fill, latency and other issues. After launch it was said that ghost fills take time to fully eliminate (understandable), and now we get to know that latency is worse by design and will be fixed after weeks (probably months). Why didn’t you say from the beginning that it was a process which will weeks to months to fully fix these issues?
@devjoshstevens@kurushdubash The thing is that we heard this “things will get better” so many times already, but they don’t. One exploit gets fixed, now a few new ones pop up immediately + the latency is worse than ever. Your devs promise do to better, but still test their vibe scripts live in production.
@HiveLiveHQ Why call out the “vibe coded bots” falling for it when this issue is only possible because Poly devs are still vibe coding most of their work?
They should be the ones learning their lessons that Claude is not the solution to fix their bugs.
Fair point, but I think it is because PM crypto markets have been basically untradable for weeks because of the previous high amount of ghost fills and other issues and bugs. So imo the users moved not because of the TWAP but because they had no choice if they want to continue trading crypto prediction markets. I’m not a fan of Kalshi at all but at least their infra works and is stable, which cannot be said for PM.