秋田预测市场 · Discord 审计

Alex参与话题 0消息总数 10

该用户的聊天记录定位。

Reset

聊天记录

共 10 条,显示第 1-10 条
Alex 2026-06-23 23:08:12 Polymarket

No update on the LP reward of 20th though

No update on the LP reward of 20th though

Alex 2026-06-23 13:09:47 Polymarket

The RSS or API of this page doesnt work. also no notice for today.

The RSS or API of this page doesnt work. also no notice for today.

Alex 2026-06-23 11:29:38 Polymarket

ah yes

ah yes

Alex 2026-06-23 11:29:14 Polymarket

guys maker rebates are missing today?

guys maker rebates are missing today?

Alex 2026-06-21 23:08:22 Polymarket

What a nice tool

What a nice tool

Alex 2026-06-21 23:07:46 Polymarket

vs the maker rebate

vs the maker rebate

Alex 2026-06-21 23:07:36 Polymarket

https://polymarket.com/rewards These ones. That when you put limit orders around the midpoint you get some liquidity provider reward

https://polymarket.com/rewards These ones. That when you put limit orders around the midpoint you get some liquidity provider reward

Alex 2026-06-21 23:00:06 Polymarket

How can we distinguish maker rebates from the quote rewards?

How can we distinguish maker rebates from the quote rewards?

Alex 2026-06-14 21:43:26 Polymarket

guys is there going to be a Dec market for https://polymarket.com/event/what-price-will-wti-hit-in-june-2026 or they are decommissioning it?

guys is there going to be a Dec market for https://polymarket.com/event/what-price-will-wti-hit-in-june-2026 or they are decommissioning it?

Alex 2026-06-10 11:25:27 Polymarket

Guy is `GET /data/orders` known to serve stale snapshots? On June 9 (UTC) we repeatedly saw it lag the matching engine by 1–4 minutes: newly placed orders (WS-acked `LIVE`) missing from responses for up to ~115 s, cancelled orders still listed `LIVE` for up to ~270 s after the WS `CANCELED`, and at 16:11:45 UTC a response that contained 107 already-cancelled orders while missing ~140 live ones — i.e., a snapshot from ~90 s in the past

Guy is `GET /data/orders` known to serve stale snapshots? On June 9 (UTC) we repeatedly saw it lag the matching engine by 1–4 minutes: newly placed orders (WS-acked `LIVE`) missing from responses for up to ~115 s, cancelled orders still listed `LIVE` for up to ~270 s after the WS `CANCELED`, and at 16:11:45 UTC a response that contained 107 already-cancelled orders while missing ~140 live ones — i.e., a snapshot from ~90 s in the past