Solana Drops Beta Label After Six Years as Network Moves to Version 1.0

Solana officially drops its mainnet-beta label after six years, introducing protocol versioning across Agave and Firedancer following Alpenglow.

Solana

Key takeaways

  • Solana officially removes mainnet-beta designation after six years
  • Version 1.0 introduces shared protocol numbering across validators
  • Firedancer and Alpenglow support the network's technical transition

Solana has officially dropped its mainnet-beta designation after more than six years, introducing Solana 1.0 as the blockchain moves toward a more standardized infrastructure model.

In a November 16 announcement, the Solana Foundation confirmed that the network will now be referred to as mainnet, with a unified protocol version independent of validator software developed by different engineering teams.

The change follows October's Alpenglow consensus upgrade, which targeted transaction finality of approximately 150 milliseconds.

Solana 1.0 Ends Mainnet Beta Era

Solana launched in March 2020 under the mainnet-beta designation, reflecting its early development stage. Despite processing transactions and supporting decentralized applications for years, the label remained unchanged.

The Foundation said the new designation recognizes improvements in performance, resilience and developer experience rather than introducing an entirely new blockchain.

Existing SOL holdings, accounts, smart contracts and transaction histories remain unchanged. Users do not need to migrate tokens, update wallets or take additional steps.

The transition also follows years of work addressing Solana's network stability, including validator software improvements and changes to consensus infrastructure.

Unlike a conventional software release, Solana 1.0 primarily establishes a clearer distinction between the blockchain's shared rules and the software used to operate it.

Firedancer and Agave Move Under Shared Protocol Versioning

One of the most important changes concerns Solana's validator infrastructure.

The blockchain currently supports different validator implementations, including Agave, developed by Anza, and Firedancer, developed by Jump Crypto.

These clients operate using separate codebases, software versions and release schedules while following the same underlying blockchain rules.

Under Solana 1.0, developers can identify the protocol version supported by each client without relying on individual software version numbers.

The Foundation coordinated the transition with Anza and Firedancer developers, building on previous validator infrastructure improvements.

Independent clients can also improve resilience by reducing the network's dependence on a single software implementation.

However, multiple clients do not eliminate operational risks. Solana has previously experienced validator-related security incidents, including a recent five-operator compromise.

What Does Solana 1.0 Mean for SOL and Developers?

The transition does not directly change SOL's circulating supply, transaction fees or staking rewards.

Instead, developers and infrastructure providers gain a clearer framework for tracking protocol changes and determining which validator releases support upcoming network features.

That distinction could become increasingly relevant as Solana expands institutional services, including its recently announced DTCC tokenization integration, targeted for the second half of 2027.

The network's technical progress has nevertheless unfolded alongside substantial SOL price volatility, demonstrating that infrastructure improvements do not necessarily produce immediate market gains.