Joerg Hiller Aug 12, 2026 18:41
Stellar (XLM)’s Protocol 28 introduces faster consensus, atomic contract upgrades, and migration-friendly data, enhancing scalability and developer experience.
Stellar (XLM) has officially rolled out Protocol 28, dubbed “Adapter,” a significant upgrade aimed at developers. The release brings faster consensus, atomic upgrades for contract fleets, and more flexible contract data migration tools. These changes are designed to improve the scalability and resilience of the Stellar network, which currently trades at $0.196853 as of August 12, 2026.
Faster Consensus with CAP-83
A core improvement with Protocol 28 is CAP-83, which enhances the network’s consensus speed under heavy load. Validators can now begin voting on transactions before receiving the full transaction set, bypassing delays caused by slow data propagation. This upgrade ensures smoother throughput and maintains low operational costs, positioning Stellar as a robust option for scaling decentralized applications.
The performance boost will be phased in post-mainnet activation as Stellar enables parallel transaction-set downloading. Importantly, developers consuming raw ledger data should note a new value type introduced with this change, which may require updates to their systems.
Atomic Upgrades for Contract Fleets (CAP-85)
For projects deploying large fleets of contracts, CAP-85 introduces externally managed executables. Contracts can now point to a single shared, updatable code reference. This allows for seamless, atomic upgrades across all linked contracts, eliminating risks of inconsistent states during updates.
This feature mirrors the beacon proxy pattern seen on other chains, simplifying deployment management and making upgrades safer for developers managing extensive ecosystems on Stellar.
Migration-Friendly Contract Data (CAP-86)
CAP-86 tackles a pain point for developers—evolving contract data schemas. Traditional methods required exact matches between data structures, complicating upgrades and leaving some contracts stuck. The new “sparse” host functions allow contracts to handle missing or extra fields without failure, offering a safer, more flexible way to migrate data.
Developers can leverage this feature by rebuilding against the updated Stellar SDK once it becomes available. Migration guides will provide further details to ease the transition.
Protocol 28: A Step Forward in Soroban Evolution
Protocol 28 is also notable for its impact on the Soroban smart contract platform. It marks the mandatory adoption of AddressV2 for authorization, phasing out legacy credentials introduced in Protocol 27. The migration to AddressV2 is set to improve security and enable advanced features like delegated authorization. Developers will need to update their SDKs to accommodate this shift as RPC simulation defaults flip to AddressV2 with this upgrade.
What’s Next for Stellar?
While Stellar has yet to announce an official activation date for Protocol 28 on the mainnet, the upgrade signals the network’s ongoing focus on scalability and developer usability. With Protocol 27 laying the groundwork for Soroban enhancements, Protocol 28 pushes the ecosystem further toward seamless contract management and robust infrastructure.
As Stellar continues to evolve, its upgrades may position it as a competitive option for developers seeking scalable solutions. Traders and investors should watch for further announcements on Protocol 28’s mainnet activation and adoption metrics, particularly as the platform solidifies its smart contract capabilities.
Image source: Shutterstock Source
