秋田预测市场 · Discord 审计

reverend_renegade参与话题 1消息总数 6

该用户的聊天记录定位。

Reset

聊天记录

共 6 条,显示第 1-6 条
reverend_renegade 2026-07-10 21:11:35 Kalshi 用户询问API是否存在自成交预防机制

does the exchange have built in wash trading prevention for those who are market making and taking? I want to avoid latency for when taker liquidity shows up while i have maker orders open, cancelling my makers to consume the taker liquidity which would likely be gone by then.

does the exchange have built in wash trading prevention for those who are market making and taking? I want to avoid latency for when taker liquidity shows up while i have maker orders open, cancelling my makers to consume the taker liquidity which would likely be gone by then.

reverend_renegade 2026-06-12 21:16:21 Kalshi

Following the June 11th maintenance announcement that all HYPE market settlements would transition from U_HYPEUSD_RTI to HYPEUSD_RTI, we're seeing an inconsistency in the market metadata returned by the API. 15-minute markets (consistent with announcement): GET /trade-api/v2/markets/KXHYPE15M-26JUN121300-00 rules_primary references HYPEUSDRTI (new index) Hourly range markets created before the switch (inconsistent): GET /trade-api/v2/markets?event_ticker=KXHYPE-26JUN1217 rules_primary on all markets still references UHYPEUSDRTI (old index) Hourly range markets created after the switch (consistent): GET /trade-api/v2/markets?event_ticker=KXHYPE-26JUN1210 rules_primary references HYPEUSD_RTI (new index) It appears that markets created before the 5:00 AM ET switch retained the old index name in their rules_primary text, while markets created after reflect the new index. Will the 5 PM range event (KXHYPE-26JUN1217) settle using HYPEUSD_RTI (as stated in the announcement) or U_HYPEUSD_RTI (as stated in the market's own rules_primary)? Is rules_primary a reliable indicator of which index is used for settlement, or is the announcement the source of truth?

Following the June 11th maintenance announcement that all HYPE market settlements would transition from U_HYPEUSD_RTI to HYPEUSD_RTI, we're seeing an inconsistency in the market metadata returned by the API. 15-minute markets (consistent with announcement): GET /trade-api/v2/markets/KXHYPE15M-26JUN121300-00 rules_primary references HYPEUSDRTI (new index) Hourly range markets created before the switch (inconsistent): GET /trade-api/v2/markets?event_ticker=KXHYPE-26JUN1217 rules_primary on all markets still references UHYPEUSDRTI (old index) Hourly range markets created after the switch (consistent): GET /trade-api/v2/markets?event_ticker=KXHYPE-26JUN1210 rules_primary references HYPEUSD_RTI (new index) It appears that markets created before the 5:00 AM ET switch retained the old index name in their rules_primary text, while markets created after reflect the new index. Will the 5 PM range event (KXHYPE-26JUN1217) settle using HYPEUSD_RTI (as stated in the announcement) or U_HYPEUSD_RTI (as stated in the market's own rules_primary)? Is rules_primary a reliable indicator of which index is used for settlement, or is the announcement the source of truth?

reverend_renegade 2026-06-05 04:57:02 Kalshi

<@709913035766235146> anything for the deadliest pistoleer since wild bill

<@709913035766235146> anything for the deadliest pistoleer since wild bill

reverend_renegade 2026-06-04 20:25:58 Kalshi

<@709913035766235146> https://docs.kalshi.com/llms.txt point your llm to this url rather than manually going through the api documents or relying upon training data

<@709913035766235146> https://docs.kalshi.com/llms.txt point your llm to this url rather than manually going through the api documents or relying upon training data

reverend_renegade 2026-06-04 04:28:10 Kalshi

you guys ever plan on doing <15m cryptocurrency markets such as 10m, 5m or 1m using the same ma for the last 60s?

you guys ever plan on doing <15m cryptocurrency markets such as 10m, 5m or 1m using the same ma for the last 60s?