DepositWallet initialization bug - Unable to generate API credentials + withdraw impossible

[mnogoreche-sys]

Deposit succeeded.

Balance: 106.57 pUSD

Symptoms:

• Unable to generate API credentials
• Trading cannot be enabled
• Withdraw fails
• Base signs EIP712 successfully
• No tx hash is created
• No gas spent
• UI returns "Something went wrong"

Wallet:

0x5D106C255ce4Ffc6d0366FDb0F3eB24F70372884

Looks like DepositWallet backend initialization failed.

[osr21]

Likely root cause: API key bound to EOA, not deposit wallet

The symptoms you describe — EIP-712 signs correctly, no on-chain transaction, "Something went wrong" — are the same pattern as **#64** and the related cluster (#65, #73, #75).

### What's happening

`createApiKey()` internally calls `createL1Headers(this.signer)`, which signs the key-creation request with your **EOA** (the Base wallet you connected). The CLOB registers the API key against that EOA address.

When your account was onboarded after the V2 cutover, Polymarket automatically created a **deposit wallet** (a Safe proxy controlled by the relayer). All trading — including API key creation — must be authorised relative to that deposit wallet, not the bare EOA.

Result: the API key is created but bound to the wrong address, so every subsequent trading action (including the "enable trading" step in the UI) is rejected server-side, leaving you in the locked state you see.

### Quickest check

```ts
import { ClobClientV2 } from "@polymarket/clob-client-v2";

const client = new ClobClientV2({ host: "https://clob.polymarket.com", chainId: 137, signer });

// This should return the deposit wallet address — NOT your EOA
const depositWalletAddr = await client.getDepositWalletAddress();
console.log("Deposit wallet:", depositWalletAddr);

// If this matches your EOA, the client hasn't resolved the deposit wallet yet
// — that's the initialization failure
```

### Fix

Migrate to **`@polymarket/client@0.4.0`** (the `ts-sdk` monorepo package), which resolved this in the `createApiKey`/`deriveApiKey` flow by signing the key-creation message with the deposit wallet's EIP-1271 method rather than the raw EOA. The `clob-client-v2` package predates this fix.

If you need to stay on `clob-client-v2`, see the workaround in #64 — you can manually pass `funderAddress` equal to the deposit wallet address to force the correct binding.

Also see: #64, #75 (TypeScript), #87 (Python equivalent).