Solana (Photo: Shutterstock)

Solana will remove “beta” from the “Mainnet Beta” name it has used for about 7 years and introduce protocol version 1.0 to manage common network rules.

On Nov. 17 (local time), blockchain outlet Coinpost reported that the Solana Foundation will change the network name from Mainnet Beta to Mainnet starting Nov. 16 and introduce a system to manage protocol and validator software versions separately.

The move focuses on refining technical standards for developers, operators and validators. The foundation explained that Solana had been a live-use network that has processed transactions, applications and assets since its early operation, but the name still included “beta”. It has kept the label for about 6 years and 8 months since launch in March 2020.

The foundation pointed to recent technical changes as the backdrop for the name overhaul. It explained that after Alpenglow, which revamps the consensus structure, was activated on mainnet, transaction finality time was reduced to about 150 milliseconds.

It also cited diversification of validator software as a key change. With the introduction of Firedancer, developed separately from existing Agave, software options increased and reliance on a single codebase declined. The foundation decided to assign a separate version to the protocol, the common rules validators must follow, rather than referring to the entire network by a specific client version.

Under the new system, Agave and Firedancer will each maintain independent code, release schedules and version numbers. Network-wide changes will be managed through a common protocol version. The foundation said this will help developers and operators more easily identify network changes and the corresponding client releases.

There will be no changes that general users will notice. As the existing network will remain in place, there will be no changes to SOL, accounts, assets, applications or transaction history. Users also do not need to take any separate action. Software releases and network feature activations will proceed according to their respective requirements and schedules.

Developers and operators will still need to check guidance for each release. In particular, validators and RPC operators will need to separately review the required client releases in line with the introduction of each protocol version. It explained that even with a common protocol version, client-by-client update management will still be necessary.

The name change will be reflected sequentially in documents, websites and explorers. The overhaul aims to clarify operating standards by separating versioning for common network rules and the software that implements them, without changing user assets or transaction history.

Keyword

#Solana #Solana Foundation #Alpenglow #Agave #Firedancer
Copyright © DigitalToday. All rights reserved. Unauthorized reproduction and redistribution are prohibited.