Stellar (XLM) Approaches Protocol 28 Upgrade with Smart Contract Enhancements

iconCrypto Economy
Share
AI summary iconSummary
Stellar (XLM) is set to launch the Protocol 28 network upgrade, also called Adapter, with a focus on improving Soroban smart contracts and network performance. The protocol update brings tools for synchronized contract updates and smoother data migrations, helping developers manage applications more efficiently. Validators will vote on testnet activation on August 27 and mainnet activation on September 16.

TL;DR

  • Stellar is preparing Protocol 28, known as Adapter, with changes focused on Soroban smart contracts and network performance.
  • The upgrade introduces tools for coordinated contract updates and smoother data migrations, making application maintenance easier for developers.
  • Validators are scheduled to vote on testnet activation on August 27 and mainnet activation on September 16, putting the next few weeks in focus for developers and infrastructure providers.

Stellar (XLM) is approaching another significant protocol change as developers and validators prepare for Adapter, or Protocol 28. The upgrade targets Soroban, Stellar’s smart contract platform, while also introducing improvements intended to strengthen performance as on-chain applications become more complex. Stellar’sprotocol upgrades are decided through validator voting rather than a centralized deployment process.

Stellar Prepares For Soroban-Focused Changes

Adapter brings several changes aimed at reducing friction for developers managing smart contracts. CAP-85 focuses on atomic upgrades for groups of contracts that share executable code, allowing developers to update the common reference rather than handling every contract independently. CAP-86 addresses contract data migrations, an important consideration as applications evolve without forcing disruptive redesigns.

The upgrade also builds on Stellar’s broader effort to make Soroban more practical for financial applications. Recent protocol work has targeted network efficiency, including improvements to Soroban state management in Protocol 26. Stellar’s development ecosystem also includes dedicated contract SDKs and tooling for builders working with Soroban.

Another relevant change concerns authentication. Protocol 28 introduces AddressV2, replacing the older Soroban address credential format and giving developers time to migrate applications and dependencies before the transition. The change is part of Stellar’s continuing effort to improve the infrastructure supporting smart contract applications on the network.

Stellar is preparing Protocol 28, known as Adapter, with changes focused on Soroban smart contracts and network performance.

Key Dates Put Developers On Notice

The upgrade schedule now becomes particularly important. August 13 marked the core stable release, while infrastructure and SDK releases are scheduled during the August 13–21 window. The testnet vote is set for August 27 at 17:00 UTC, giving validators and developers an opportunity to evaluate the proposed changes before mainnet activation.

The mainnet vote is scheduled for September 16 at 17:00 UTC. Activation depends on validatorapproval, so the date represents a planned governance milestone rather than a guaranteed launch. Developers running SDK-based integrations should update their dependencies and test their applications ahead of the respective voting dates.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.