秋田预测市场 · Discord 审计

存款钱包API签名类型3报错maker address not allowed

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

alzxul 2026-06-02 20:59:29

If you're a moron like me make sure you actually use your deposit wallet address... turns out I was using the wrong address 💀 I used `derive_uups_deposit_wallet_address` from `py-sdk` to work it out in the end

If you're a moron like me make sure you actually use your deposit wallet address... turns out I was using the wrong address 💀 I used `derive_uups_deposit_wallet_address` from `py-sdk` to work it out in the end

climbtheladder 2026-06-02 21:08:53

Has anyone got this whole deposit wallet thing to work with magic-owned wallets. What is the workflow there?

Has anyone got this whole deposit wallet thing to work with magic-owned wallets. What is the workflow there?

Anon 2026-06-02 22:12:06

I'm a developer trying to use the Python CLOB API with a deposit wallet account (signature_type=3). I'm getting 'the order signer address has to be the address of the API KEY' on every order. This matches GitHub issues #64, #70, #71 on py-clob-client-v2. Is there a working workaround or timeline for a fix?

I'm a developer trying to use the Python CLOB API with a deposit wallet account (signature_type=3). I'm getting 'the order signer address has to be the address of the API KEY' on every order. This matches GitHub issues #64, #70, #71 on py-clob-client-v2. Is there a working workaround or timeline for a fix?

Anon 2026-06-02 22:16:59

I'm a developer trying to use the Python CLOB API with a deposit wallet account (signature_type=3). I'm getting 'the order signer address has to be the address of the API KEY' on every order. This matches GitHub issues #64, #70, #71 on py-clob-client-v2. Is there a working workaround or timeline for a fix?

I'm a developer trying to use the Python CLOB API with a deposit wallet account (signature_type=3). I'm getting 'the order signer address has to be the address of the API KEY' on every order. This matches GitHub issues #64, #70, #71 on py-clob-client-v2. Is there a working workaround or timeline for a fix?

Aemond Targaryen 2026-06-02 23:23:55

# (Type 3) Fixing `Order signer address` / `Maker address not allowed` 🍆 `signature_type=3` + `funder` is not sufficient: the server requires `order.signer` (your deposit wallet) to equal the address your CLOB key resolves to. The derived key only resolves to the deposit wallet when the wallet is deployed and your signing EOA is its registered signer. ## What you need - **Funder address**: Profile page (left of the pencil) - **Private key**L: Settings -> Account -> Export PK - **Relayer API key**: Settings -> Relayer API keys -> Create new - **Singer address**: Settings -> Relayer API keys -> Signer address - **At least two brain cells and one minute to read and understant** ## Rust ```rust let signer = LocalSigner::from_str(&private_key)? .with_chain_id(Some(137)); let funder: Address = deposit_wallet_address.parse()?; let clob = ClobClient::new("https://clob.polymarket.com", ClobConfig::default())? .authentication_builder(&signer) .funder(funder) .signature_type(SignatureType::Poly1271) .authenticate() .await?; ``` ## Python ```python from py_clob_client_v2 import ClobClient, OrderArgs, OrderType from py_clob_client_v2.constants import BUY client = ClobClient( host="https://clob.polymarket.com", key=PRIVATE_KEY, chain_id=137, signature_type=3, funder=DEPOSIT_WALLET_ADDRESS, ) creds = client.create_or_derive_api_creds() client.set_api_creds(creds) resp = client.create_and_post_order( OrderArgs(token_id=TOKEN_ID, price=0.40, size=5, side=BUY), order_type=OrderType.GTC, ) ```

# (Type 3) Fixing `Order signer address` / `Maker address not allowed` 🍆 `signature_type=3` + `funder` is not sufficient: the server requires `order.signer` (your deposit wallet) to equal the address your CLOB key resolves to. The derived key only resolves to the deposit wallet when the wallet is deployed and your signing EOA is its registered signer. ## What you need - **Funder address**: Profile page (left of the pencil) - **Private key**L: Settings -> Account -> Export PK - **Relayer API key**: Settings -> Relayer API keys -> Create new - **Singer address**: Settings -> Relayer API keys -> Signer address - **At least two brain cells and one minute to read and understant** ## Rust ```rust let signer = LocalSigner::from_str(&private_key)? .with_chain_id(Some(137)); let funder: Address = deposit_wallet_address.parse()?; let clob = ClobClient::new("https://clob.polymarket.com", ClobConfig::default())? .authentication_builder(&signer) .funder(funder) .signature_type(SignatureType::Poly1271) .authenticate() .await?; ``` ## Python ```python from py_clob_client_v2 import ClobClient, OrderArgs, OrderType from py_clob_client_v2.constants import BUY client = ClobClient( host="https://clob.polymarket.com", key=PRIVATE_KEY, chain_id=137, signature_type=3, funder=DEPOSIT_WALLET_ADDRESS, ) creds = client.create_or_derive_api_creds() client.set_api_creds(creds) resp = client.create_and_post_order( OrderArgs(token_id=TOKEN_ID, price=0.40, size=5, side=BUY), order_type=OrderType.GTC, ) ```

