Stellar is preparing its next major network upgrade, and Protocol 28, known as Adapter, is aimed squarely at making the network easier to build on and more resilient as activity grows.
The upgrade introduces three key changes. CAP-83 is designed to improve consensus performance when transaction data is slow to propagate, while CAP-85 and CAP-86 focus on making Soroban smart contracts easier to upgrade and migrate.
For the Stellar community, this is less about a headline-grabbing new feature and more about improving the infrastructure underneath the applications being built on the network.
Adapter Could Make Stellar Smart Contracts Easier to Manage
One of the biggest changes in Protocol 28 is CAP-85, which introduces a way for multiple contracts using the same underlying code to share an externally managed executable reference.
That means developers managing large fleets of similar contracts can update the shared reference rather than upgrading every contract individually.
The practical benefit is significant. A security fix or software improvement can be rolled out across an entire fleet atomically, reducing the possibility that some contracts run updated code while others remain on an older version. Stellar describes the approach as comparable to the beacon-proxy pattern familiar to developers on other smart-contract networks.
Related: Stellar Powers New Barça Mobile Wallet for Payments, Rewards and Global Transfers
CAP-86 tackles another problem developers eventually face: data migration.
Smart contracts change over time. Their data structures may need new fields, removed fields or other modifications. Protocol 28 introduces sparse host functions that allow contracts to handle missing or additional fields more gracefully during these migrations.
That could make long-lived Soroban applications easier to maintain.
Stellar Is Also Targeting Faster Consensus
The third major component is CAP-83.
Today, validators need transaction sets to propagate through the network before certain consensus steps can move forward. CAP-83 changes that process by allowing validators to begin voting before the complete transaction set has arrived and providing a mechanism to discard transaction sets that are late or invalid.
The objective is to prevent slow transaction propagation from unnecessarily holding up consensus.
Stellar says the improvement should strengthen throughput and network performance as the blockchain scales, with the full benefits expected to appear gradually as parallel transaction-set downloading is enabled after mainnet.
Importantly, this is largely a behind-the-scenes upgrade for users.
There is no new token to claim and no migration required for ordinary XLM holders simply because of the protocol changes.
Instead, the focus is on making the network underneath applications more efficient.
Protocol 28 Timeline Is Already Set
The rollout has moved into its preparation phase.
Stellar Core’s stable release for Protocol 28 became available on August 13, 2026, followed by additional infrastructure and SDK releases expected through August 21.
The next major milestone is the testnet upgrade vote on August 27 at 17:00 UTC.
If the process proceeds as planned, the mainnet upgrade vote will take place on September 16 at 17:00 UTC.
That gives developers, validators, infrastructure providers, wallets, exchanges and other ecosystem participants time to prepare.
Stellar has also advised typical SDK-based integrations to update their SDK versions ahead of the relevant testnet and mainnet deadlines.
What Does Protocol 28 Mean for XLM?
This is where investors need to separate network development from token price.
Protocol 28 is positive for Stellar’s technical infrastructure, but the upgrade does not automatically mean XLM will rise.
The longer-term question is whether better infrastructure leads to more developers, applications, transactions and financial activity on Stellar.
Related: Stellar Joins the x402 Foundation to Help Build the Payment Layer for the AI Economy
XLM remains the native asset used for network fees and minimum account balances, while Stellar’s broader ecosystem is focused heavily on payments, asset issuance and financial applications. Regulatory filings have also described XLM as having utility for payment providers, tokenization projects, wallets, exchanges and other Stellar ecosystem participants.
That makes adoption the more important metric to watch.
If Protocol 28 helps developers build larger and more sophisticated applications, its effect on the network could eventually become more meaningful than the initial upgrade announcement itself.
The Bigger Stellar Story
Adapter arrives as Stellar continues expanding its smart-contract capabilities through Soroban.
The timing is important because blockchain competition is increasingly moving beyond transaction speed. Developers also care about upgradeability, security, tooling, interoperability and the ability to maintain applications after they go live.
Protocol 28 addresses several of those practical issues.
CAP-85 makes contract fleet upgrades safer.
CAP-86 makes data migrations easier.
CAP-83 strengthens the consensus layer supporting everything else.
Together, they represent a relatively focused upgrade, but one aimed at problems developers actually encounter when applications become larger and more complicated.
Related: Stellar Introduces On-Chain Analytics Platform Powered by Allium Labs
For the Stellar community, that is arguably the most important part.
Adapter is not designed to create a short-term XLM narrative. It is designed to make Stellar a better platform to build on.
The next milestone is the August 27 testnet vote, followed by the scheduled September 16 mainnet vote.
If the upgrade passes and the promised improvements translate into stronger developer activity, Protocol 28 could become another important piece of Stellar’s longer-term push toward becoming infrastructure for real-world financial applications.
And for XLM holders, that is the story worth watching: not simply what Adapter does on launch day, but what developers build with it afterward.
About The Author
