- Solana Foundation has announced that the Solana network is moving from mainnet-beta to full mainnet, dropping the “beta” label used since launch.
- The foundation said Solana 1.0 introduces shared protocol versioning across validator clients without changing users’ assets, accounts or transaction histories.
- The transition follows the activation of the Alpenglow upgrade and continued rollout of the independent Firedancer validator client.
Solana Foundation has announced that the Solana network is transitioning from mainnet-beta to full mainnet, removing the “beta” designation it has used since launch. The change introduces a unified protocol versioning system while leaving the network’s operation and users’ holdings unchanged.
The transition to Solana 1.0 was coordinated by Solana Foundation, the Anza team and Firedancer, according to the announcement. Solana coins, accounts, assets, applications and transaction histories remain unchanged, and users do not need to take any action.
The team said the network has effectively operated as production infrastructure since its launch, but that the mainnet-beta label no longer reflected its status.
Shared protocol versioning
Solana 1.0 separates the network’s protocol version from the version numbers of individual validator clients. Agave and Firedancer previously maintained their own version numbers and release schedules.
Under the shared system, developers and infrastructure operators can determine which protocol updates each client supports without relying on the numbering used by a particular client.
Solana said the announcement of a protocol version does not mean that all associated features will be activated simultaneously. Software releases and network upgrades will continue to follow separate schedules and requirements.
Technical upgrades support transition
The team identified the activation of the Alpenglow upgrade on mainnet as one of the key prerequisites for the change. Alpenglow changes how validators reach consensus and, according to the team, provides transaction finality in about 150 milliseconds.
Solana is also rolling out Firedancer, an independent validator client developed separately from Agave. The use of different codebases reduces the network’s dependence on a single software implementation and limits the potential effect of bugs in any one client.
Although users do not need to take action, the statement advised application developers to monitor changes to application programming interfaces, software development kits and infrastructure. Validator and remote procedure call operators should verify that their clients are compatible with specific protocol upgrades.
In a separate development previously reported by Incrypted, DTCC plans to launch tokenized securities on the Solana network in 2027.
Source: Incrypted
