秋田预测市场 · Discord 审计

py-clob-client v2升级后订单签名错误

2026-06-21 · Polymarket · 14 条相关讨论

idk 2026-06-20 20:10:22

does this stuff work? https://www.pmxt.dev/docs/api-reference/fetch-order-book#historical-crypto-5m-events I can't find any event

does this stuff work? https://www.pmxt.dev/docs/api-reference/fetch-order-book#historical-crypto-5m-events I can't find any event

CryptoScam 2026-06-20 21:26:46

of Polymarket that does not have any proper docs to use the API and of this standalone fix that simply does not work

of Polymarket that does not have any proper docs to use the API and of this standalone fix that simply does not work

blunkoed 2026-06-20 21:29:11

wdym they don't have api doc

wdym they don't have api doc

CryptoScam 2026-06-20 21:33:06

docs are dogshit, they don't even explain you how to authenticate

docs are dogshit, they don't even explain you how to authenticate

CryptoScam 2026-06-20 22:04:27

I have 3 accounts, 2 legacy safe and 1 with new deposit method. The 2 legacy are working perfectly well, the 1 with new deposit method, I can't get to trade with it

I have 3 accounts, 2 legacy safe and 1 with new deposit method. The 2 legacy are working perfectly well, the 1 with new deposit method, I can't get to trade with it

CryptoScam 2026-06-20 22:34:11

Even ChatGPT premium can't get it to work

Even ChatGPT premium can't get it to work

CryptoScam 2026-06-20 22:42:04

I give up, it's broken

I give up, it's broken

shenlol 2026-06-20 23:01:26

CLOB V2: how do I place API orders from a deposit wallet (POLY_1271 / sig type 3)? My pUSD sits in a deposit wallet (standard website signup), but the SDKs bind the API key to my EOA while the order signer is the deposit wallet, so every order is rejected with the order signer address has to be the address of the API KEY (and create_api_key → 400). Checked py-clob-client-v2 1.0.1 and polymarket_client_sdk_v2 0.6.0-canary.1 — neither threads funder/signature_type into L1 auth (matches issues #53/#70/#75/#77). Is there any working way to trade from a deposit wallet via API today (which SDK/version + flow), or is a fix still pending?

CLOB V2: how do I place API orders from a deposit wallet (POLY_1271 / sig type 3)? My pUSD sits in a deposit wallet (standard website signup), but the SDKs bind the API key to my EOA while the order signer is the deposit wallet, so every order is rejected with the order signer address has to be the address of the API KEY (and create_api_key → 400). Checked py-clob-client-v2 1.0.1 and polymarket_client_sdk_v2 0.6.0-canary.1 — neither threads funder/signature_type into L1 auth (matches issues #53/#70/#75/#77). Is there any working way to trade from a deposit wallet via API today (which SDK/version + flow), or is a fix still pending?

CryptoScam 2026-06-20 23:16:57

For new deposit, sig 0/1/2 -> PolyApiException: PolyApiException[status_code=400, error_message={'error': 'maker address not allowed, please use the deposit wallet flow'}] sig 3 -> PolyApiException: PolyApiException[status_code=400, error_message={'error': 'the order signer address has to be the address of the API KEY'}]

For new deposit, sig 0/1/2 -> PolyApiException: PolyApiException[status_code=400, error_message={'error': 'maker address not allowed, please use the deposit wallet flow'}] sig 3 -> PolyApiException: PolyApiException[status_code=400, error_message={'error': 'the order signer address has to be the address of the API KEY'}]

1nevitably 2026-06-21 01:08:57

I have an account created via email/Magic Link(signed up June 2026 I can authenticate with the CLOB API and see my balance, but every order placement returns: PolyApiException status_code=400 'the order signer address has to be the address of the API KEY'. private key and funder address are both exported directly from Polymarket's reveal.magic.link This appears to be the same issue as py_clob_client_v2 GitHub issue #75 (deposit wallet POLY_1271 accounts incompatible with Python SDK) Is there a workaround or timeline for a fix? <:pepecry:1480174599093096560>

I have an account created via email/Magic Link(signed up June 2026 I can authenticate with the CLOB API and see my balance, but every order placement returns: PolyApiException status_code=400 'the order signer address has to be the address of the API KEY'. private key and funder address are both exported directly from Polymarket's reveal.magic.link This appears to be the same issue as py_clob_client_v2 GitHub issue #75 (deposit wallet POLY_1271 accounts incompatible with Python SDK) Is there a workaround or timeline for a fix? <:pepecry:1480174599093096560>

1nevitably 2026-06-21 01:35:16

I have an account created via email/Magic Link(signed up June 2026 I can authenticate with the CLOB API and see my balance, but every order placement returns: PolyApiException status_code=400 'the order signer address has to be the address of the API KEY'. private key and funder address are both exported directly from Polymarket's reveal.magic.link <:pepecry:1480174599093096560>

I have an account created via email/Magic Link(signed up June 2026 I can authenticate with the CLOB API and see my balance, but every order placement returns: PolyApiException status_code=400 'the order signer address has to be the address of the API KEY'. private key and funder address are both exported directly from Polymarket's reveal.magic.link <:pepecry:1480174599093096560>

Naru 2026-06-21 04:19:41

My bot was working on py-clob-client v1 ~6 weeks ago. After migrating to py-clob-client-v2 I get maker address not allowed, please use the deposit wallet flow on every order. Wallet is a Google login proxy wallet. How do I complete the deposit wallet flow programmatically for v2? The update_balance_allowance() call returns empty. Any docs on the v1→v2 migration for proxy wallets?

My bot was working on py-clob-client v1 ~6 weeks ago. After migrating to py-clob-client-v2 I get maker address not allowed, please use the deposit wallet flow on every order. Wallet is a Google login proxy wallet. How do I complete the deposit wallet flow programmatically for v2? The update_balance_allowance() call returns empty. Any docs on the v1→v2 migration for proxy wallets?

Naru 2026-06-21 04:19:52

My bot was working on py-clob-client v1 ~6 weeks ago. After migrating to py-clob-client-v2 I get maker address not allowed, please use the deposit wallet flow on every order. Wallet is a Google login proxy wallet. How do I complete the deposit wallet flow programmatically for v2? The update_balance_allowance() call returns empty. Any docs on the v1→v2 migration for proxy wallets?

My bot was working on py-clob-client v1 ~6 weeks ago. After migrating to py-clob-client-v2 I get maker address not allowed, please use the deposit wallet flow on every order. Wallet is a Google login proxy wallet. How do I complete the deposit wallet flow programmatically for v2? The update_balance_allowance() call returns empty. Any docs on the v1→v2 migration for proxy wallets?

Gabriel 2026-06-21 09:52:12

Hi guys, I've been experiencing this error when trying to post orders via CLOB SDK even when using POLY_1271 + auth with funder ```Order failed: the order signer address has to be the address of the API KEY``` This is a new wallet created to trade programatically onto Polymarket, I signed all setup needed txs, I made a trade from UI just to check if trading works from it, tried creating a relayer api key, deposited funds from signer wallet but could not figure it out, does anyone have an idea of how to fix this or what could be the problem?

Hi guys, I've been experiencing this error when trying to post orders via CLOB SDK even when using POLY_1271 + auth with funder ```Order failed: the order signer address has to be the address of the API KEY``` This is a new wallet created to trade programatically onto Polymarket, I signed all setup needed txs, I made a trade from UI just to check if trading works from it, tried creating a relayer api key, deposited funds from signer wallet but could not figure it out, does anyone have an idea of how to fix this or what could be the problem?