Solana 1.0 marks the network’s graduation from “mainnet beta” to “mainnet,” retiring the beta designation it has carried since launch. It recognizes technical progress and gives the network a shared protocol version, independent of the software versions used by individual validator clients such as Agave and Firedancer.
The Solana Foundation coordinated the rollout with the Anza and Firedancer teams.
For users, this is the same network, nothing changes. Your SOL, accounts, assets, applications, and transaction history remain the same.
For developers and infrastructure operators, protocol versioning makes it easier to track network changes and understand which client releases support them.
Why move beyond beta now?
Solana has been a live production network since genesis, supporting transactions, applications, and assets under a mainnet-beta label that never evolved to signal its production status.
A recent major milestone, Alpenglow’s mainnet activation, changes how validators reach agreement and enables faster transaction finality (~150ms). Finality is the point at which the network considers a transaction settled.
The deployment of Firedancer, a validator client developed independently from Agave, adds greater diversity to the software running the network. Independent implementations reduce reliance on a single codebase, limit the impact of bugs affecting one client, and strengthen network resilience.
Solana 1.0 recognizes the progress on network performance, resilience, and developer experience. That progress continues with this simplification of nomenclature.
One protocol, multiple clients
The protocol defines the shared rules validators follow. A client implements those rules in software. As Solana’s client ecosystem grows, the distinction between the network’s protocol and the software implementing it becomes more important.
Agave and Firedancer have separate codebases, release schedules, and version numbers. A shared protocol version lets everyone refer to Solana’s evolution without using one client’s release number as shorthand for the entire network.
Different client releases can therefore support the same protocol version while retaining their own version numbers. Operators should check which releases support each protocol rollout. Announcing a protocol version does not activate every associated improvement at once. Software releases and network feature activations will continue to have their own rollout requirements and timelines.
What should users, developers, and operators do?
Users don’t need to do anything. Improvements to their experience come through underlying upgrades and applications that adopt them.
Developers and operators should continue following release-specific guidance:
- Application developers: Review changes affecting the APIs, SDKs, and infrastructure your applications use. The Solana Changelog tracks these updates weekly.
- Validator and RPC operators: Check which client releases support each protocol rollout, and follow the relevant upgrade and activation instructions in the Agave documentation or Firedancer documentation.
- Documentation and tooling teams: Update network references as the new naming rolls out.
Documentation, websites, explorers, and other ecosystem surfaces will progressively reflect the updated designation.
For upcoming features, compatible client releases, activation status, and technical guidance, visit Solana Upgrades.












