Solana 1.0 vs. Mainnet Beta: A Protocol Label, Not a New SOL Token

In a report published on November 17, 2026 (UTC+8), the Solana Foundation said it had retired the network’s “mainnet beta” label on Monday, November 16, more than six years after its March 16, 2020 launch. Solana 1.0 is a shared version number for the network’s protocol rules, not a new token or a speed upgrade arriving with the name change.

For SOL holders, the distinction is straightforward: the Foundation said SOL, accounts, other assets, applications and transaction history remain unchanged. Users do not need to swap tokens, move wallets or install software to continue using the network.

For validator operators, 1.0 provides a common reference point across two separately developed clients: Anza’s Agave and Jump Crypto’s Firedancer. Their software releases can have different version numbers while supporting the same protocol version. The Foundation said it coordinated the change with both development teams, but warned that naming a protocol version does not activate every associated improvement. Operators still need to check their client’s support and follow the relevant upgrade instructions. The announcement did not describe a new voting system or a change to Solana’s governance process.

The Foundation pointed to earlier engineering work, including Alpenglow, which went live on October 21 and targets transaction finality of roughly 150 milliseconds, compared with about 12.8 seconds under the previous system. That target belongs to the October upgrade, not to the 1.0 label. Firedancer reached mainnet in 2025, offering a separately developed alternative to Agave. Multiple clients can reduce reliance on one codebase, but the protection depends in part on their adoption and does not guarantee uptime: Solana experienced an outage of nearly five hours in February 2024 and one lasting almost 19 hours a year earlier.

At the time of the report, Solana’s upgrade tracker listed Agave 4.4 as planned for November and Agave 4.5 for December, each with separate release and activation requirements. The Foundation said documentation and block explorers would gradually adopt the new mainnet name.