Stellar protocol discussion on CAP 46-06 covering the standardized token contract for Soroban smart contracts, including updates to token balances, naming conventions, clawback functionality, and solutions for handling auth-required assets from Stellar Classic.
The Stellar Development Foundation held a protocol discussion focused on CAP 46-06, which defines the built-in token contract for Soroban. Key changes include updating token balances from BigInt to U128, replacing the approved function with increased/decreased allowance methods, and aligning terminology with Stellar Classic (burn to clawback, freeze to authorize/deauthorize). The team discussed how to handle auth-required assets wrapped from Classic, proposing a mechanism where issuers must explicitly authorize new balances on Soroban. Participants debated naming conventions against ERC20 standards, the complexity of supporting auth-required semantics, and whether custom token contracts should be deployed for assets requiring fine-grained control beyond the built-in contract capabilities.