Stellar (XLM) Mainnet Activates Protocol 28 “Adapter” With Contract Data Migration

Protocol 28 Goes Live on Mainnet

Stellar (XLM) is now running Protocol 28 on its mainnet, an upgrade code-named “Adapter” that went live on September 16, 2026 at 17:00 UTC and opens a working path for migrating stored smart contract data. The change targets Soroban developers and node infrastructure rather than everyday wallet and payment users, and market data shows no confirmed causal link between the activation and the Stellar (XLM) price in spot trading. Earlier technical coverage tracked the token breaking above its 50-week moving average with $0.2227 in sight, but this upgrade is a network event, not a price event. The Stellar Development Foundation built the release around three core advancement proposals: CAP-86, CAP-85 and CAP-83, with the official software version documentation dating the Protocol 28 mainnet build to September 16. Soroban, the smart contract platform integrated directly into the Stellar network rather than a separate sidechain, executes Rust programs compiled to WebAssembly.

Before Adapter, a contract reading data from the ledger demanded an exact match: every field of a struct had to be present as a key, and no extra key could exist. A missing or unexpected field could break the read outright. CAP-86 relaxes that constraint with sparse host functions that tolerate missing or added fields, so legacy storage moves into a new schema in stages instead of being discarded in one cut.

CAP-85 addresses a separate bottleneck. It supports externally managed references to executable code, meaning a bundle of contracts sharing the same program can be upgraded by switching one reference instead of replacing each instance. That cuts mixed-version fleets during large operations, though each developer still has to check that new code fits the old data.

CAP-83 works at the consensus mechanism level: validators may begin voting before a full transaction set arrives, and a discard procedure removes sets that land late or fail validity, easing stalls tied to data propagation. Parallel transaction-set downloads arrive in stages after the mainnet cut. Validator operators are advised to check clock synchronization, while indexers and data pipelines that read the ledger directly must handle the new ledger value types.

Soroban SDK v28 and 11 Years of Stellar

The developer tooling caught up on September 30. Version 28 of the Soroban Rust SDK shipped that day, and the Build on Stellar account confirmed the release on X in a summary attributed to Leigh McCulloch, principal software engineer at Stellar. SDK v28 supports Protocol 28 and carries build system changes plus new behavior for contract data migration. For most contracts, the release says, the change is a rebuild and nothing else. Its feature list includes Spec Shaking v2, which applies dead code elimination to how specs ship: the SDK emits an entry for everything, and the stellar-cli build then strips entries the contract does not use. Further additions cover sparsely published events, executable references, and native contracts that can be uploaded in tests. The migration support lands where it matters, because a struct lives on the ledger as a map keyed by field names, and v28 lets a contract read that map even when its fields differ from the original write.

@BuildOnStellar · X post

Confirmed the release on X.

View on X

The date is also the network’s 11th birthday. Stellar ecosystem history runs longer than its ledger: the network launched on September 30, 2015, and head of product Tomer Weller has noted the anniversary belongs to the “new” Stellar network, while an earlier 2014 version ran under the ticker STR. Recent milestones point at real-world rails: the network passed 22,000 holders of tokenized real-world assets, and deployments such as MoneyGram’s Visa stablecoin card pilot in Colombia keep building on that direction.

The Migration Step That Stays Manual

Read against the official release documentation, both items trace one arc: contract data that can change shape over a network’s lifetime. The Protocol 28 notes date the mainnet version to September 16, 2026, require a rebuild on the Soroban Rust SDK 28.0.0, and instruct developers to reproduce old state and verify that a new contract reads it before calling migration done. Node operators carry the near-term load: indexers and data pipelines must process the new ledger value types, and validator clock synchronization needs checking. Enterprise work on the network, including U.S. Bank’s USBDC stablecoin tests, shows why upgradeable contract data matters at scale. What survived the change unchanged is the manual step: nothing migrates on its own.