Polymarketmerging yes and no shares of the same parlay is broken, pls fix
merging yes and no shares of the same parlay is broken, pls fix
martenJ参与话题 2消息总数 20
该用户的聊天记录定位。
聊天记录
共 20 条，显示第 1-20 条merging YES and NO shares of the same combo doesnt work
merging YES and NO shares of the same combo doesnt work
YES and NO shares of the combo cant be merged
YES and NO shares of the combo cant be merged
merging YES and NO shares of the same WC combo is broken
merging YES and NO shares of the same WC combo is broken
if i own YES and NO shares of the same parlay, how do I merge / redeem it? it used to work, something was changed, now it doesnt
if i own YES and NO shares of the same parlay, how do I merge / redeem it? it used to work, something was changed, now it doesnt
if i own YES and NO shares of the same combo, how do I redeem / merge it? It used to work, now it doesnt anymore
if i own YES and NO shares of the same combo, how do I redeem / merge it? It used to work, now it doesnt anymore
merging YES and NO shares of World Cup combos doesnt work anymore
merging YES and NO shares of World Cup combos doesnt work anymore
how do i merge YES and NO shares of the same combo bet? It used to work, something was changed, no I can't merge anymore
how do i merge YES and NO shares of the same combo bet? It used to work, something was changed, no I can't merge anymore
if i own YES and NO shares of the same World Cup combo, how do merge them exactly? it used to work, now it doesn't, something changed, claude cant help me
if i own YES and NO shares of the same World Cup combo, how do merge them exactly? it used to work, now it doesn't, something changed, claude cant help me
<@707597210845446214> getting this error when withdrawing, console has this error . claude tells me frontend "thinks" i have a deposit vault, but i have an old account with safe wallet. happy to share address in DM
<@707597210845446214> getting this error when withdrawing, console has this error . claude tells me frontend "thinks" i have a deposit vault, but i have an old account with safe wallet. happy to share address in DM
i have the same issue. i checked the console, claude is telling me frontend thinks i have a deposit vault, but its an old account with safe wallet . fix plz
i have the same issue. i checked the console, claude is telling me frontend thinks i have a deposit vault, but its an old account with safe wallet . fix plz
did that, same error
did that, same error
yes
yes
cant withdraw, tried different amounts, different networks, different addresses, always same "something went wrong error". yes there are more than enough funds in the acc edit: removed screenshot for privacy reason
cant withdraw, tried different amounts, different networks, different addresses, always same "something went wrong error". yes there are more than enough funds in the acc edit: removed screenshot for privacy reason
are world cup RFQs down?
are world cup RFQs down?
Gasless relayer 500 on combo merge_positions (mints on same relayer are fine) Since 2026-06-23 ~19:25 UTC, every gasless combo merge returns HTTP 500 internal server error at POST /submit. The relayer is otherwise healthy — the same wallet + same relayer key submits mint/split txns continuously with a normal success rate. Nothing changed on our side, and it hits 100% of merge attempts including newly-created combos, so it's not position-specific. We already ruled out the client: diffed the latest SDK (polymarket-client 0.1.0b9) vs ours (0.1.0b7) — the combo merge path is identical (same router/module addresses, same selectors, same prepare_condition + merge bundle). Same request 500s regardless of SDK version → server-side. SDK: polymarket-client 0.1.0b7 (also repro'd as identical in 0.1.0b9) Relayer: https://relayer-v2.polymarket.com → POST /submit Chain: Polygon (137), deposit/proxy wallet (gasless) WORKS: mint/split via POST /submit — hundreds/hr, 0 errors FAILS: merge_positions(legs=..., amount="max") → 500 "internal server error", every attempt, every ~20 min since 19:25Z 06-23 Failing bundle: 1) combinatorial_prepare_condition → 0x30000034706c7d8e12009dab006be20000c031a8 2) merge (router merge selector) → 0x12121212006e4CD160D18e3f00711DA5c3372600 SDK reads on-chain balances first; amount resolves > 0 (both legs held on-chain, NOT a "no balance" case). Response body is literally "internal server error" — no request id / detail. Q: Known relayer-side regression on the combinatorial-merge path? ETA or workaround? Low urgency on our end (collateral self-recovers at resolution), but complete-set merges are fully blocked meanwhile. Can share a specific failing condition_id in DM to trace.
Gasless relayer 500 on combo merge_positions (mints on same relayer are fine) Since 2026-06-23 ~19:25 UTC, every gasless combo merge returns HTTP 500 internal server error at POST /submit. The relayer is otherwise healthy — the same wallet + same relayer key submits mint/split txns continuously with a normal success rate. Nothing changed on our side, and it hits 100% of merge attempts including newly-created combos, so it's not position-specific. We already ruled out the client: diffed the latest SDK (polymarket-client 0.1.0b9) vs ours (0.1.0b7) — the combo merge path is identical (same router/module addresses, same selectors, same prepare_condition + merge bundle). Same request 500s regardless of SDK version → server-side. SDK: polymarket-client 0.1.0b7 (also repro'd as identical in 0.1.0b9) Relayer: https://relayer-v2.polymarket.com → POST /submit Chain: Polygon (137), deposit/proxy wallet (gasless) WORKS: mint/split via POST /submit — hundreds/hr, 0 errors FAILS: merge_positions(legs=..., amount="max") → 500 "internal server error", every attempt, every ~20 min since 19:25Z 06-23 Failing bundle: 1) combinatorial_prepare_condition → 0x30000034706c7d8e12009dab006be20000c031a8 2) merge (router merge selector) → 0x12121212006e4CD160D18e3f00711DA5c3372600 SDK reads on-chain balances first; amount resolves > 0 (both legs held on-chain, NOT a "no balance" case). Response body is literally "internal server error" — no request id / detail. Q: Known relayer-side regression on the combinatorial-merge path? ETA or workaround? Low urgency on our end (collateral self-recovers at resolution), but complete-set merges are fully blocked meanwhile. Can share a specific failing condition_id in DM to trace.
sick combo ser, dont spend it all at once
sick combo ser, dont spend it all at once
anyways will change to AWS eu-west-1 i
anyways will change to AWS eu-west-1 i
claude is telling there is
claude is telling there is
my PM bot on a hetzner server in Helsinki is getting geoblocked, do I need to get a new server in a new location?
my PM bot on a hetzner server in Helsinki is getting geoblocked, do I need to get a new server in a new location?