Native USDC sent to proxy EOA address not recognized as CLOB balance

[Antoniaiaiaiaia]

Issue

When following the proxy wallet flow, I transferred native USDC directly to the proxy EOA address on Polygon, but the CLOB balance remains $0.00 and orders fail with not enough balance / allowance.

Details

• Main wallet: 0x20aD5B77A64855325Cb42D23f4f52EC418d11436
• Proxy wallet: 0xE4F6a03ad7012e901F206ce09513f387B16aFC30
• Amount stuck: 61.12 USDC (native, Polygon — 0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359)
• TX hash: 0x3e3a7f826d3de3b82ae0c175f7923301fe265a3b5e2914e216aa47a891e19b09
• Chain: Polygon (chainId 137)

What happened

1. polymarket clob balance --asset-type collateral returned $0.00
2. polymarket wallet show displayed the proxy address
3. I assumed transferring USDC to the proxy address would fund the account
4. Transferred native USDC directly to the proxy EOA on-chain
5. CLOB balance still shows $0.00 after update-balance
6. Running polymarket approve set succeeds but on-chain allowances remain 0
7. Order placement fails: not enough balance / allowance

Additionally, the proxy address has 0 bytes of code (not yet deployed as a contract), so the USDC is currently inaccessible.

Questions

1. What is the correct way to fund a proxy wallet account for CLOB trading?
2. Is the proxy address a counterfactual contract? If so, how is it deployed?
3. Is there a recovery path for USDC sent directly to an undeployed proxy address?

Suggestion

The CLI documentation and wallet show output should clearly warn users not to send funds directly to the proxy address, and instead direct them to use the official deposit flow via the Polymarket web interface or bridge.

[arielmiki]

i'm on the same boat here, i transfer 100 USDC directly to proxy address and cannot recover it

[rafael81]

Me too

[David200308]

Me too