Newsroom
16 November, 2026 / News / AI / Tags: solana, agave, protocol, beta, version

The Solana Foundation has ended the long-running mainnet beta designation and introduced a shared protocol version number, with no impact on user holdings or applications
The Solana Foundation announced on November 16, 2026, that the network is retiring the “mainnet beta” label it has carried since its March 2020 launch. The blockchain will now be referred to as Solana Mainnet, while Solana 1.0 becomes the first shared protocol version number describing the network’s underlying rules.
The change was coordinated with the teams behind the Agave and Firedancer validator clients. It marks a shift in how the network tracks its technical evolution rather than a new chain or migration. Solana has processed live transactions, supported applications, and held real assets under the beta designation for more than six years.
Solana 1.0 applies to the protocol itself—the common set of rules that all validators follow. It stands apart from the software version numbers of individual validator clients. Agave, developed by Anza, and Firedancer, built independently by Jump Crypto, each maintain their own release schedules and numbering. Different client releases can support the same protocol version without sharing software version numbers.
This separation aims to give developers, validators, and infrastructure operators a clearer reference point for network compatibility as the ecosystem relies on multiple client implementations. A shared protocol designation helps operators determine which rules their software supports without tying the assessment solely to one client’s release number.
Users are not required to take any action. Balances, wallets, applications, and transaction records stay unchanged. The foundation stressed that announcing a protocol version does not activate every related improvement at the same time. Node operators and developers must still follow the specific upgrade and activation instructions for their chosen client software.
The decision to retire the beta label follows two significant infrastructure developments. The Alpenglow consensus upgrade activated on the network in October 2026. It targets transaction finality of roughly 150 milliseconds, compared with approximately 12.8 seconds under the previous system. Finality is the point at which a transaction is treated as settled and not expected to be reversed.
Firedancer reached mainnet deployment earlier, providing an independent alternative to the Agave client. Running multiple codebases reduces dependence on a single software implementation. A problem in one client does not automatically affect every validator, though the overall benefit depends on how widely the different clients are used across the network.
Documentation, block explorers, and ecosystem tools are expected to update gradually to the new mainnet designation. Upcoming client releases, including planned Agave versions, will continue to follow their own schedules and activation requirements.
Everyday users and SOL holders experience no disruption. Existing holdings and application interactions continue without modification. Developers should monitor updates to APIs, SDKs, and infrastructure components through the network’s regular changelogs and upgrade trackers. Validator and RPC operators need to verify which client releases support each protocol rollout and complete the corresponding upgrade steps.
The introduction of formal protocol versioning creates a clearer framework for coordinating changes across independent development teams. As Solana continues to operate with multiple validator clients, the shared version number is intended to simplify tracking of network rules over time.
The announcement took place amid ongoing activity across Solana’s decentralized finance applications and stablecoin markets. The naming and versioning update itself does not alter transaction fees, throughput, or other performance characteristics beyond what prior upgrades have already delivered.









