Solana, one of the leading layer-1 blockchains, has officially concluded its mainnet-beta phase after more than six years, moving the network to mainnet 1.0. This shift marks a new phase in Solana’s evolution, highlighting its transition towards a standardized infrastructure while retaining its original blockchain foundation.
Network moves to unified protocol version
The Solana Foundation, the non-profit organization that supports the network’s development, stated that Solana will now be known as “mainnet,” with a protocol versioning system that is independent from the varying validator software used by developer teams.
Previously, the network retained its “mainnet-beta” status, reflecting an ongoing commitment to active development since its launch in March 2020 despite years of operational use and decentralized application deployment. The mainnet 1.0 designation comes after substantial infrastructure improvements, most notably the October Alpenglow consensus upgrade, which set the network’s transaction finality target at 150 milliseconds.
While Solana has supported real transactions, smart contracts, and applications for years, the mainnet 1.0 naming signals progress in performance, reliability, and the developer experience, according to the Solana Foundation.
The Foundation emphasized that existing SOL balances, transaction histories, accounts, and smart contracts remain completely unaffected. Users do not need to update wallets, migrate tokens, or take any special action as part of this transition.
Validator diversity and protocol standardization
Solana has made significant changes to its validator infrastructure. In addition to the primary client maintained by Anza (previously Solana Labs), the network supports independent validator clients such as Firedancer, developed by Jump Crypto.
These validators function on unique codebases and follow their own software release schedules, although they all implement the same core blockchain specifications. The new approach allows developers to reference the protocol version that a validator client supports, rather than relying solely on specific software version numbers.
Collaboration between the Solana Foundation and teams behind Agave and Firedancer clients has been central to this transition. The outcome is increased resilience for the network, as diversity among validator clients helps reduce the risk of network outages or exploits linked to a single software implementation.
Mini dictionary: Firedancer is a high-performance Solana validator client developed by Jump Crypto, aiming to increase network speed and reliability. Agave is another validator client for Solana, developed by Anza, which enhances decentralization by offering an alternative to the primary validator software.
Despite improvements, the Solana Foundation cautioned that diversity in validator clients does not remove all operational risks. The network has previously encountered validator security incidents, including a compromise involving multiple operators.
| Validator Client | Developer | Status |
|---|---|---|
| Agave | Anza | Active |
| Firedancer | Jump Crypto | Active |
The protocol versioning also makes it easier for developers and infrastructure providers to track network upgrades and maintain compatibility as Solana introduces new features.
No changes for users, future institutional focus
The shift to Solana 1.0 does not affect the circulating supply of SOL, transaction fees, or staking rewards. Accounts and user-facing services will operate as before, with no migration or additional requirements.
Looking ahead, the protocol’s updated structure is expected to support Solana’s expansion in institutional markets, including its planned integration with the Depository Trust & Clearing Corporation (DTCC) for tokenization services in the second half of 2027.
Solana’s ongoing technical development has unfolded alongside significant price volatility for its native token, highlighting that infrastructure enhancements may not lead to immediate shifts in market value.
Solana’s transition to a formal mainnet protocol version establishes a more transparent foundation for future upgrades, as multiple validator clients and institutional integrations become increasingly important for scaling the network.






