
polynode
491 posts

polynode
@joinPolynode
https://t.co/C9ayz8M0OU | fastest data streams and most robust API on @polymarket







ANNOUNCING: PREDICTION MARKETS ON ARKHAM





Exchange upgrades go live on April 28 at 11am UTC. ~1 hour of downtime. The v1 orderbook gets cleared and all open limit orders are cancelled. Funds and positions are safe. Trading via API? Update to the latest SDK before then. V1 clients stop working after cutover. Dev migration guide: poly.market/dznOlVu Users guide: poly.market/DaxnRAA








Polymarket's V2 exchange upgrades go live April 22nd. The upgraded exchange is now open to all for testing. 🚨 If you use our API or clients, there's migration work to do before then: → Upgrade your SDK/ API integration → New exchange contract addresses & order struct → Collateral moves to pUSD (wrap USDC.e via the Collateral Onramp) We expect ~1 hour of downtime on April 22nd at ~11am UTC. Open limit orders will be cancelled during the switch. Funds and positions are safe. Please note that the V1 exchange will stop working after the migration. Migration guide: docs.polymarket.com/v2-migration Security: Our CTFv2 contracts are open sourced & audited by Cantina + Quantstamp. $5 million bug bounty program is live on Cantina: cantina.xyz/bounties/ff945… Changelog: docs.polymarket.com/changelog








opened a PR: github.com/fulldecent/pol… your stream was subscribed to `trades`, which is our post-confirmation firehose. the pre-confirmation channel is `settlements`. that's the one that fires the second we decode from the mempool. the 650ms you measured is actually a pretty clean tell that you were reading our confirmed trade events, not the mempool ones. swap the subscription and the lead shows up. ran your unchanged v2 with the fix: n=7464, median 3353ms, zero missed txs across every block.


