Solana 1.0 is the Solana Foundation’s name for the network’s move from “mainnet beta” to plain “mainnet.” The Foundation announced it on November 16, 2026, together with a shared protocol version for the whole network that sits apart from the version numbers of the software validators run. It says it coordinated the change with the Anza and Firedancer teams.
For people who hold SOL or use Solana apps, the Foundation’s announcement is direct: “For users, this is the same network, nothing changes.” Accounts, assets, applications and transaction history stay as they are.
Why the beta label is going
Solana has run as a live production network since its genesis, but the mainnet-beta name never changed to reflect that, the Foundation says. It points to two developments as the reason to drop it now:
- Alpenglow, a change to how validators reach agreement, is active on mainnet and brings finality, the point at which a transaction counts as settled, to about 150 milliseconds.
- Firedancer is a second validator client built independently of Agave. The Foundation says independent implementations reduce reliance on a single codebase and limit the damage a bug in one client can do.
One protocol, two clients
The protocol is the set of rules every validator follows; a client is the software that implements those rules. Agave and Firedancer have separate codebases, release schedules and version numbers, so one client’s release number no longer works as shorthand for the network.
Under Solana 1.0, different client releases can support the same protocol version while keeping their own numbering. The Foundation adds a caution for operators: “Announcing a protocol version does not activate every associated improvement at once.” Software releases and feature activations keep their own rollout requirements and timelines. The announcement does not give the numbering scheme or dates for the next protocol versions.
Who needs to do what
| Group | What the Foundation asks |
|---|---|
| Users | Nothing |
| App developers | Review changes to the APIs, SDKs and infrastructure they use; the Solana Changelog tracks them weekly |
| Validator and RPC operators | Check which client releases support each protocol rollout and follow the Agave or Firedancer upgrade docs |
| Documentation and tooling teams | Update network references as the new name rolls out |
Explorers, websites and documentation will switch to the new name gradually, and the Solana Upgrades page lists upcoming features, compatible client releases and activation status.
For the basics of how validators agree on a shared ledger, see what a blockchain is.