porto 2026-06-03 01:54:50

hi polymarket team, quick builder question. is there an approved path for depositwallet authorizesessionsigner using the official ts builder relayer client and sig type three? our owner signed wallet batch self calls authorizesessionsigner with a session signer and valid until, but the relayer rejects it with call blocked self call authorizesessionsigner not allowed. is this unavailable to builders, allowlist only, or is there another sdk or endpoint for one tap trading? thanks.

hi polymarket team, quick builder question. is there an approved path for depositwallet authorizesessionsigner using the official ts builder relayer client and sig type three? our owner signed wallet batch self calls authorizesessionsigner with a session signer and valid until, but the relayer rejects it with call blocked self call authorizesessionsigner not allowed. is this unavailable to builders, allowlist only, or is there another sdk or endpoint for one tap trading? thanks.

mau 2026-06-03 02:33:10

Hi, I'm building a bot to bet on Polymarket. It reads the markets and everything seems fine, but when I try to place trades, I always get the same error: it can't place bets on its own. I asked Claude and he said it's a problem with new accounts. Is this true, or how can I fix it?

Hi, I'm building a bot to bet on Polymarket. It reads the markets and everything seems fine, but when I try to place trades, I always get the same error: it can't place bets on its own. I asked Claude and he said it's a problem with new accounts. Is this true, or how can I fix it?

mau 2026-06-03 02:38:15

Platform: macOS, Python 3.11, py-clob-client-v2 1.0.x Wallet type: MetaMask (EOA) EOA address: 0x5295681E3f21f16e78007D3e0A8D1a2dDF05F0B2 Proxy/funder address: 0xa43F755A2bd67beec038CA897EeDA8A73511449E Error: status_code=400 'maker address not allowed, please use the deposit wallet flow' Tried all signature types (0, 1, 2, 3) with funder=proxy address. Also tried with TypeScript SDK (@polymarket/clob-client-v2) — same error. Account was created with Gmail/Magic on Polymarket.com. API credentials were extracted from localStorage poly_clob_api_key_map. The account has funds ($22.74) and trade history, but cannot place orders via API.

Platform: macOS, Python 3.11, py-clob-client-v2 1.0.x Wallet type: MetaMask (EOA) EOA address: 0x5295681E3f21f16e78007D3e0A8D1a2dDF05F0B2 Proxy/funder address: 0xa43F755A2bd67beec038CA897EeDA8A73511449E Error: status_code=400 'maker address not allowed, please use the deposit wallet flow' Tried all signature types (0, 1, 2, 3) with funder=proxy address. Also tried with TypeScript SDK (@polymarket/clob-client-v2) — same error. Account was created with Gmail/Magic on Polymarket.com. API credentials were extracted from localStorage poly_clob_api_key_map. The account has funds ($22.74) and trade history, but cannot place orders via API.

mau 2026-06-03 02:58:59

Hi, I'm trying to place orders via API with my deposit wallet but getting "maker address not allowed, please use the deposit wallet flow" My setup: - EOA/Signer: 0x2Ff679034651D97aE2F6B8b0166efF33904aCb7f (from Export PK) - Deposit wallet: 0xa43F755A2bd67beec038CA897EeDA8A73511449E (from profile page) - API key: associated with signer address (verified) - Using py-clob-client-v2 with signature_type=3, funder=deposit_wallet Error: "maker address not allowed, please use the deposit wallet flow" Also tried signature_type 0,1,2 — same error. Is the deposit wallet 0xa43F... fully deployed and initialized? How can I verify it's ready to trade via API?

Hi, I'm trying to place orders via API with my deposit wallet but getting "maker address not allowed, please use the deposit wallet flow" My setup: - EOA/Signer: 0x2Ff679034651D97aE2F6B8b0166efF33904aCb7f (from Export PK) - Deposit wallet: 0xa43F755A2bd67beec038CA897EeDA8A73511449E (from profile page) - API key: associated with signer address (verified) - Using py-clob-client-v2 with signature_type=3, funder=deposit_wallet Error: "maker address not allowed, please use the deposit wallet flow" Also tried signature_type 0,1,2 — same error. Is the deposit wallet 0xa43F... fully deployed and initialized? How can I verify it's ready to trade via API?

