0x472147914721…4721478e
Solana Sheds Mainnet Beta Label, Declares Solana 1.0
Solana dropped its mainnet-beta label and introduced Solana 1.0 on November 16, after the Alpenglow consensus upgrade and Firedancer client deployment. No user action is required.

Outputs
The Solana Foundation announced Solana 1.0 on Monday, November 16, ending a mainnet-beta label that lasted more than six years.
Alpenglow, the consensus upgrade behind the transition, delivers transaction finality in approximately 150 milliseconds.
Firedancer, an independently developed validator client, is now deployed alongside Agave under a shared protocol version.
Agave and Firedancer will keep separate software versions and release schedules while supporting the same protocol.
The Foundation confirmed no impact on SOL holdings, accounts, applications, or transaction histories, and no user action is required.
The Solana Foundation officially retired the network's mainnet-beta designation on Monday, November 16, and introduced Solana 1.0, closing a classification chapter that had run for more than six years. The Foundation said it coordinated the rollout with the Anza and Firedancer teams, and that the change requires no action from users.
The announcement is a labeling and governance milestone rather than a technical fork. Solana 1.0 introduces a shared protocol version that exists independently of individual validator software releases. Under the new framework, Agave and Firedancer will maintain separate software versions and separate release schedules while supporting the same underlying Solana protocol.
Why did the label change now?
The Foundation tied the transition to two engineering developments. The first is the activation of Alpenglow, a consensus upgrade that delivers transaction finality in approximately 150 milliseconds — roughly one-fifteenth of a blink of a human eye, and a figure the network could not claim at launch. The second is the deployment of Firedancer, an independently developed validator client built to improve network resilience and reduce the ecosystem's reliance on a single codebase.
The sequencing matters. Client diversity addresses a specific operational risk: a bug in one validator implementation cannot bring down an entire network when a second, independent client carries part of the load. The Foundation presented the two-client structure as a precondition for the 1.0 label, not an afterthought. In plain words: the network graduated only after it had both speed and redundancy.
What does the change mean for users and developers?
The Foundation said existing SOL holdings, accounts, applications, and transaction histories remain unaffected. Users are not required to take any action — though users facing a network relabeling rarely do, and the Foundation's assurance here matches what the technical record already implied.
Developers and validator operators face the more consequential shift. They will continue following individual software updates and activation schedules, because the 1.0 designation does not automatically activate future network upgrades. The version is a reference point, not an autopilot. Documentation, block explorers, and other ecosystem services will adopt the new naming convention gradually, which means mixed terminology will likely persist across the ecosystem for some time.
What is left unsaid?
The Foundation's statement does not specify which upgrade criteria, if any, apply to a future Solana 2.0 designation, nor does it publish a formal versioning policy document alongside the announcement. The 150-millisecond finality figure also deserves a caveat: it describes a protocol capability under the upgraded consensus, not a guaranteed user experience under congestion or network partition conditions.
The institutional read is straightforward. A six-year beta label had become a reputational liability for a chain courting enterprise and institutional integrations, where beta status invites procurement and audit questions. The change signals operational maturity; it does not by itself alter throughput, fees, or validator economics. Whether the shared protocol version simplifies coordination between the Agave and Firedancer release tracks — the practical test of this framework — will become visible as the two clients' schedules diverge over the coming quarters.
via solana.com (Original)
More from Elena Vasquez
Show full bio
Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.
1,525 articles