BLOCKCHAINUSA

Solana 1.0: Mainnet Beta Label Dropped. What Changes for Wallets, Developers and Validators

The Solana Foundation retired the mainnet-beta label on 16 November 2026 and introduced Solana 1.0 as a protocol version. Funds are unaffected.

Crypto Support Desk
Crypto Support Desk

Crypto Support & Research Desk

Published Nov 16, 2026
Updated Nov 16, 2026
7 min read
Referenced Assets:General Market
Share:

Quick answer: On 16 November 2026 the Solana Foundation dropped the "mainnet beta" label and introduced "Solana 1.0" as a shared protocol version. Nothing changes on-chain: balances, accounts, tokens and transaction history stay the same, and wallet users need to do nothing. Treat any "Solana 1.0 migration" or claim request as a scam.

What happened

The Solana Foundation published Solana 1.0: Dropping Beta and What Comes Next on Monday 16 November 2026. The post retires the "mainnet-beta" label the network has carried since its 2020 launch and introduces Solana 1.0 as a shared protocol version that describes the rules the network runs on. The Block reported the change the same morning.

The Foundation framed the change as recognition of progress rather than a technical cutover. It quoted: "Solana 1.0 recognizes the progress on network performance, resilience, and developer experience." The milestones it cites include:

  • Alpenglow consensus, live on mainnet since October 2026, which the Foundation says cut finality to about 150 milliseconds from roughly 12.8 seconds.
  • Firedancer, a second independent validator client, live on mainnet since December 2025, alongside Anza's Agave client.

What "protocol version 1.0" means

Until now, people often described Solana's state by client version numbers, such as an Agave release. The Foundation is separating two ideas:

  • Protocol version: the shared set of rules all validators follow. This is now "Solana 1.0".
  • Client versions: the software that implements those rules. Agave and Firedancer keep their own codebases, release schedules and version numbers. Several client releases can support the same protocol version.

The Foundation was clear that assigning a protocol version does not activate every improvement at once. Feature activations keep their own rollout requirements and timelines, which are still coordinated through client releases and feature gates.

What does not change

  • Your SOL balance, SPL tokens, NFTs and staking positions.
  • Your wallet address and private keys.
  • Transaction history and existing on-chain programs.
  • The network itself. There is no new chain and no snapshot.

Why the "beta" label mattered

For years, "mainnet beta" signalled that Solana's core software was still maturing. Dropping the label does not change how the chain works today, but it changes how the Foundation describes it: the network now has a named protocol version that client teams can target, and that future versions can increment when the rules change. For users, the practical meaning is simple. When you later see "Solana 1.x" or "2.0" in official notices, that will refer to changes in network rules, and those notices will explain whether any action is needed.

Who is affected

Wallet and exchange users

No action is needed. You do not need to move funds, swap tokens, update a seed phrase or "verify" your wallet. Over time your wallet or block explorer may start showing "Mainnet" instead of "Mainnet Beta". That is cosmetic. When it happens, just confirm you are on the main Solana network and not a test cluster such as devnet before signing anything.

Developers and RPC users

The Foundation says APIs, SDKs, explorers and wallets will "progressively reflect" the new naming but gave no dates. Until tooling changes are announced:

1. Search your code for "mainnet-beta". Note where you hard-code the cluster name or the api.mainnet-beta.solana.com endpoint, so you are ready if names change.

2. Don't rename anything yet. Neither the Foundation nor The Block said the public RPC endpoint or CLI cluster names are changing now. Changing them early could break your app.

3. Follow the weekly Solana changelog and the Solana upgrades page for concrete activation news.

4. Plan for sBPFv3. The upgrades page lists Agave 4.4 (planned for November 2026) as requiring sBPFv3 for new program deployments, and raising the cross-program invocation (CPI) nesting depth from 4 to 8.

5. Watch v1 transaction limits. Agave 4.5 (planned for December 2026) is listed as letting v1 transactions load 96 accounts instead of 64.

