> ## Content Index
> Fetch the complete content index at: https://btcpeers.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Solana Drops the Beta Label. What Does 1.0 Change?
- URL: https://btcpeers.com/solana-mainnet-beta-1-0-protocol-version-wallets-validators/
- Published: 2026-11-16T14:37:05.000Z
- Updated: 2026-11-16T14:37:05.000Z
- Description: Solana now has a shared protocol version across validator clients. Wallets and balances carry on as before.
- Author: John Williams
- Tags: News

Solana dropped its “mainnet beta” label on Monday, and crypto commentator Ryan (@Ryanhlx) pointed out that the new 1.0 number gives validators a shared version for the rules they follow, even when they run different software. He also highlighted the immediate implication for anyone holding SOL or using an app. Their accounts and balances carry on as before.

The [Solana Foundation announced the change](https://solana.com/news/solana-1-0-dropping-beta-and-what-comes-next?ref=btcpeers.com) on November 16 and said it had coordinated with the teams behind Agave and Firedancer. Solana has processed transactions under the beta label since its launch. Existing apps, assets and transaction history stay on the same network as documentation, explorers and other tools adopt the shorter “mainnet” name.

> solana is moving from mainnet beta to version 1.0  
>  
> here is what this means and what comes next:   
>  
> \- alpenglow: faster transaction finality through a new consensus system  
>  
> \- firedancer: a second independent validator client for the network  
>  
> \- protocol versioning: a shared standard… [https://t.co/Q9gcopIiI0](https://t.co/Q9gcopIiI0?ref=btcpeers.com) [pic.twitter.com/ZeQJwvQVtR](https://t.co/ZeQJwvQVtR?ref=btcpeers.com)
> 
> — Ryan (@Ryanhlx) [November 16, 2026](https://x.com/Ryanhlx/status/2122310449924366749?ref%5Fsrc=twsrc%5Etfw&ref=btcpeers.com)

## One version for the network’s rules

Agave and Firedancer are separate implementations of the rules validators follow to agree on transactions. Each team can ship software on its own schedule, with its own release numbers. Two different client releases can therefore support the same protocol version. For validator and RPC operators, the practical question is which release of the software they run supports the protocol version the network is rolling out.

Ryan also cited Firedancer and Alpenglow in his rundown. The Foundation pointed to the deployment of the independently developed Firedancer client and the earlier activation of Alpenglow, which changed how validators reach agreement, as milestones behind the decision to retire the beta label. Future improvements still have their own activation schedules.

App developers can use the [Solana upgrade tracker](https://solana.com/upgrades?ref=btcpeers.com) to see when a feature goes live and check whether it affects the tools their app uses. For wallet users, the first visible change may simply be the label on a block explorer.