Solana Retires ‘Mainnet Beta’ Label and Adopts Protocol Version 1.0
The Solana Foundation has replaced the network’s long-standing “mainnet beta” designation with Solana 1.0, creating a shared protocol version separate from individual validator-client releases.
The Solana Foundation has retired the network’s “mainnet beta” label and introduced Solana 1.0 as a shared protocol version. The change is intended to reflect progress in performance, resilience and developer experience while separating network-wide protocol status from the software versions used by validator operators.
What Changed
Solana’s new version designation applies to the protocol itself, rather than to any specific validator client. Clients including Agave and Firedancer will continue to maintain their own version numbers, release schedules and upgrade guidance.
The foundation said the nomenclature change does not require action from users. SOL holdings, transaction histories and accounts remain unaffected, and the announcement does not represent a separate token or a new chain.
For developers and validators, the distinction is operationally important. Assigning a protocol version does not automatically activate every network improvement associated with the broader Solana roadmap. Operators should therefore continue following the release instructions for their selected client.
- Solana 1.0: A shared designation for the network protocol.
- Agave and Firedancer releases: Independent software versions maintained by separate client teams.
- User impact: No changes required to wallets, balances, accounts or transaction histories.
A Milestone for Network Infrastructure
The label change arrives after a series of infrastructure developments. In October, Solana activated Alpenglow, a consensus upgrade designed to reduce transaction finality from approximately 12.8 seconds to about 150 milliseconds.
Meanwhile, Firedancer, developed by Jump Crypto, went live on Solana mainnet in December 2025. Its independent codebase gives the network an alternative to Agave and supports client diversity, a key consideration for resilience and validator operations.
The foundation framed Solana 1.0 as a simplification of nomenclature rather than a single technical activation. That distinction allows protocol progress to be communicated at the network level without implying that every client is running identical software or that all roadmap features have become active simultaneously.
The timing also coincides with expanding external interest in Solana’s infrastructure. The Depository Trust & Clearing Corporation plans to connect its tokenization service to the network in the second half of 2027, while Formation Securities has notified the SEC of plans for a tokenized securities venue targeting early 2027. Schroders also launched a tokenized emerging-markets debt fund on Solana through Centrifuge.
What This Means
For markets and ecosystem participants, Solana 1.0 is primarily a credibility and communications milestone. Dropping “beta” signals that the foundation considers the network mature enough for a conventional protocol designation, while preserving the flexibility for multiple validator clients to evolve independently.
The change may support institutional and developer confidence, particularly as tokenization projects evaluate long-term infrastructure. However, the label itself does not guarantee faster finality, improved reliability or automatic access to future features. Those outcomes will continue to depend on upgrades, client adoption and validator execution.











