News analysis ·

Solana 1.0 explained: what a protocol version changes

Solana dropped its mainnet beta label for Solana 1.0. We explain how one protocol version lets Agave and Firedancer coordinate upgrades, and what stays the same.

Black-and-white photo of two steam locomotives standing side by side on parallel tracks at a railway depot, each with its own number plate.
Photo: Ben Brooksbank / Wikimedia Commons, CC BY-SA 2.0 (cropped)

The Solana Foundation has stopped calling its network a beta and moved to Solana 1.0, a single version number for the rules of the network, Decrypt reported. Nothing about balances or speed changes with the new name. This article looks at what a shared protocol version actually does for the software that runs Solana, and where its limits are.

The change in one paragraph

On Monday the Foundation dropped the beta tag that Solana had carried since its mainnet beta began on March 16, 2020. In its place comes Solana 1.0, a number that describes the network rules themselves rather than any one piece of software. According to Decrypt, the move is mostly about how developers and node operators coordinate releases. It is not a performance upgrade, and users do not need to do anything. The Foundation said SOL, accounts, apps and transaction history stay as they are, with no token swap, wallet move or install required.

What is Solana, and why does it need a protocol version?

Solana is a layer 1 blockchain: a base network where validators, the computers that check and record transactions, agree on one shared history. Validators do not all run the same program. Solana has two main validator clients. Agave is built by Anza. Firedancer comes from a separate team at Jump Crypto. The two clients ship on different schedules, from different codebases, under different version numbers.

That is where the trouble started. If one client is on one version and the other is on a very different number, it is hard to tell whether both handle the same network features. The 1.0 label gives everyone a common reference point.

Under the hood: software version versus protocol version

The key idea is to separate two numbers that used to blur together. A software version says which build of a program you are running. A protocol version says which set of rules that build follows. Other parts of computing already work this way: many different programs can speak the same network standard without sharing a version number with each other.

Before Solana 1.0, the moving parts looked like this:

  • Agave releases, numbered by Anza on its own schedule.
  • Firedancer releases, numbered by its team on a different schedule.
  • No single label to say both builds follow the same network rules.
  • After Solana 1.0: an Agave build and a Firedancer build can both target the same protocol version while keeping different software numbers.

This matters most at upgrade time. A protocol version is a label for a rule set, not a switch. The Foundation was explicit on this point: "Announcing a protocol version does not activate every associated improvement at once." Each change still has its own activation step, and operators must check that their particular client supports it before it goes live. In plain terms, the version number tells you what the destination is; it does not move anyone there.

What Solana 1.0 does not change

It is easy to credit the new label with recent gains, so it helps to be precise. The Alpenglow upgrade, activated on October 21, replaced the consensus system validators had used since launch. Alpenglow targets finality, the point at which a transaction counts as settled, of roughly 150 milliseconds; the old figure was about 12.8 seconds. Decrypt noted that this speed-up belongs to Alpenglow; the new version label added none of it.

No governance change was described either. According to the Foundation, Anza and the Firedancer team were part of the planning, and Decrypt reported that no new voting system or shift in who governs Solana was described.

Who is affected

Ordinary users and app builders see no direct change. Validator operators are the main audience. They now have one number to check when deciding whether their client is ready for a planned rule change, regardless of which client they run.

Client diversity is the wider reason this matters. Firedancer reached mainnet in 2025, giving validators an alternative codebase to Agave. When several implementations run side by side, a flaw in one of them does not have to take down every validator. Decrypt cautioned that diversity alone cannot ensure the network stays up, and that the protection depends on how widely each client is actually used. Solana has a record that makes this relevant: the network was down for close to five hours in February 2024, after an outage of almost 19 hours a year earlier.

Status and next steps

The Foundation said documentation and block explorers will switch to the new mainnet name gradually. On its upgrade tracker, Agave 4.4 is still pencilled in for November, with Agave 4.5 slated for December. Each of those releases has its own release and activation requirements, which is exactly the kind of detail the shared protocol version is meant to make easier to follow across clients.

Sources

AI wrote this summary from the primary documents and reports cited above. It went live automatically after checks that figures match those sources and nothing is copied; there was no human review. It explains a protocol or rule change and is not investment advice.

← All posts