秋田预测市场 · Discord 审计

jof974参与话题 0消息总数 1

该用户的聊天记录定位。

Reset

聊天记录

共 1 条,显示第 1-1 条
jof974 2026-06-14 19:40:49 Polymarket

Hi ! +1 - same issue, still blocked as of today (June 13). Two independent accounts (Magic Link + MetaMask), both post-2026-04-28, signatureType=3, funder=deposit wallet, EOA≠funder: • Manual UI trading: works • createOrDeriveApiKey(): binds key to EOA • POST order: 400 "the order signer address has to be the address of the API KEY" • L1 with POLY_ADDRESS=funder + ERC-7739 wrap: 401 Invalid L1 Request headers Also completed full UI onboarding + manual order on MetaMask account — balance updated ($50→$45) but API still fails identically. Tested: clob-client-v2 1.0.6, rs-clob-client-v2 0.6.0-canary.1 — same result. Polymarket AI bot support confirmed: no officially supported way to bind L2 creds to deposit wallet when EOA≠funder. No ETA, can't escalate via chat. Question for the group: has ANYONE actually gotten API orders working on a type-3 deposit wallet account created after April 28? If yes, what was the exact fix? If no, we're all waiting on a server-side L1 fix. GitHub: #64 #65 #70 #56 (all open)

Hi ! +1 - same issue, still blocked as of today (June 13). Two independent accounts (Magic Link + MetaMask), both post-2026-04-28, signatureType=3, funder=deposit wallet, EOA≠funder: • Manual UI trading: works • createOrDeriveApiKey(): binds key to EOA • POST order: 400 "the order signer address has to be the address of the API KEY" • L1 with POLY_ADDRESS=funder + ERC-7739 wrap: 401 Invalid L1 Request headers Also completed full UI onboarding + manual order on MetaMask account — balance updated ($50→$45) but API still fails identically. Tested: clob-client-v2 1.0.6, rs-clob-client-v2 0.6.0-canary.1 — same result. Polymarket AI bot support confirmed: no officially supported way to bind L2 creds to deposit wallet when EOA≠funder. No ETA, can't escalate via chat. Question for the group: has ANYONE actually gotten API orders working on a type-3 deposit wallet account created after April 28? If yes, what was the exact fix? If no, we're all waiting on a server-side L1 fix. GitHub: #64 #65 #70 #56 (all open)