maker address not allowed with signature_type=2 (GNOSIS_SAFE) on create_and_post_order

[pablojuve27t1]

SDK: py-clob-client-v2 v1.0.1rc1
Wallet: Existing Gnosis Safe proxy (MetaMask login)
EOA: 0xd35b6D...be99b
Funder: 0x93d06c...FcDc (shown in polymarket.com/settings)
get_open_orders() → works ✅
create_and_post_order() → {"error": "maker address not allowed, please use the deposit wallet flow"}
Initialization: signature_type=2, funder=proxy_address, creds derived with same params
All on-chain allowances set (USDC, CTF Exchange, NegRisk Exchange)

[nxdht]

me too

[devin202506]

me too

[GaratSahil]

me too

[Hansoey]

Same bug here, can confirm reproduction. SDK v1.0.1rc1, MetaMask Safe (signature_type=2).
Adding one extra data point: orders on non-neg-risk markets work fine with the same client (verified by placing $1 test order on a regular binary market). Only neg-risk markets fail with invalid signature. Suggests the bug is in the EIP-712 domain construction for the neg-risk verifyingContract path.

[mnyshenko]

+++

[mlewandowskim]

https://docs.polymarket.com/trading/deposit-wallet-migration

[GaratSahil]

Update: tested both v1.0.0 and v1.0.1rc1 — both fail with the same
"order signer address has to be the address of the API KEY" error.

In v1.0.0, the order has signer = EOA (matches the address that L1
auth signed with → should match api_key.bound_address). Still rejected.

In v1.0.1rc1, the order has signer = deposit_wallet (matches POLY_1271
spec). Also rejected.

So neither what the SDK calls "correct" nor "buggy" is what Polymarket's
server actually accepts. Suggests the api_key created with
funder=deposit_wallet, sig_type=3 parameters isn't being bound to
ANY valid address server-side.

Polymarket support (Polybot via email) confirmed today that L2 API
keys cannot bind to deposit wallets — described as a "structural
limitation."

Without server-side EIP-1271 L1 auth or a deposit-wallet-specific
api_key endpoint, retail users with deposit wallets can't place orders
via SDK.