Stellar activated Yardstick on testnet ahead of its mainnet vote

Stellar activated Protocol 26, codenamed Yardstick, on its test network at 17:00 UTC on April 16, 2026, beginning the final public testing phase before a separately scheduled mainnet validator vote.

The activation was a protocol milestone, not a mainnet deployment. Stellar’s April 1 upgrade guide placed stable software releases on April 8, the testnet change on April 16 and the mainnet vote on May 6. Infrastructure operators and application developers were therefore being asked to test compatible software and integrations against the new protocol while the production network continued operating under its existing rules.

This article is a newly researched reconstruction of the April 16 record. It is not presented as a recovered copy of an article published on that date.

What changed on April 16

A Stellar protocol version is part of the network’s consensus-controlled ledger behavior. Moving testnet to version 26 gave validators, node operators, wallet teams, exchanges and smart-contract developers a shared environment in which to identify incompatibilities before any production vote.

Stellar’s event-day developer notes recorded that Yardstick went live at 17:00 UTC and directed operators toward Protocol 26-compatible nodes, software-development kits and integrations. The foundation’s upgrade guide likewise distinguished between testnet preparation and the later mainnet process. Operators of Stellar Core, Horizon, RPC and Galexie were told to install compatible releases, while SDK users were told to update the components used by their testnet integrations.

The software record supplies another contemporaneous checkpoint. Stellar Core v26.0.1 had been released before the activation and included stability and security-related fixes in addition to its Protocol 26 compatibility. That matters because a protocol rollout is not only a specification change: it also depends on interoperable implementations remaining synchronized under real network conditions.

No event-day evidence cited here establishes that every operator upgraded successfully or that every application was compatible. Testnet activation demonstrates that the network accepted the new protocol version in its testing environment; it does not by itself prove production readiness.

Why the testing window mattered

Stellar was positioning its network for payment, tokenization and smart-contract activity, making predictable protocol transitions important to both crypto-native developers and institutions integrating the ledger. A failed or poorly coordinated upgrade can interrupt transaction submission, indexing, contract simulation or access to network data even when the underlying protocol design is sound.

The April 16 milestone reduced that risk by creating a defined interval between testnet activation and the proposed production vote. Developers could submit transactions, exercise contracts and verify tooling against Protocol 26, while infrastructure operators could observe synchronization and deployment behavior. Problems discovered during that interval could still lead to revised software, changed instructions or a delayed vote.

The central significance was therefore operational rather than market-based. This reconstruction makes no claim that Yardstick caused a movement in XLM or any other asset. Cryptocurrency trades continuously across venues, and no consistent event-window price or volume dataset was necessary to verify the protocol activation.

What remained unresolved

As of April 16, Yardstick was not active on Stellar mainnet. The May 6 date was a scheduled validator vote, not a guaranteed outcome, and the April 16 record could not establish whether validators would approve the change or whether additional defects would emerge.

The activation also did not certify individual applications, contracts, custodians or exchanges. Each integration retained its own testing, security and operational responsibilities.

Later context

Stellar subsequently recorded that Protocol 26 went live on mainnet on May 6, 2026. The foundation’s upgrade-guide changelog says detailed descriptions of Yardstick’s included Core Advancement Proposals were added on April 29. Those later records clarify the completed rollout but do not change the narrower fact knowable on April 16: Protocol 26 had reached testnet, while mainnet approval remained pending.