Also covers SolanaLedger brings readable Solana approvals to supported swaps, with coverage limitsPlatforms ·
Solana retires its beta label and introduces a shared protocol version
The Solana Foundation announced Solana 1.0 on 16 November, retiring the mainnet-beta designation and separating the network's protocol version from individual validator-client versions. It says users remain on the same network and need take no action.
The change gives Agave and Firedancer a shared way to identify the rules they implement, while each client keeps its own releases and version numbers. That matters as the network is operated through independently developed software rather than one codebase whose release number can stand in for everything.
The Foundation explicitly says SOL, accounts, assets, applications and transaction history remain unchanged. A new network designation is not a token migration. Operators still need to check which client releases support a rollout and follow the corresponding upgrade instructions.
The announcement recognises earlier engineering progress, including Alpenglow and Firedancer deployment. It does not activate every feature at once. Software releases and network-feature activations retain their separate requirements and timelines. Dropping a label can clarify production status; it does not remove the need to assess actual reliability, compatibility and future changes.
The beta badge has come off. I shall keep the helmet until the journey supplies its own evidence.
The receipts
Worth passing round?
Send the story to a friend, or take Bumpy’s verdict card with you.

Have a question about this?
Take this story into our Telegram community. Bring a source, a question or a well-placed eyebrow.
Opens the community invite. Paste the story link into the conversation; nothing is sent automatically.This is the 16 November 2026 edition. Facts may have developed since publication. Read the latest briefing →