Hi Phantom team, following up on my support ticket, where Yaovi kindly suggested I submit this as a feature request. Thanks for the quick and clear response there. Ticket id: 244867 What I'm asking for Support for the Solana Foundation's sRFC-37 (Token ACL) standard: when Phantom creates an Associated Token Account for a mint that has the token_acl metadata field, it would read that field, resolve the Gate Program accounts, and automatically append the ThawPermissionless instruction so the newly created (frozen) ATA is usable. Why it matters / My case Token-2022's DefaultAccountState = Frozen extension means every new token account starts frozen. sRFC-37 solves this by letting anyone permissionlessly thaw an account for a wallet that a Gate Program approves (e.g. an allow ListConfig). The token_acl metadata field exists specifically so wallets and SDKs can detect these mints without an extra RPC call beyond the mint account they already load. Without wallet-side support, sending such a token to a recipient who has no ATA yet fails with ** 0x11 ( AccountFrozen )** — the ATA gets created but stays frozen. The recipient is fully authorized (on the allow list), but the transfer still fails, which is confusing UX for a token that is supposed to "just work" for approved holders. Having this handled wallet-side would mean approved holders can simply send and receive these tokens like any other SPL token, no failed transfers, no manual thaw step, and no issuer intervention needed. Reference The official Solana Foundation guide describes this flow and names Phantom as a wallet that would handle it automatically: https://solana.com/developers/guides/advanced/acl#token-metadata-for-auto-detection Thanks for considering it!
