秋田预测市场 · Discord 审计

Ric参与话题 1消息总数 3

该用户的聊天记录定位。

Reset

聊天记录

共 3 条,显示第 1-3 条
Ric 2026-07-02 15:18:05 Polymarket API tick size和limit参数错误导致下单失败

https://polymarket.com/api/chainlink-candles?symbol=SOL&interval=5m&limit=15&endTime=1782975899999 shows ```{"error":"limit must be 30"}``` https://polymarket.com/api/chainlink-candles?symbol=SOL&interval=5m&limit=30&endTime=1782975899999 it works when I change it to 30, but if I remove limit I get the same error: https://polymarket.com/api/chainlink-candles?symbol=SOL&interval=5m&endTime=1782975899999 what's the point? if limit must always be 30 then why even include it as a parameter? Why not just remove it altogether?

https://polymarket.com/api/chainlink-candles?symbol=SOL&interval=5m&limit=15&endTime=1782975899999 shows ```{"error":"limit must be 30"}``` https://polymarket.com/api/chainlink-candles?symbol=SOL&interval=5m&limit=30&endTime=1782975899999 it works when I change it to 30, but if I remove limit I get the same error: https://polymarket.com/api/chainlink-candles?symbol=SOL&interval=5m&endTime=1782975899999 what's the point? if limit must always be 30 then why even include it as a parameter? Why not just remove it altogether?

Ric 2026-06-15 16:39:56 Polymarket

Please add optional start_time and end_time params to the api for /closed_positions, /positions and /trades because currently it returns ~5000 rows which is incomplete. Adding date filters would mean it can return the complete results and require fewer api calls

Please add optional start_time and end_time params to the api for /closed_positions, /positions and /trades because currently it returns ~5000 rows which is incomplete. Adding date filters would mean it can return the complete results and require fewer api calls

Ric 2026-06-09 00:51:32 Polymarket

wtf is this? Bitcoin Up or Down - June 7, 8:00PM-8:05PM ET. The websocket lagged by nearly 45 seconds! In this image the red line is the actual on-chain trade, the yellow line is the bitcoin price change - they both match. Green line is the ask and the dots are simulated orders along the Ask. For nearly a minute the websockets, both orderbook and trades lagged massively behind. It caught up after. How are we supposed to trade like this if the live price information is that stale???

wtf is this? Bitcoin Up or Down - June 7, 8:00PM-8:05PM ET. The websocket lagged by nearly 45 seconds! In this image the red line is the actual on-chain trade, the yellow line is the bitcoin price change - they both match. Green line is the ask and the dots are simulated orders along the Ask. For nearly a minute the websockets, both orderbook and trades lagged massively behind. It caught up after. How are we supposed to trade like this if the live price information is that stale???