Solana Abandons Mainnet-Beta Status and Introduces Protocol 1.0

The Solana Foundation announced the official discontinuation of the mainnet-beta designation, which has been used since the network's launch. The blockchain will now be called mainnet, and a unified protocol versioning system will be designated as Solana 1.0. The transition is coordinated with the Anza and Firedancer teams and does not imply replacing the existing network or altering its data.
What will change after the transition to Solana 1.0
According to the Solana Foundation, the transition does not require any additional actions from regular users. SOL tokens, wallet addresses, accounts, digital assets, applications, and transaction history remain unchanged.
The foundation explained that Solana has effectively operated as a full-fledged production network since its launch, despite using the mainnet-beta designation. Dropping it reflects accumulated technical changes and the development of blockchain infrastructure.
The main innovation is a unified protocol versioning system, independent of the software of individual validators.
Previously, clients Agave and Firedancer used their own version numbering and separate update release schedules. Now developers and infrastructure operators can rely on a common protocol version to determine which features are supported by specific client versions.
However, the announcement of Solana 1.0 does not mean the simultaneous activation of all network updates. Software releases and the implementation of new features will still follow separate schedules.
How Alpenglow and Firedancer are related to the transition
One of the prerequisites for dropping the mainnet-beta status was the modernization of Solana's consensus mechanism.
On October 21, 2026, the Alpenglow update was activated in the main network, replacing the previous TowerBFT transaction agreement mechanism. Developers claim the new protocol is designed to finalize transactions in approximately 150 ms instead of about 12.8 seconds with the previous mechanism.
Finalization means the moment after which the network considers a transaction to be definitively confirmed. The stated 150 ms is a target figure, and actual time may depend on network operating conditions.
Another area of development has been work on Firedancer, an independent validator client created separately from Agave.
Having multiple software implementations of a single protocol reduces the blockchain's dependency on a single codebase. If an error occurs in one client, its impact can potentially be limited, as other implementations use their own code.
What developers and validators need to consider
The Solana Foundation recommends that application developers continue to monitor changes in API, SDK, and the infrastructure in use.
Operators of validators and RPC nodes need to check which client versions are compatible with specific protocol updates and follow the appropriate installation and activation instructions.
Documentation, blockchain explorers, and other ecosystem services will gradually transition to the new mainnet designation.
Thus, Solana 1.0 represents a change in the official status of the network and the approach to protocol versioning. It is intended to simplify infrastructure maintenance as multiple independent validator clients develop, but it does not change the order of executing user transactions.
This material is prepared solely for informational purposes and does not constitute financial advice or a recommendation.





