jjwarr参与话题 0消息总数 2

jjwarr 2026-07-02 06:21:05 ↗ Polymarket

Hey all — hoping someone can help with a CTF approval issue on a post-April 28 Magic.link email account. I'm using signature type POLY_1271 (sig_type=3). BUY orders work fine and pass balance checks. SELL orders fail with "not enough balance → balance 0". I've called `setApprovalForAll` on the CTF ERC-1155 contract via the WALLET batch endpoint — the transaction mines successfully (nonce increments, STATE_MINED confirmed), but when I check `isApprovedForAll` on-chain, it returns False. The approval simply isn't landing. Same behaviour for `approve()` on the pUSD ERC-20 — mines fine but allowances remain 0 on-chain. Is there a specific way to set CTF ERC-1155 approvals from a deposit wallet on a post-April 28 account? Is the WALLET batch endpoint the correct mechanism, or is there a different call encoding / flow required for this account type? Any help appreciated!

Hey all — hoping someone can help with a CTF approval issue on a post-April 28 Magic.link email account. I'm using signature type POLY_1271 (sig_type=3). BUY orders work fine and pass balance checks. SELL orders fail with "not enough balance → balance 0". I've called `setApprovalForAll` on the CTF ERC-1155 contract via the WALLET batch endpoint — the transaction mines successfully (nonce increments, STATE_MINED confirmed), but when I check `isApprovedForAll` on-chain, it returns False. The approval simply isn't landing. Same behaviour for `approve()` on the pUSD ERC-20 — mines fine but allowances remain 0 on-chain. Is there a specific way to set CTF ERC-1155 approvals from a deposit wallet on a post-April 28 account? Is the WALLET batch endpoint the correct mechanism, or is there a different call encoding / flow required for this account type? Any help appreciated!

jjwarr 2026-07-02 06:20:09 ↗ Polymarket

Hey all — not sure if this is an ongoing bug CTF approval issue on a post-April 28 Magic.link email account. I'm using signature type POLY_1271 (sig_type=3). BUY orders work fine and pass balance checks. SELL orders fail with "not enough balance → balance 0". I've called `setApprovalForAll` on the CTF ERC-1155 contract via the WALLET batch endpoint — the transaction mines successfully (nonce increments, STATE_MINED confirmed), but when I check `isApprovedForAll` on-chain, it returns False. The approval simply isn't landing. Same behaviour for `approve()` on the pUSD ERC-20 — mines fine but allowances remain 0 on-chain. Is there a specific way to set CTF ERC-1155 approvals from a deposit wallet on a post-April 28 account? Is the WALLET batch endpoint the correct mechanism, or is there a different call encoding / flow required for this account type? Any help appreciated!

Hey all — not sure if this is an ongoing bug CTF approval issue on a post-April 28 Magic.link email account. I'm using signature type POLY_1271 (sig_type=3). BUY orders work fine and pass balance checks. SELL orders fail with "not enough balance → balance 0". I've called `setApprovalForAll` on the CTF ERC-1155 contract via the WALLET batch endpoint — the transaction mines successfully (nonce increments, STATE_MINED confirmed), but when I check `isApprovedForAll` on-chain, it returns False. The approval simply isn't landing. Same behaviour for `approve()` on the pUSD ERC-20 — mines fine but allowances remain 0 on-chain. Is there a specific way to set CTF ERC-1155 approvals from a deposit wallet on a post-April 28 account? Is the WALLET batch endpoint the correct mechanism, or is there a different call encoding / flow required for this account type? Any help appreciated!