Market cap $2.19 T −3.65 % over 24 hours24h volume $73.68 BBTC dominance 58.1 %ETH 10.0 %Fear & Greed 10 Extreme fearCoins 21,490

Solana drops the “beta” label after six years, but Solana 1.0 is a name and a version number, not an upgrade

Solana 1.0 retires the mainnet beta label and adds a protocol version shared by Agave and Firedancer. No feature is activated and users do nothing.

8 min read

Abstract chain links and stacked blocks beside a plain flag and a document
Table of contents
  1. What Solana 1.0 changes, and what it leaves alone
  2. Why the Foundation says the label had become wrong
  3. The last network halt dates from February 2024
  4. The old name is still in the plumbing
  5. Breakpoint: a crowded programme and a modest price move
    1. SOL gained about 7% over the conference and is still down on the week
  6. What the Foundation says the version number is for
  7. What to watch after the rename

Solana is no longer called a beta. In a post dated Monday 16 November 2026, published during its Breakpoint conference in London, the Solana Foundation said the network had moved from “mainnet beta” to plain “mainnet” under the name Solana 1.0, retiring a label the chain had carried since its launch in 2020. The same post says just as plainly what the change is not: for users, “this is the same network, nothing changes”.

The Foundation’s announcement describes two things. The first is a rename. The second is a version number for the protocol itself, shared by the different validator programs that run it, mainly Agave and Firedancer. No feature was switched on by the announcement, no software called “1.0” was released, and nobody who owns SOL, runs an app or holds a token on Solana has anything to do.

The rollout was coordinated, the post says, with Anza, the company that maintains Agave, and with the Firedancer team. The text sets out no test the network had to pass and gives no date for a next protocol version.

What Solana 1.0 changes, and what it leaves alone

The “1.0” belongs to the protocol, the set of rules every validator must follow, and not to a client, the program that implements those rules. With two independent programs now running the network, the Foundation argues, one client’s release number can no longer stand “as shorthand for the entire network”.

Agave and Firedancer, the post says, “have separate codebases, release schedules, and version numbers”. A protocol version sits above both. Different releases of each client can support the same protocol version while keeping their own numbering, which is why Agave is on its 4.x series and stays there. Anza put it in one line on X on 16 November, as relayed by the news site Solana Compass: “Solana 1.0 is the protocol version, shared across clients. Agave keeps its own versioning as is.”

The number is a reference point and not a release. “Announcing a protocol version does not activate every associated improvement at once,” the post says. Software releases and feature activations keep their own schedules, listed on the Solana upgrades page.

What the post asks depends on who is reading it:

  • Holders and users of apps do nothing. Balances, accounts, tokens, applications and transaction history are untouched.
  • Application developers are told to keep following the weekly Solana Changelog for changes to the APIs and SDKs they use.
  • Validator and RPC operators should check which Agave or Firedancer release supports each protocol rollout, and follow the activation instructions of their client.
  • Documentation and tooling teams are asked to update the network’s name as the new wording spreads.

Nothing in the post touches staking, fees, token supply or governance.

Why the Foundation says the label had become wrong

The argument is that “beta” described a status the network left long ago. Solana “has been a live production network since genesis”, the post says, under a label “that never evolved to signal its production status”. It names two milestones as the reason to act now.

One is Alpenglow, the new consensus design, which went live on mainnet on 21 October 2026 according to Solana Compass. It changes how validators agree on blocks and brings finality, the moment a transaction is treated as settled, to about 150 milliseconds according to the Foundation. Our guide to proof of history, Tower BFT and Alpenglow explains what was replaced.

The other is Firedancer, a validator client built by Jump Crypto independently of Agave, which Solana Compass dates to December 2025 on mainnet. When every validator runs the same code, one bug can stop them all. With two codebases, a bug in one should leave the other running. The Foundation says independent implementations “limit the impact of bugs affecting one client”.

The network has also got faster this year. The upgrades page lists Agave 4.2, shipped in August 2026, as cutting slot times from 400 to 200 milliseconds and raising the maximum transaction size from 1,232 to 4,096 bytes, both marked live on mainnet. A 90% cut in storage rent, phased over five steps, is marked partially activated.

Abstract lightning bolt above connected nodes, a turning gear and a server rack
The Foundation cites Alpenglow's faster finality and a second validator client, Firedancer, as the reasons to drop the label now.

The last network halt dates from February 2024

The beta label was not decorative in the early years. Solana stopped producing or finalizing blocks several times between 2021 and 2024, and each time validators had to agree off-chain on a point to restart from. The Foundation’s post does not mention those episodes.

The most recent one is documented in a report written by Anza. On 6 February 2024, block finalization halted at 09:53 UTC. Engineers matched the failure to a bug already found while investigating an outage on Devnet, the developer test network, for which a patch was about to ship. A patched release, v1.17.20, and restart instructions were published at about 12:34 UTC, and consensus resumed at 14:55 UTC, “approximately five hours” after the halt.

