protocol
Solana Foundation drops 'mainnet beta' label, adopts protocol version 1.0
After six years on 'mainnet beta,' the Solana Foundation introduced a shared protocol version — Solana 1.0 — separate from validator client versions. No action required from users.
The Solana Foundation retired the "mainnet beta" label the network has carried since March 2020 and introduced Solana 1.0 as a shared protocol version, separate from the software version numbers of individual validator clients. The announcement was published on Monday on the Solana blog and first reported by The Block.
What changed
The foundation describes Solana 1.0 as a nomenclature change on top of protocol milestones already shipped, not a new release in itself. Users do not need to do anything: SOL holdings, transaction histories, and accounts are unaffected. Validator operators and developers are told to keep tracking individual client release notes, because assigning a protocol version does not automatically activate every network improvement attached to it.
Validator clients continue to maintain their own version numbers. The two mainnet clients are Anza's Agave and Jump Crypto's Firedancer, which went live on mainnet in December 2025. The announcement does not peg the 1.0 protocol version to a specific Agave or Firedancer release.
Why now
Dropping the beta tag has been a recurring debate inside Solana. Co-founder Anatoly Yakovenko has argued the label should go once Firedancer was live on mainnet, citing the removal of a single-client point of failure. Firedancer activation last December satisfied that condition.
The more recent trigger is Alpenglow, the consensus upgrade that replaced TowerBFT and brought block finality to roughly 150 ms, down from about 12.8 s. Alpenglow went live on mainnet in October 2026 — the final major protocol change the foundation now cites as grounds for considering the network out of beta.
What 1.0 does not mean
- It is not a hard fork or coordinated upgrade on top of existing client releases.
- It is not a commitment to feature freeze — the foundation explicitly notes future improvements will keep landing through client releases on a per-feature cadence.
- It is not tied to a specific Firedancer or Agave release number in the announcement.
Readers who treat Solana 1.0 as a silent gate on features should check the Agave and Firedancer release notes before assuming any particular activation is live on their validator.
What to watch
- Whether validator operators standardize on Agave or Firedancer client versions as "the" 1.0 build. Client diversity was the original motivation for dropping beta; it is also the operational variable that will matter most in the next outage.
- The next protocol-level items on the roadmap. The foundation's post flags continued client releases but does not name specific EIP-equivalent items as the next milestones after Alpenglow.
- Downstream vendor copy. Exchanges, custodians, and index providers that still describe Solana as "mainnet beta" in their risk disclosures now have to decide whether to update that language.
Context
Solana launched mainnet beta on March 16, 2020. The beta tag outlasted at least three multi-hour network halts (2021–2023), the Firedancer rollout (December 2025), and Alpenglow (October 2026). For most of that period the foundation's position was that dropping the tag required a second production-ready validator client, which Firedancer provided. Monday's announcement closes the loop on an argument that has run inside the ecosystem for most of the chain's existence.
The move is nomenclature, not consensus. What it changes is how the network is described — to institutional counterparties, to regulators writing custody and risk frameworks, and to anyone still citing "beta" as a reason not to integrate. The protocol a 1.0 label now refers to is the same one Agave and Firedancer were already running on Monday morning.