Hi, I'm blocked from API trading due to a known issue with POLY_1271 deposit wallets. The problem: The CLOB requires order.signer = deposit wallet for signatureType 3, but also requires the order signer to match the API key address. API keys can only be derived from an EOA (since /auth/api-key doesn't support ERC-1271). So there's no way to get an API key that matches the deposit wallet address. My setup: EOA: 0x1f89FE1099E70cFeC149e1E668E9b388941Dc211 Deposit wallet (deployed): 0x85c09ee56f43a2f6f5706adb4bbc946bf4a0fbcd SDK: <@1507887323474432153>/clob-client-v2 v1.0.8 Error: "the order signer address has to be the address of the API KEY" This is the same issue as GitHub #70, #71, #76 on py-clob-client-v2. Multiple users are blocked. Has anyone from engineering confirmed whether POLY_1271 API trading actually works today, or is it still being implemented on the server side?
Hi, I'm blocked from API trading due to a known issue with POLY_1271 deposit wallets. The problem: The CLOB requires order.signer = deposit wallet for signatureType 3, but also requires the order signer to match the API key address. API keys can only be derived from an EOA (since /auth/api-key doesn't support ERC-1271). So there's no way to get an API key that matches the deposit wallet address. My setup: EOA: 0x1f89FE1099E70cFeC149e1E668E9b388941Dc211 Deposit wallet (deployed): 0x85c09ee56f43a2f6f5706adb4bbc946bf4a0fbcd SDK: <@1507887323474432153>/clob-client-v2 v1.0.8 Error: "the order signer address has to be the address of the API KEY" This is the same issue as GitHub #70, #71, #76 on py-clob-client-v2. Multiple users are blocked. Has anyone from engineering confirmed whether POLY_1271 API trading actually works today, or is it still being implemented on the server side?