Wikedtik参与话题 0消息总数 2

Wikedtik 2026-07-06 06:31:57 ↗ Polymarket

No problem. Just stop snooping into my "encrypted" messages now please <@1100435718737772574> <:Bidensmile:1040247925420339251>

No problem. Just stop snooping into my "encrypted" messages now please <@1100435718737772574> <:Bidensmile:1040247925420339251>

Wikedtik 2026-07-05 15:39:53 ↗ Polymarket

The top-level 'to' for 'type: "WALLET"' is the polygon mainnet deposit wallet factory: `0x00000000000Fb5C9ADea0298D729A0CB3823Cc07' For a wallet batch, actual contract call goes in 'depositWalletParams.calls[].target'.. not top-level 'to'. If you’re already sending that exact factory & still get 'invalid 'to' field', I don’t think the fix is a different address. I’d check the final serialized JSON body right before POST, make sure you’re not using an old SAFE/PROXY payload shape, && make sure relayer key address matches 'from' if using personal 'RELAYER_API_KEY'. Also update to latest deposit wallet client path, there was a recent UUPS/beacon derivation issue.

The top-level 'to' for 'type: "WALLET"' is the polygon mainnet deposit wallet factory: `0x00000000000Fb5C9ADea0298D729A0CB3823Cc07' For a wallet batch, actual contract call goes in 'depositWalletParams.calls[].target'.. not top-level 'to'. If you’re already sending that exact factory & still get 'invalid 'to' field', I don’t think the fix is a different address. I’d check the final serialized JSON body right before POST, make sure you’re not using an old SAFE/PROXY payload shape, && make sure relayer key address matches 'from' if using personal 'RELAYER_API_KEY'. Also update to latest deposit wallet client path, there was a recent UUPS/beacon derivation issue.