Protocol 28, nicknamed Adapter, is a Stellar network upgrade that changes how validators reach consensus and how Soroban smart contracts get upgraded. The Stellar Development Foundation (SDF) set a testnet vote for August 27, 2026 at 1700 UTC and a mainnet vote for September 16, 2026 at 1700 UTC. Stellar Core’s stable release came out on August 13, 2026, with infrastructure and SDK releases following from August 13 to 21.
Who Benefits and How
Mostly developers and node operators, at least at first. Contract teams get new, opt-in tools for upgrading code and moving data. Ordinary Stellar users won’t see a switch flip: the SDF says the consensus gains are phased in after mainnet activation, and it publishes no speed figures. Anything users notice would come later, through the apps those developers build.
What Adapter changes
The upgrade bundles three Core Advancement Proposals (CAPs), which are Stellar’s formal documents for protocol changes. The descriptions below come from the SDF announcement and upgrade guide.
CAP-83 (consensus). Validators can start voting before they receive the full transaction set, and they can drop a late or invalid set instead of stalling. The SDF says the full performance gains arrive as parallel downloading of transaction sets is gradually enabled. The change adds a new empty-set value type, so teams that process raw ledger data need to handle it.
CAP-85 (shared contract code). A contract can point to a shared, updatable code reference owned by another contract. Update that one reference and every contract pointing to it is upgraded at once. The SDF compares this to the beacon proxy pattern. Teams opt in by rebuilding against the updated Soroban SDK.
CAP-86 (data migration). New sparse host functions handle missing or extra fields instead of failing, which gives developers a supported way to move contract data to a new schema gradually. This one is also opt-in through the updated SDK.
Who had to act, and where activation stands
The upgrade guide says SDK users should upgrade before the relevant vote, and most only need a version bump. Infrastructure operators needed the Protocol 28 builds. Validators had to install the release, arm the upgrade, and keep clocks synced with NTP, which the guide says is required from Protocol 28. Smart contract teams don’t have to do anything to stay compatible, since CAP-85 and CAP-86 are opt-in. The SDF pages we opened describe the upgrade as scheduled. A September 20, 2026 Blockonomi report, republished by edgeX, says it went live after a validator vote in September but gives no exact date, and we found no SDF confirmation, so check Stellar’s developer channels. The guide also lists a mainnet vote of September 16 in its key dates but September 9 in one validator instruction, and the SDF page advises confirming the date with the community. The same report cites a sustained 211 transactions per second over 100 consecutive ledgers, sourced to a social media post using Chainspect data and not attributed to Protocol 28 alone, so treat it as unverified. Shared upgradable code also concentrates risk: a mistake in a shared reference would reach every contract pointing to it, so access control over that reference matters.
Quick answers
Is Protocol 28 live on mainnet?
The Blockonomi report says it went live after a September validator vote. We could not confirm the exact date from an SDF source.
Does Adapter make Stellar payments faster?
The SDF describes consensus improvements in CAP-83 but publishes no throughput or latency numbers, and says gains arrive in phases after mainnet. No source we opened measures a speedup.
Sources
- Stellar Development Foundation: Introducing Adapter, Protocol 28 on Stellar (accessed Oct 13, 2026)
- Stellar Development Foundation: Adapter Protocol 28 Upgrade Guide (accessed Oct 13, 2026)
- edgeX News (republishing Blockonomi): Stellar Protocol 28 “Adapter” Goes Live on Mainnet as Network Posts 211 TPS Record (Sep 20, 2026)
