The Polymarket team has absolutely no experience with CLOB (Content on Transaction Allocation), and their technical skills are at least at the level of a third-rate exchange, or even lower. For those using the API, here are some current warnings to avoid pitfalls and losses: The PM team has not yet responded to our situation, support tickets are being ignored, and they are operating in a completely passive, irresponsible manner. See the previous post for details. Seeking redress is extremely difficult; prioritize risk management. 1. WebStorm (WS) data latency is common. Whether using WS or the API, proper timestamp verification and order book cross-validation are fundamental. It is now recommended to add an additional liquidity check; a sudden and significant drop in liquidity is a red flag. 2. If you are looking for the lowest possible latency, hosting your server in Europe is the fastest option. A ping time of under 3ms and an API request response time of under 100ms are considered normal. 3. Cross-validation is necessary, but currently unlikely on polymarkets because their matching events are sometimes delayed by several hours before being pushed to the blockchain, and their orderbook interface returns erroneous data (unverifiable). Furthermore, regardless of whether you perform timestamp verification or not, neither API data nor on-chain events can be trusted. It's not that the data is outdated, not that it's downtime, not that it's an error; the returned data is simply fake. For example, if a market price is 0.8, it might experience a server glitch and restart, giving you a quote of 0.6. Then you trigger a stop-loss and the system actually matches you at the 0.6 price and liquidity, only for the original 0.6-0.8 orders to reappear a few minutes later. How do you know if the price at that time was due to a server glitch, a genuine order cancellation by the counterparty, or a price drop? Unfortunately, there's no way to know. 4. Based on this situation, any program handling large transactions needs to be extremely cautious, especially avoiding stop-loss logic. We have already removed the stop-loss logic from all strategies and made other adjustments.