mau 2026-06-03 03:26:53

The issue: create_or_derive_api_key() returns the key for my EOA (0x2Ff679...) not for my deposit wallet (0xa43F...). With signature_type=3, the order signer = funder = 0xa43F... But the API key is associated with 0x2Ff679... Server error: "the order signer address has to be the address of the API KEY" create_api_key() returns: "Could not create api key" How do I create an API key that resolves to the deposit wallet 0xa43F... instead of the EOA 0x2Ff679...? Is there a relayer step needed first to deploy the wallet?

The issue: create_or_derive_api_key() returns the key for my EOA (0x2Ff679...) not for my deposit wallet (0xa43F...). With signature_type=3, the order signer = funder = 0xa43F... But the API key is associated with 0x2Ff679... Server error: "the order signer address has to be the address of the API KEY" create_api_key() returns: "Could not create api key" How do I create an API key that resolves to the deposit wallet 0xa43F... instead of the EOA 0x2Ff679...? Is there a relayer step needed first to deploy the wallet?

⚜Casanoovaa_⚜ 2026-06-03 04:54:24

Hello!! Im Using @polymarket/clob-client-v2 (5.8.1), proxy/Gnosis Safe wallet, signatureType=2, and Im getting this error: maker address not allowed, please use the deposit wallet flow. What is the correct configuration for accounts created via MetaMask wallet connect? My funder address is correctly set.

Hello!! Im Using @polymarket/clob-client-v2 (5.8.1), proxy/Gnosis Safe wallet, signatureType=2, and Im getting this error: maker address not allowed, please use the deposit wallet flow. What is the correct configuration for accounts created via MetaMask wallet connect? My funder address is correctly set.

mau 2026-06-03 05:28:37

Following your instructions exactly: - Private key from Settings → Export PK ✓ - Funder = profile page address = 0xa43F755A2bd67beec038CA897EeDA8A73511449E ✓ - Signer = 0x2Ff679034651D97aE2F6B8b0166efF33904aCb7f ✓ - Relayer API key created ✓ - getDeployed() returns true ✓ Running exact Python code from your guide: client = ClobClient(key=PRIVATE_KEY, chain_id=137, signature_type=3, funder=DEPOSIT_WALLET) creds = client.create_or_derive_api_key() # Returns "Could not create api key" from server # Falls back to old creds associated with 0x2Ff679... not 0xa43F... Then create_and_post_order() fails with: "the order signer address has to be the address of the API KEY" The server cannot create a new API key for the deposit wallet 0xa43F... Is there a manual step needed to associate the API key with the deposit wallet?

Following your instructions exactly: - Private key from Settings → Export PK ✓ - Funder = profile page address = 0xa43F755A2bd67beec038CA897EeDA8A73511449E ✓ - Signer = 0x2Ff679034651D97aE2F6B8b0166efF33904aCb7f ✓ - Relayer API key created ✓ - getDeployed() returns true ✓ Running exact Python code from your guide: client = ClobClient(key=PRIVATE_KEY, chain_id=137, signature_type=3, funder=DEPOSIT_WALLET) creds = client.create_or_derive_api_key() # Returns "Could not create api key" from server # Falls back to old creds associated with 0x2Ff679... not 0xa43F... Then create_and_post_order() fails with: "the order signer address has to be the address of the API KEY" The server cannot create a new API key for the deposit wallet 0xa43F... Is there a manual step needed to associate the API key with the deposit wallet?

mau 2026-06-03 06:58:52

Getting "the order signer address has to be the address of the API KEY" when placing orders with signature_type=3. Setup: - funder (deposit wallet): 0xa43F755A2bd67beec038CA897EeDA8A73511449E - signer (EOA): 0x2Ff679034651D97aE2F6B8b0166efF33904aCb7f - getDeployed() = true - Relayer API key created Problem: create_or_derive_api_key() returns "Could not create api key" from server, falls back to existing key which is associated with the EOA not the deposit wallet. How do I get/create an API key that resolves to the deposit wallet 0xa43F... instead of the EOA 0x2Ff679...?

Getting "the order signer address has to be the address of the API KEY" when placing orders with signature_type=3. Setup: - funder (deposit wallet): 0xa43F755A2bd67beec038CA897EeDA8A73511449E - signer (EOA): 0x2Ff679034651D97aE2F6B8b0166efF33904aCb7f - getDeployed() = true - Relayer API key created Problem: create_or_derive_api_key() returns "Could not create api key" from server, falls back to existing key which is associated with the EOA not the deposit wallet. How do I get/create an API key that resolves to the deposit wallet 0xa43F... instead of the EOA 0x2Ff679...?