No network-wide halt has been recorded since, which makes two years and nine months on 18 November 2026. The post never presents that record as a condition for the new name.

The old name is still in the plumbing

Renaming a network is slower than announcing it. The string “mainnet-beta” is written into web addresses, command-line settings, wallet code and years of tutorials, and the Foundation’s post says only that documentation, websites and explorers “will progressively reflect the updated designation”. It says nothing about RPC addresses or the cluster name developers type.

On 18 November the two main sets of documentation disagree. The Foundation’s own clusters page lists the production network as “Mainnet”, with the public endpoint api.mainnet.solana.com, a gap Solana Compass pointed out on 16 November. Two days later, Anza’s documentation for Agave still reads “Mainnet Beta”, with api.mainnet-beta.solana.com as the RPC address and “mainnet-beta” as the name of the metrics database.

Both addresses work. Queried on 18 November at about 11:50 UTC, the new and the old public endpoints each answered and reported the same software version, 4.4.0, and the same epoch. An app that keeps the old address is not broken today. Whether that address will be kept for good, redirected or retired has not been said, and that is the practical question for anyone who maintains code with “mainnet-beta” in it.

Breakpoint: a crowded programme and a modest price move

The rename was one announcement among many. Cointelegraph describes Breakpoint as a pre-conference event on Sunday 15 November followed by the main programme on Monday and Tuesday. The larger items have their own articles here: Zelle’s $1.25 million ZelleUSD demonstration and its limits, DTCC’s plan to connect its tokenization service to Solana in 2027, and what is known about the Foundation’s stake in CoinGecko.

One item concerns European readers more than the rest. Project Harmonia, an initiative led by Allfunds Blockchain and the Solana Foundation, named its first group of asset managers during the conference, Cointelegraph reports. Its aim is to distribute funds tokenized on Solana through the institutional network of Allfunds, a European fund distribution platform.

SOL gained about 7% over the conference and is still down on the week

Cointelegraph reported on 18 November, using CoinGecko data, that SOL reached $75.12 on Tuesday 17 November, up 6.95% from $70.24 at the end of Saturday 14 November. Over the same span it puts bitcoin at +1.2% and ether at +3.1%.

That is a three-day bounce inside a poor week. SOL traded near $74.50 around 11:30 UTC on 18 November, up 1.6% over 24 hours and down 10.7% over seven days. Bitcoin was near $64,170 at the same time, down 12.8% on the week, and the Fear and Greed index stood at 11, in “extreme fear”.

Nothing ties the move to the rename. The same three days carried the Zelle demonstration and the fund announcement, and bitcoin and ether rose as well.

Abstract megaphone beside candlesticks and a rising line over a city skyline
SOL rose 6.95% between 14 and 17 November, according to Cointelegraph, and was still down 10.7% over seven days on 18 November.

What the Foundation says the version number is for

The post’s own justification is modest. Solana 1.0, it says, “recognizes the progress on network performance, resilience, and developer experience”, and the rename itself is a “simplification of nomenclature”.

The practical benefit it claims is for developers and infrastructure operators: protocol versioning “makes it easier to track network changes and understand which client releases support them”. An operator on Firedancer and another on Agave can then name the rules their nodes follow with one number, without quoting either team’s release.

The post gives no figure for how the network is split between the two clients. Solana Compass counted 699 validators voting and producing blocks in epoch 1088, which began on 16 November.

What to watch after the rename

The post does not say what would make a 1.1 or a 2.0, or who decides. The nearer dates are on the client calendar. The upgrades page lists Agave 4.4 as expected in November 2026, with a new program format required for fresh deployments and nested program calls going from four levels to eight, and Agave 4.5 in December, raising the accounts a transaction can name from 64 to 96. All three changes are marked in development.

Then there is the plumbing: whether Anza’s documentation, the command-line tools and the big explorers drop “mainnet-beta”, and what happens to the old RPC address. Until the Foundation or Anza says otherwise, both names point to the same network.

Sources

  1. Solana Foundation: Solana 1.0: Dropping -beta, and what comes next (16 November 2026) solana.com
  2. Solana Compass: Solana drops the mainnet-beta label and introduces Solana 1.0 (16 November 2026) solanacompass.com
  3. Solana Foundation: Solana Upgrades page (read 18 November 2026) solana.com
  4. Anza documentation for Agave: Available Solana Clusters (read 18 November 2026) docs.anza.xyz
  5. Anza: 02-06-24 Solana Mainnet Beta Outage Report (9 February 2024) solana.com
  6. Cointelegraph: Solana outperforms Bitcoin and Ether during Breakpoint (18 November 2026) cointelegraph.com

Leave a Reply

Your email address will not be published. Required fields are marked *