Solana Drops Mainnet-Beta Label With New 1.0 Version

Semi-realistic illustration of Solana network with a central Solana 1.0 badge, no beta label, validators connected in a modern data center.

Solana has formally retired the “mainnet-beta” designation it carried for more than six years, introducing Solana 1.0 as a shared protocol version for the network. The change was announced during Breakpoint on November 16 and does not involve a new blockchain, migration or reset of existing state. SOL balances, accounts, applications and transaction history remain on the same production network.

According to the Solana Foundation’s official 1.0 announcement, the new system separates the version of the protocol itself from the releases of validator software implementing it. The Foundation coordinated the change with Anza and the Firedancer team as Solana moves toward multiple independently developed clients. Solana 1.0 gives those clients a common reference for the network rules without forcing them to use identical software version numbers.

One Protocol Version, Multiple Validator Clients

Agave and Firedancer maintain separate codebases, development schedules and release numbering. Under the new structure, different releases of each client can support the same Solana protocol version, while operators continue following client-specific upgrade instructions. A Solana protocol-version announcement therefore does not mean every compatible feature has simultaneously activated across the network.

That distinction matters after several substantial technical changes during 2026. Solana began community validator testing of Alpenglow earlier in the year before the consensus system activated on mainnet on October 21, replacing TowerBFT and targeting approximately 150-millisecond finality. The migration occurred under Agave 4.3, weeks before the Solana 1.0 naming change. Alpenglow is an actual consensus upgrade, whereas dropping the beta label is primarily a versioning and nomenclature change.

Firedancer adds another reason for separating protocol and client versions. It is an independently developed validator implementation rather than another release of Agave, and its current security work includes a bug bounty focused on Alpenglow-compatible configurations. Firedancer’s own network reporting currently identifies multiple validator-client configurations operating on mainnet. Client diversity means Solana increasingly needs a protocol-level identifier that is independent of any one implementation.

The Network Does Not Restart at 1.0

For ordinary users, there is no required action. Wallets do not need to migrate SOL, applications do not need to redeploy because of the rename, and transaction history is unchanged. Documentation, explorers and other ecosystem interfaces will instead update their terminology progressively. Solana 1.0 formalizes how the existing network is described rather than creating a replacement mainnet.

The distinction also prevents software releases from being mistaken for network activations. Agave 4.4.0 and 4.4.1, for example, were published before the 1.0 announcement, while Solana’s upgrade tracker separately identifies which features are live, partially activated, planned or still in development. Similar status boundaries matter for applications such as CoW Protocol’s native Solana trading alpha, where an application deployment stage remains independent of the underlying network’s name. Software shipped, protocol versioned and feature activated remain three different technical states.

Yahoo Finance also characterized the November 16 announcement as Solana’s graduation from the beta designation it had used since its March 2020 launch, while noting that recent milestones included Alpenglow and Firedancer. The significance of 1.0 is consequently structural rather than an immediate performance change: it gives a mature multi-client network a cleaner way to identify the protocol all validators are implementing.

Find Us on Socials

Join Our
Newsletter

Subscribe to get latest crypto news!

Latest News

You may also like

The Chain Observer
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.