Technologie
Solana drops the ‘mainnet beta’ label and introduces a shared protocol version
Solana 1.0 describes the network’s rules independently of Agave and Firedancer releases. The foundation says users will not need to migrate.

The main network drops the beta label
The Solana Foundation announced on November 16, 2026, that the Solana main network was dropping the beta label. It also introduced Solana 1.0 as a shared protocol version. The main network has operated in production since launch. The change in name therefore does not mark the opening of a new blockchain. According to the foundation, users keep their SOL, other assets, accounts, applications, and transaction history. They do not need to transfer anything or change their addresses.
The foundation coordinated the change with the Anza and Firedancer teams. It linked the removal of the beta label to changes that have already taken place, including the mainnet activation of Alpenglow and the introduction of the Firedancer validator client. Alpenglow changes how validators agree on the state of the network. The foundation says it enables finality of around 150 milliseconds. That measure refers to when the network considers a transaction settled. It does not measure the full wait a user may experience in an application.
Agave and Firedancer keep their own version numbers
Validators use a shared set of rules to process transactions and agree on the outcome. Agave and Firedancer implement those rules in separate software, with their own code, release schedules, and version numbers. Until now, referring to a software version could make it sound as if it applied to the entire network. The shared protocol number provides a reference when one development affects several clients, even if their teams update them on different dates.
Two software releases with different numbers can therefore support the same protocol version. Conversely, announcing a shared version does not mean every feature associated with it will go live at the same time. The foundation says software releases and network feature activations keep their own requirements. To prepare for an upgrade, an operator still needs to check whether the release they run is compatible and whether the network feature has been activated.
Instructions depend on the role
For application developers, the foundation points to changes that affect the interfaces, software development kits, and services their products use. Validator and RPC operators, who relay application requests to the blockchain, need to consult the instructions for their software. Teams responsible for documentation and tools are encouraged to update their network references as the change rolls out.
Websites, explorers, and documentation across the ecosystem are expected to adopt the new name gradually. Users may therefore still see “mainnet beta” in an interface during the transition. Solana 1.0 now gives technical teams a shared reference for tracking changes to the protocol, while Agave and Firedancer release numbers remain useful for checking what their software supports.
