Solana Introduces Version 1.0, Retiring Its Longstanding…
Solana has retired the “mainnet beta” designation it has carried since launch. The Solana Foundation announced Solana 1.0 on November 16, giving the network a protocol version that stands apart from the software versions of validator clients such as Agave and Firedancer.For users, the change alters nothing, since the network remains the same. Developers and infrastructure operators gain a clearer way to track network changes and to see which client releases support them. The Solana Foundation coordinated the rollout with the Anza and Firedancer teams. It said SOL balances, accounts, assets, applications and transaction history all stay as they are.
Alpenglow and Firedancer Drive the Change
Solana has run as a live production network since genesis, yet its label never reflected that status. The Foundation says Solana 1.0 recognizes progress on performance, resilience and developer experience, and points to two recent milestones.The first is the mainnet activation of Alpenglow, which changes how validators reach agreement and enables finality of roughly 150 milliseconds. Finality is the point at which the network considers a transaction settled. The upgrade was set to cut finality from about 12.8 seconds when it was scheduled for October 21, and readiness trackers flagged 20.3% of stake as unprepared a day before the switch.The second is the deployment of Firedancer, a validator client built independently from Agave. The Foundation says independent implementations reduce reliance on a single codebase, limit the damage when a bug hits one client and strengthen network resilience. Its hybrid predecessor, Frankendancer, had run on mainnet since 2024 and reached roughly a fifth of staked SOL by early 2026.
Investor Takeaway
Solana 1.0 follows the Alpenglow upgrade and Firedancer deployment, marking progress in transaction finality, validator diversity and network resilience.
Next Steps for Developers and Operators
Agave and Firedancer keep separate codebases, release schedules and version numbers, so a shared protocol version lets the ecosystem describe Solana’s progress without using one client’s release number as shorthand. The Foundation cautions that announcing a version does not switch on every related improvement at once, because software releases and feature activations keep their own timelines.Users need to do nothing, since improvements reach them through underlying upgrades and the applications that adopt them. Application developers should review changes to the APIs, SDKs and infrastructure their products use, which the Solana Changelog tracks weekly. Validator and RPC operators should check which client releases support each protocol rollout and follow the Agave or Firedancer upgrade instructions. Documentation, websites and explorers will adopt the new designation progressively.The label change arrives while Alpenglow’s results are still being measured. The Solana Foundation’s dashboard showed observed finality of 202 milliseconds on day one, about 35% above the 150 millisecond target, with sustained performance still to be established. Upcoming features, compatible client releases and activation status are listed on the Solana Upgrades page. Solana approaches a key support zone as selling pressure builds, with the A/D Indicator highlighting roughly 701 SOL million in trading volume.Source: TradingView
Investor Takeaway
The new protocol version gives developers and operators a common way to track network upgrades, while users do not need to take any action.
