Ismo Invest参与话题 0消息总数 2

Ismo Invest 2026-07-06 07:51:20 ↗ Polymarket

<@624575779023355904> Coud you kindly address this?

<@624575779023355904> Coud you kindly address this?

Ismo Invest 2026-07-03 18:43:29 ↗ Polymarket

Hey everyone 👋 Hoping someone on the team can help me out, I'm building a trading bot and I'm trying to nail down a few details about how trade events behave that I couldn't fully pin down from the docs. This is more of an follow-up on trade event / matching-engine semantics (ref: Benayun's 5/2/26 "Settlement tx hash mismatch on MATCHED FOK order" thread in #polybuilder https://discord.com/channels/710897173927297116/1413855130360484003/1500200097798160497) A few things still aren't clear from the docs — hoping the team can confirm: (a) Top-level price on a multi-level sweep: when a taker order crosses several resting levels, is the top-level price field the volume-weighted average across all maker_orders, the first (best) level, or the marginal (last) level? And is top-level size always the taker's total matched quantity across all levels? (b) bucket_index contract: when a trade is split into multiple objects (Snowman noted this happens "only if they would require too much gas"), do the per-bucket sizes always sum to the taker total, and is there exactly one MINED/settlement per bucket? What precisely does bucket_index index? (c) Hash stability & trade id (the Benayun follow-up): does transaction_hash change if a settlement tx is replaced/resubmitted (gas repricing / nonce bump / RETRYING)? And is the trade id guaranteed static across all lifecycle emissions (MATCHED → MINED → CONFIRMED)? We dedup on transaction_hash, so this matters a lot. (d) User-channel delivery guarantees: are user-channel trade events best-effort (missable across a reconnect, with GET /trades as canonical recovery), or guaranteed delivery? Are stages strictly ordered (never CONFIRMED without a prior MINED)? Thanks!

Hey everyone 👋 Hoping someone on the team can help me out, I'm building a trading bot and I'm trying to nail down a few details about how trade events behave that I couldn't fully pin down from the docs. This is more of an follow-up on trade event / matching-engine semantics (ref: Benayun's 5/2/26 "Settlement tx hash mismatch on MATCHED FOK order" thread in #polybuilder https://discord.com/channels/710897173927297116/1413855130360484003/1500200097798160497) A few things still aren't clear from the docs — hoping the team can confirm: (a) Top-level price on a multi-level sweep: when a taker order crosses several resting levels, is the top-level price field the volume-weighted average across all maker_orders, the first (best) level, or the marginal (last) level? And is top-level size always the taker's total matched quantity across all levels? (b) bucket_index contract: when a trade is split into multiple objects (Snowman noted this happens "only if they would require too much gas"), do the per-bucket sizes always sum to the taker total, and is there exactly one MINED/settlement per bucket? What precisely does bucket_index index? (c) Hash stability & trade id (the Benayun follow-up): does transaction_hash change if a settlement tx is replaced/resubmitted (gas repricing / nonce bump / RETRYING)? And is the trade id guaranteed static across all lifecycle emissions (MATCHED → MINED → CONFIRMED)? We dedup on transaction_hash, so this matters a lot. (d) User-channel delivery guarantees: are user-channel trade events best-effort (missable across a reconnect, with GET /trades as canonical recovery), or guaranteed delivery? Are stages strictly ordered (never CONFIRMED without a prior MINED)? Thanks!