Deep Web3

SYSTEMS.
PEOPLE.
POSSIBILITIES.

Menu

Go beneath
the surface.

Solana 1.0 Is a Protocol Version, Not a New Network

As reported on November 17, 2026 (UTC+8), the Solana Foundation had retired the “mainnet beta” label more than six years after the network’s March 16, 2020 launch. The change gives Solana’s underlying protocol a shared version number; it does not itself deliver a speed upgrade or change users’ assets.

Why a shared version matters

Solana’s two major validator clients—Anza’s Agave and Jump Crypto’s independently developed Firedancer—have separate codebases, release schedules and software version numbers. Solana 1.0 provides a reference for the network rules they support: an Agave release and a Firedancer release can implement the same protocol version without having matching client version numbers.

That distinction may make upgrade compatibility clearer, but a protocol-version announcement does not activate every associated improvement. The Foundation said operators must still check whether their client supports a planned upgrade and follow its activation instructions. It said the change was coordinated with Anza and the Firedancer team; the announcement did not describe a new voting system or a change to Solana’s governance process.

What changed earlier—and what did not

The Foundation pointed to engineering work that preceded the naming change. Alpenglow went live on October 21, replacing the validator agreement system used since launch. It targets transaction finality—the point at which a transaction is considered settled—of roughly 150 milliseconds, versus about 12.8 seconds previously. That target belongs to the October upgrade, not to the adoption of the 1.0 label.

Firedancer reached mainnet in 2025, offering validators an alternative to Agave. Separate implementations can reduce dependence on one codebase, but the protection depends in part on how widely each client is used; software diversity alone does not guarantee uptime. Solana’s reliability record includes an outage of nearly five hours in February 2024 and another lasting almost 19 hours about a year earlier.

The Foundation said SOL, accounts, assets, applications and transaction histories remain unchanged. Users need not swap tokens, move wallets or install software because of the naming change. Documentation and block explorers were expected to adopt the new name gradually. At the time of the report, the upgrade tracker listed Agave 4.4 as planned for November 2026 and Agave 4.5 for December 2026, each with separate release and activation requirements.