秋田预测市场 · Discord 审计

0xDonny参与话题 1消息总数 2

该用户的聊天记录定位。

Reset

聊天记录

共 2 条,显示第 1-2 条
0xDonny 2026-06-15 17:10:07 Polymarket

Hey folks, anyone's bot keep a local cache of the orderbook for a token/tokens? If so, any tips on how to properly detect staleness in this book? This should be possible with the hashes that get sent around, but the hashes require 'Last Trade Price", which isn't always included definitively in all WS messages, e.g. the price change event. There is a 'last trade price' event, but it's not nearly as frequent as the price change events, so you deal with lag if you just grab it then. You can 'kind of' derive it, but it's not always clear what metric PM is using in the hash depending on the change- cancellations, fills, etc. the complement token trading. Would love if someone has authoritatively solved this problem to chat about it some.

Hey folks, anyone's bot keep a local cache of the orderbook for a token/tokens? If so, any tips on how to properly detect staleness in this book? This should be possible with the hashes that get sent around, but the hashes require 'Last Trade Price", which isn't always included definitively in all WS messages, e.g. the price change event. There is a 'last trade price' event, but it's not nearly as frequent as the price change events, so you deal with lag if you just grab it then. You can 'kind of' derive it, but it's not always clear what metric PM is using in the hash depending on the change- cancellations, fills, etc. the complement token trading. Would love if someone has authoritatively solved this problem to chat about it some.

0xDonny 2026-06-14 15:56:02 Polymarket WebSocket数据流重复及API签名错误影响开发者

Can anyone share the formula for the `hash` field in CLOB market-channel `price_change` / `book` events — exact field list (including last trade price source), JSON key order, and hash algorithm? Reverse-engineering it for local-book verification but our recompute diverges.

Can anyone share the formula for the `hash` field in CLOB market-channel `price_change` / `book` events — exact field list (including last trade price source), JSON key order, and hash algorithm? Reverse-engineering it for local-book verification but our recompute diverges.