NewsCryptoSolana Retires 'Mainnet Beta' Label After Six Years, Introduces Solana 1.0

Solana Retires 'Mainnet Beta' Label After Six Years, Introduces Solana 1.0

Author: Decrypt·

Key Takeaways

  • •The Solana Foundation announced on Monday the retirement of the 'mainnet beta' label in favor of Solana 1.0, a shared protocol version for the network's underlying rules, more than six years after the March 2020 launch.
  • •Solana 1.0 is intended to help teams running the Agave and Firedancer validator clients coordinate software updates, allowing independent releases to support the same protocol version without sharing software version numbers.
  • •The change activates no new features, does not boost transaction speed, and does not alter user balances, so holders need not swap tokens, move wallets, or install anything.
  • •The timing follows the Alpenglow consensus upgrade that went live on October 21 with targeted finality of roughly 150 milliseconds, down from about 12.8 seconds, and Firedancer reaching mainnet in 2025 as a second independent client.
  • •The network's upgrade tracker lists Agave 4.4 for November and Agave 4.5 for December as the next compatibility checkpoints, while documentation and block explorers gradually adopt the new mainnet name.
Solana Retires 'Mainnet Beta' Label After Six Years, Introduces Solana 1.0

Solana has officially dropped its "mainnet beta" designation, retiring the label it has carried since March 2020 in favor of Solana 1.0, a shared protocol version for the network's underlying rules. The Solana Foundation announced the change on Monday, more than six years after the network launched a blockchain that has been settling real transactions throughout that period.

The change is primarily about how developers and validator operators coordinate software updates, helping teams running Agave and Firedancer track compatibility across releases. It does not activate new features, boost transaction speed, or deliver any other meaningful improvement over what users already have, and it does not alter user balances.

From experimental label to versioned protocol

Solana launched its mainnet beta on March 16, 2020, and kept the experimental-sounding name even as users traded tokens, built applications, and moved assets across the chain. Nothing happens to those holdings now. "Your SOL, accounts, assets, applications, and transaction history remain the same," the Foundation said. Users do not need to swap tokens, move wallets, or install anything to keep using the network.

Why a shared version number matters

Solana has two major validator clients: Agave, developed by Anza, and Firedancer, built independently by Jump Crypto. Each has its own code, release schedule, and version numbers, which can make it harder to tell whether different software releases support the same network features.

Solana 1.0 creates a common reference point for the protocol itself. An Agave release and a Firedancer release can support the same protocol version without sharing a software version number. The approach follows a convention familiar from broader software engineering, where a shared specification carries the version number and independent implementations adopt it on their own schedules.

That distinction matters as the network relies on more than one software implementation. A bug in one client need not affect every validator, although software diversity alone cannot guarantee the network will stay online.

"Announcing a protocol version does not activate every associated improvement at once," the Foundation warned. Operators still need to check whether their particular software supports a planned upgrade and follow its activation instructions.

The Foundation said it coordinated the change with Anza and the Firedancer team. Its announcement does not describe a new voting system or a change in who governs Solana; the network's governance process for proposals remains separate.

Why retire beta now?

The Foundation credits engineering work that preceded Monday's announcement, particularly the Alpenglow consensus upgrade and Firedancer. Alpenglow went live on October 21, replacing the system validators had used to reach agreement since launch. It targets transaction finality of roughly 150 milliseconds, compared with about 12.8 seconds previously. Finality is the point at which a transaction is considered settled; that improvement came from the October upgrade, not from calling the network 1.0.

Firedancer also reached mainnet in 2025, giving validators a separately developed alternative to Agave. That reduces dependence on a single codebase, though the extent of the protection depends on how widely different clients are actually used.

Solana has reasons to be careful with promises of reliability. The network went offline for nearly five hours in February 2024, following an outage that lasted almost 19 hours a year earlier.

According to the Foundation, documentation and block explorers will gradually adopt the new mainnet name, so references to the beta label may linger while services update at their own pace. Its upgrade tracker still lists Agave 4.4 as planned for November and Agave 4.5 for December, each with its own release and activation requirements. For validator operators, those releases are the next checkpoints for tracking compatibility across clients — the kind of coordination the new protocol version is designed to simplify.