Stellar Development Foundation team discusses critical decision on how stellar assets are represented in Soroban: single balance approach (assets stored in trust lines, exposed via Soroban interface) versus dual balance approach (separate Soroban and classic balances). Community consensus strongly favors single balance for simplified user experience and ecosystem interoperability.
The Stellar Development Foundation held a technical discussion on representing stellar assets in Soroban smart contracts. The core decision centers on two approaches: dual balances (separate Soroban token balances and classic trust line balances) versus single balance (assets stored only in trust lines, exposed through a built-in contract interface). Speakers explored tradeoffs including security implications, performance considerations, downstream system impacts (Horizon), opt-in semantics for contracts, and compatibility with classic operations. Key concerns included approval surface area risks, 64-bit integer constraints on classic assets versus 128-bit Soroban interface, and whether to maintain separate native Soroban token contracts. The discussion revealed overwhelming community support for the single balance approach due to improved user experience, reduced friction for wallet developers, and better ecosystem interoperability, though several implementation details remain open questions.