Bug: signer field set to EOA address instead of deposit wallet when using signature_type=3 (POLY_1271)

[yokithaiii]

When using py-clob-client-v2 v1.0.0 with a deposit wallet (signature_type=3 / POLY_1271), the signer field in the order payload is populated with the EOA address (derived from the private key) instead of the deposit wallet address passed as funder.

According to Polymarket documentation, for POLY_1271 orders both maker and signer must equal the deposit wallet address. As a result, every order placement fails with:

the order signer address has to be the address of the API KEY

Steps to reproduce

from py_clob_client_v2 import ClobClient, OrderArgs, OrderType, PartialCreateOrderOptions, Side

client = ClobClient(
    host="https://clob-v2.polymarket.com",
    chain_id=137,
    key=EOA_PRIVATE_KEY,
    creds=creds,
    funder=DEPOSIT_WALLET_ADDRESS,  # deposit wallet
    signature_type=3,               # POLY_1271
)

order = client.create_order(
    order_args=OrderArgs(token_id="...", price=0.4, side=Side.BUY, size=100),
    options=PartialCreateOrderOptions(tick_size="0.01"),
)

print(order["maker"])   # DEPOSIT_WALLET_ADDRESS  ✅
print(order["signer"])  # EOA_ADDRESS             ❌ — should also be DEPOSIT_WALLET_ADDRESS

Expected behavior

When signature_type=3 and funder is provided, the signer field in the built order should be set to funder (deposit wallet address), not to the EOA address derived from the private key.

Actual behavior

order["signer"] is set to the EOA address. The API rejects the order.

Root cause (suspected)

In OrderBuilder, the signer field of the order struct is populated from self.signer.address (the EOA). For signature_type=3, it should instead use self.funder when a funder address is provided.

Workaround

Manually overwrite the field after building the order:

order["signer"] = DEPOSIT_WALLET_ADDRESS
order["maker"] = DEPOSIT_WALLET_ADDRESS

Environment

• py-clob-client-v2 version: 1.0.0
• Python: 3.x
• Chain: Polygon (137)
• signature_type: 3 (POLY_1271)

[GaratSahil]

Confirming the bug exists in v1.0.0 — but flagging that the fix in
PR #39 (shipped as v1.0.1rc1) doesn't actually solve the trading
problem.

Tested both versions today with sig_type=3 + funder=deposit_wallet:

v1.0.0:
Order built: signer = EOA, maker = deposit_wallet
POST /order → 400 "the order signer address has to be the address of the API KEY"

v1.0.1rc1 (with PR #39 fix):
Order built: signer = deposit_wallet, maker = deposit_wallet
POST /order → 400 "the order signer address has to be the address of the API KEY"

Neither config works. The SDK fix is correct per spec, but Polymarket's
server rejects both EOA and deposit_wallet as the order.signer.

Same root cause as #43, #46, #48 — Polymarket support confirmed via
email today this is a structural limitation in how api_keys bind to
deposit wallets.

[favianyip]

Confirming this also blocks me. V2 SDK 1.0.1rc1, deposit wallet deployed, sig_type=3, getting the order signer address has to be the address of the API KEY. Funds
▎ stranded in deposit wallet. Any ETA on a fix or a way to manually rebind the api_key?