Skip to content
News on crypto, fintech and digital infrastructure

News Solana

Solana 1.0 Replaces Mainnet Beta Label After Six Years of Network Operation

The Solana Foundation ended the mainnet beta label on November 16, 2026, and introduced Solana 1.0 as the network's shared protocol version.

Rating 4.5 35 votes
Solana 1.0 typography with official logo on a sleek tech monolith under dramatic crimson editorial lighting.

On November 16, 2026, the Solana Foundation retired the mainnet beta label that had been in place since the network's March 16, 2020 launch and introduced Solana 1.0 as the shared protocol version. The change marks the network's formal transition to mainnet status without altering any user balances, assets or transaction history.

Solana 1.0 Separates Protocol Version From Client Software Releases

The Solana Foundation coordinated the update with the Anza and Firedancer teams. Solana 1.0 now defines the shared rules that all validators follow, while individual client implementations such as Agave and Firedancer keep their separate codebases, release schedules and version numbers. No user action is required, and existing SOL holdings, accounts and applications continue without interruption.

Diagram showing Solana 1.0 protocol branching into independent Agave and Firedancer client software modules.
Solana 1.0 standardizes core rules while client implementations evolve independently.

The official Solana account announced the shift with the message “mainnet-beta → mainnet. Introducing Solana 1.0.” Protocol versioning helps track network rule changes, yet client-specific upgrades and activation points remain independent. Documentation and developer tools will receive gradual updates to reflect the new nomenclature.

The move follows the October 21, 2026 activation of Alpenglow, which replaced TowerBFT consensus at slot 459,653,000 and reduced expected transaction finality to roughly 150 milliseconds. Firedancer, developed by Jump Crypto, reached mainnet in December 2025 to improve client diversity and overall resilience. These prior upgrades provided the performance and stability basis for the label change.

Network Continues Standard Upgrade Processes After Label Retirement

The Solana Foundation stated that Solana 1.0 recognizes progress in network performance, resilience and developer experience, while noting that such progress continues through existing processes. The network has operated as a live production system since genesis, and the nomenclature adjustment simplifies references without introducing new features or mandatory migrations.

Developers and operators can track protocol changes through the new version number, but they must still monitor client-specific releases for any required updates. Ongoing work on validator software and future protocol improvements will proceed through established governance and activation channels rather than any one-time event tied to the 1.0 designation.

Market participants and infrastructure providers have received advance notice of the label retirement. Validators, exchanges and wallet services reported no operational adjustments needed beyond routine documentation reviews. The change affects only descriptive terminology used in network communications and public materials.

Frequently asked questions

What does the Solana 1.0 label change?

It retires the mainnet beta designation and establishes Solana 1.0 as the shared protocol version that defines validator rules. Individual client software versions continue under separate numbering.

Do Solana users need to take any action after the update?

No action is required. SOL balances, accounts, assets and transaction history remain unchanged, and fees and operations continue without modification.

How does Solana 1.0 relate to Alpenglow and Firedancer?

The label change follows Alpenglow's October 2026 activation and Firedancer's earlier mainnet deployment. These upgrades improved finality and client diversity before the protocol version was introduced.

Will future Solana upgrades still require separate client releases?

Yes. Protocol version numbers track shared rule changes, while Agave, Firedancer and other clients retain independent release schedules and activation processes.

Comments

No comments yet. Be the first!

Leave a comment