Solana adopts 1.0 protocol versioning as network drops mainnet-beta label
After operating for years under a mainnet-beta designation, Solana is now renaming its live network as mainnet and introducing a shared protocol version separate from validator software releases. The change leaves user assets, accounts, applications and transaction history untouched, while giving developers and infrastructure operators a clearer way to track network upgrades across multiple clients.
Highlights
- Solana transitions from 'mainnet beta' to 'mainnet' with protocol version 1.0, establishing a unified protocol versioning separate from client software releases.
- The protocol versioning aims to help developers and operators track network evolution, especially as Agave and Firedancer maintain independent codebases and release schedules.
- Recent Alpenglow mainnet activation reduced transaction finality to 150 milliseconds, while Firedancer’s deployment increases resilience by decentralizing validator clients.
Protocol shift and rollout coordination
As reported by Solana, citing Solana News, Solana 1.0 marks the network’s transition from “mainnet beta” to “mainnet” and establishes a common protocol version that is independent of the software version numbers used by validator clients such as Agave and Firedancer.The Solana Foundation coordinates the rollout with the Anza and Firedancer teams. The change reflects what the network describes as technical progress rather than a migration to a new chain, meaning users keep the same SOL balances, accounts, assets, applications and transaction records.
Solana says the new structure becomes more relevant as its client ecosystem expands. Agave and Firedancer maintain separate codebases, release schedules and version numbers, so a shared protocol version is intended to give developers and operators a common reference point for the network’s evolution without tying that shorthand to a single client release.
Performance gains and ecosystem impact
A key factor behind the naming change is recent work on performance and resilience. Solana points to Alpenglow’s mainnet activation, which changes how validators reach agreement and enables faster transaction finality of about 150 milliseconds, as well as the deployment of Firedancer as an independently developed validator client intended to reduce reliance on one codebase and limit the effect of client-specific bugs.For developers and infrastructure operators, the foundation says protocol versioning should make it easier to identify which client releases support each rollout. It also notes that announcing a protocol version does not switch on every related improvement at once, because software releases and network feature activations continue to follow their own upgrade requirements and timelines.
Users are not required to take any action. Application developers are advised to review changes affecting APIs, SDKs and infrastructure, while validator and RPC operators are expected to check release compatibility and follow upgrade instructions for Agave or Firedancer; documentation and tooling teams are also expected to update network references as the revised naming is adopted across websites, explorers and other ecosystem services.
We recently wrote about the Jupiter Vaults beta launch on Solana as Jupiter expanded its DeFi offerings.