Skip to content
Advertisement
Solana drops the mainnet beta label and introduces Solana 1.0

Solana drops the mainnet beta label and introduces Solana 1.0

Solana logo, official brand asset from solana.com/branding. Alpenglow is a Solana consensus upgrade.

The Solana Foundation retired the network's long-running beta tag, and balances, accounts, and transaction histories stay exactly as they were

Solana is no longer in beta. The Solana Foundation has formally retired the “mainnet beta” designation and introduced Solana 1.0, a unified protocol version for the network.

The announcement came on November 16, 2026. It moves Solana from “mainnet beta” to a plain “mainnet” designation. That ends a label the chain carried for years while it processed real transactions with real money.

What changed, and what stayed put

Users do not need to do anything. SOL token balances are unaffected. So are accounts and transaction histories.

The more technical change is how Solana numbers its protocol. Under the new structure, protocol versioning is separate from the versions of individual validator client software, such as Agave and Firedancer.

Splitting them means “Solana 1.0” describes the rules of the network. It no longer describes any single team’s code release. For developers and node operators, that should make it clearer which rules are live, whichever client a validator runs.

Advertisement

The upgrades behind the rename

The relabeling follows a stretch of deep engineering work on the network. Two upgrades stand out in the foundation’s framing of why the beta tag could finally go.

The first is Alpenglow, a consensus upgrade. Alpenglow brings transaction finality down to approximately 150 milliseconds.

Alpenglow is also part of a broader overhaul. Solana has been replacing core pieces of its original consensus design with faster, more efficient alternatives.

The second upgrade is the deployment of Firedancer, a new independent validator client. It is designed to make the network more resilient and to add software diversity.

Agave and Firedancer now sit side by side as distinct clients. That makes the decision to decouple protocol versions from client versions look less like housekeeping and more like a necessity.

Why a label is worth announcing

Dropping it is a statement of confidence. The foundation is signaling that it considers the network mature. That signal rests on faster consensus through Alpenglow and a more diverse validator setup through Firedancer.

The market’s reaction appeared muted. That fits the announcement’s emphasis on continuity over new features.

What this means for SOL holders and builders

For SOL holders, the immediate practical impact is nil by design. There are no migrations, no token swaps, and no action items.

Developers get a cleaner mental model. With a single protocol version to target, they can reason about network behavior without tracking which validator client release happens to be dominant. Operators gain similar clarity when deciding which client to run.

There are also risks worth watching. Running multiple clients brings resilience, but it also brings coordination work. Each client has to implement the same protocol rules correctly, and divergences between implementations can create their own problems. The new versioning scheme is partly built to manage exactly that.

Disclosure: This article was edited by Estefano Gomez. For more information on how we create and review content, see our Editorial Policy.