Stellar Completed Soroban’s Mainnet Rollout

Stellar validators completed the Phase 2 network-settings vote for Soroban on March 19, 2024, making the blockchain’s new smart-contract system available under its production resource limits and fees. The Stellar Development Foundation described Soroban as live on mainnet and open for building, deployment and interaction with decentralized applications.

The development was the operational finish to a deliberately staged launch, not the first activation of Protocol 20. Validators had upgraded Stellar mainnet to Protocol 20 on February 20, beginning Phase 0 with restrictive settings. They raised limits for Phase 1 on February 27 so developers could deploy while operators watched network behavior. The March 19 vote installed Phase 2 settings, moving Soroban into the user-ready stage.

That distinction matters. March 19 did not create another protocol version, and it did not prove that applications had achieved scale. It changed how much smart-contract work the network was configured to accept after two earlier observation periods.

What Soroban added

Stellar had long concentrated on payments, asset issuance and exchange functions built into its protocol. Soroban added a general-purpose contract environment based on WebAssembly, with Rust as the principal development language promoted by SDF. That widened the kinds of software developers could run on Stellar, including lending, trading and other applications whose rules are encoded in contracts.

Protocol 20’s design covered more than contract execution. Its accepted components included contract creation and lifecycle rules, host functions, data storage, authorization, standardized interaction with Stellar assets, fees, resource metering and state archival. The fee model priced categories such as CPU instructions, ledger reads and writes, memory-related limits and transaction bandwidth through network configuration.

On March 19, SDF’s software record listed Soroban Environment v20.2.2, Stellar Core v20.3.0, Soroban Rust SDK v20.4.0, Soroban CLI v20.3.1 and Soroban RPC v20.3.3 alongside Phase 2 resource limits and fees. Those version numbers describe the supported release set preserved in the project’s documentation; they do not show that every operator or application had upgraded immediately.

A launch governed through settings

The rollout showed how Stellar separated protocol capability from usable capacity. Protocol 20 made smart contracts valid on February 20, but validators governed operational limits through later configuration votes. SDF said this was intended to let infrastructure providers observe performance, security and stability before increasing capacity.

That approach reduced the risk of exposing the network to unrestricted new workloads at once, while leaving execution dependent on validator coordination. It also imposed practical work on infrastructure operators. SDF warned that older Stellar Core releases would no longer function correctly with Protocol 20 and that older Horizon instances and software-development kits could fail when encountering unfamiliar Soroban transactions. The compatible Horizon release required a state rebuild, and SDF said it would not provide a free mainnet Soroban RPC endpoint.

The institutional consequence was therefore two-sided: developers gained a programmable layer on an established payments network, while node operators, indexers, wallets and application teams inherited new compatibility and resource-management obligations.

Funding was a commitment, not adoption proof

SDF paired the launch with its previously established $100 million Soroban Adoption Fund. On March 19, the foundation said the fund had supported more than 160 projects and that roughly 15% of the commitment had been deployed during the testing period. These are contemporaneous foundation figures, not audited measurements of active mainnet applications, locked value or user demand.

The Block independently reported on March 19 that Phase 2 was live and characterized Soroban as one of Stellar’s most significant upgrades in its ten-year history. The comparison is reasonable as interpretation: Soroban expanded Stellar from protocol-level payment functions into a general-purpose smart-contract platform. It should not be read as evidence that Stellar had matched Ethereum or any other chain in usage, liquidity or developer activity.

The verified March 19 milestone is narrow but consequential. Stellar’s validators completed the capacity-setting process that made Soroban user-ready on mainnet. Application security, sustained throughput, economic activity and ecosystem adoption remained questions requiring evidence following March 19.