6. Durable nonces. The upgrades page lists durable-nonce deprecation as unscheduled, with roughly a six-month migration window once the replacement program is ready. If your app relies on durable nonces, start tracking this now.

Validator and RPC operators

Operators should keep following Agave and Firedancer release guidance and check which client releases support each feature rollout. The network's most recent emergency patch window shows why. According to a validator discussion summary from Chainflow, the Agave 4.4.1 patch deadline at the epoch 1079 boundary on 6 November passed without a halt, with about 1.5% of stake delinquent afterwards.

  • Confirm your node is producing blocks on the canonical fork, not just voting.
  • Keep monitoring and alerting tied to client release channels, not the protocol label.
  • Treat "Solana 1.0" as a documentation change unless a specific feature gate or release note says otherwise.

How to verify the situation yourself

1. Read the Foundation's post on solana.com/news. Type the address yourself.

2. Check your wallet balance in your usual wallet and on a reputable explorer. It should be unchanged.

3. Check the upgrades page for release and activation status rather than relying on social media posts.

4. Ignore anyone asking you to act. A genuine protocol rename never requires users to sign a transaction.

For examples of network changes that did require action, see our guides to the Hedera v0.79 mainnet upgrade, the Stellar Protocol 30 Bell vote and the Dash v24 hard fork. Node operators may also find our Bitcoin Core security disclosure guide useful as a model for patch checks.

What is still unconfirmed

  • RPC endpoint renaming. Whether api.mainnet-beta.solana.com will be renamed or deprecated, and when, has not been announced.
  • CLI and SDK cluster names. The Foundation said tooling will progressively reflect the change, without dates.
  • Exact activation epochs for Agave 4.4 and 4.5 features. The upgrades page lists months only.

Frequently asked questions

Do I need to do anything with my SOL because of Solana 1.0?

No. Solana 1.0 is a naming and protocol-versioning change. Balances, tokens, accounts and history are unchanged, and there is no swap or migration.

Is Solana 1.0 a hard fork?

No. The Solana Foundation said the protocol version label does not activate features by itself. Individual features still roll out through client releases and their own activation process.

Will the mainnet-beta RPC endpoint stop working?

No change has been announced. The Foundation said tools will progressively reflect the new naming but gave no dates, so keep using existing endpoints until an official deprecation notice appears.

What is the difference between Solana 1.0 and Agave or Firedancer versions?

Solana 1.0 is the protocol version, meaning the shared rules. Agave and Firedancer are client software with their own version numbers, and several client releases can support the same protocol version.

Someone sent me a link to claim a Solana 1.0 airdrop. Is it real?

No. The Solana Foundation announced no airdrop or claim. Do not connect your wallet or sign anything, and never share your seed phrase.

Conclusion

Solana 1.0 marks the end of the "mainnet beta" label, not a change to your funds. Wallet holders can ignore it apart from staying alert to scams that use the name. Developers should map where they depend on the "mainnet-beta" string and track Agave 4.4 and 4.5, while validators keep following client release guidance. When concrete endpoint or tooling changes are announced, they will come through official Solana channels with dates.

This article is for general information only and is not financial or technical advice. Blockchain Support USA is an independent publication and is not affiliated with the Solana Foundation, Anza, any exchange or any wallet provider. We are not customer support and will never ask for seed phrases, passwords, private keys or 2FA codes. Details are accurate as of 16 November 2026 and may change.

Regulatory & Financial Risk Disclosure

The opinions, research, and analysis expressed in this publication are solely for educational and informational purposes and do not constitute investment, financial, legal, or tax advice. Digital asset markets are speculative and volatile. Past performance does not indicate future results. Always perform independent due diligence.

About the Author

Crypto Support Desk
Crypto Support Desk

Crypto Support & Research Desk

Crypto Support Desk publishes practical, source-led guides to exchange, wallet, network and on-chain service changes. Information is checked against primary or reputable security sources and is not investment advice.

Source-led crypto support research