Solana’s mainnet will no longer be called “mainnet beta” starting on the 16th. The official account @solana announced at 18:20 Taiwan time on November 16: “mainnet-beta → mainnet,” and simultaneously introduced Solana 1.0 as the protocol version number shared by the entire network.
The beta label has been in place since the mainnet launched on March 16, 2020—more than six years ago. The announcement came during the Breakpoint 2026 conference in London.
According to an announcement by the Solana Foundation, the rename was coordinated by the Foundation and the two development teams, Anza and Firedancer. For everyday users, it’s still the same network: SOL, accounts, assets, applications, and transaction history are all unaffected, and no action is required.
The old mainnet-beta alias will remain available, while command-line tools will point to mainnet
Developers will be the first to notice the change in their tools. In late October, the Agave client maintained by Anza merged a command-line tool change that replaced the connection alias mainnet-beta with mainnet and changed the default RPC URL to api.mainnet.solana.com.
The old alias has not been removed. Entering –url mainnet-beta will still connect, but a warning will appear once: “Solana is no longer in beta! The mainnet-beta alias is deprecated. Please use mainnet or -um instead.”
In its announcement, the Foundation asked documentation and tooling teams to update the network name to reflect the new designation. Websites, block explorers, and other ecosystem interfaces will also gradually remove references to mainnet beta.
Solana 1.0 is a protocol version; Agave and Firedancer will retain their own version numbers
The number 1.0 can easily be mistaken for a software version. The Foundation explains that the protocol defines the shared rules all validators follow, while clients are the software that implements those rules. Agave and Firedancer have their own codebases, release schedules, and version numbers.
Anza added on X: “Solana 1.0 is a protocol version shared by all clients. Agave will keep its own version numbering.”
The Foundation also noted that announcing a protocol version does not mean all related improvements will be activated at once. Software releases and on-chain feature activations each have their own thresholds and timelines. Validators and RPC operators should check which client versions support each protocol update, while application developers should continue to track API and SDK changes as usual.
Foundation: Mainnet has been a production network since its genesis block
The Foundation explained why it is removing the label now: Solana has been a production network since its genesis block, supporting real transactions, applications, and assets, but the name mainnet-beta had never been updated to reflect that.
The announcement highlighted two recent developments. First, Alpenglow consensus has been activated on mainnet, changing how validators reach consensus and bringing transaction finality to around 150 milliseconds. Second, the Firedancer client, developed independently of Agave, has gone live, so the network no longer has to rely on a single codebase.
The Foundation said Solana 1.0 recognizes progress in network performance, resilience, and developer experience. Upcoming features, compatible client versions, and activation statuses will be published on the Solana Upgrades page.
This article, “Solana drops the beta label more than six years after mainnet launch and sets the protocol version at 1.0,” first appeared in .
【Further Analysis】
【My Further Perspective】
Solana’s removal of the “beta” label and designation of its protocol as version 1.0 mark the blockchain’s formal transition from a “rapidly iterating testing ground” to “enterprise-grade infrastructure.” Solana has often faced criticism over network outages and its reliance on a single client, but the launch of the independent Firedancer client has brought code diversity, while the Alpenglow consensus mechanism has improved settlement efficiency. The underlying architecture is now significantly more predictable. This is more than a branding change: it also eases some of the compliance and risk-management concerns that have made traditional financial institutions hesitant to enter the ecosystem.
【Market Impact】
1. **Cryptocurrency market (SOL)**: **Bullish**. Dropping the beta label could strengthen SOL’s standing as an institutional-grade asset. If the market later advances applications for a spot SOL ETF, the network’s maturity will be a strong supporting argument.
2. **U.S. stock market**: **Neutral to bullish**. This is an indirect positive for crypto trading service providers such as Coinbase (COIN) and Robinhood (HOOD). More stable infrastructure could attract additional high-frequency trading and on-chain activity, increasing trading and custody revenue for related publicly traded companies.
3. **Taiwan stock market**: **Neutral**. Solana uses a proof-of-stake (PoS) mechanism, so it does not directly drive demand for hardware among Taiwanese graphics card or mining-related stocks. Any impact will mainly come indirectly through shifts in overall risk appetite in the crypto market.
【What to Watch Next】
1. **Stability under high-pressure conditions**: Closely monitor whether the 1.0 protocol and Firedancer can consistently maintain transaction confirmations within 150 milliseconds without errors during periods of high transaction volume, such as popular asset launches or sharp market volatility.
2. **Institutional ecosystem integration**: Watch whether traditional financial players—including RWA asset issuers, stablecoin issuers, and payment giants—accelerate their expansion onto Solana after the 1.0 release.
【Risk Reminder】
Removing the beta label also means losing the psychological safety net of being in a “testing phase.” If a major outage still occurs on mainnet after version 1.0 launches, the damage to market credibility will be far greater than before. In addition, continued caution is warranted regarding the overall liquidity squeeze on crypto markets from global macroeconomic and monetary policy.