Solana’s highly anticipated Alpenglow consensus upgrade did not activate on mainnet on September 28, despite reports and market calendars pointing to that date, with developers explicitly pushing back against expectations of an imminent rollout.
Roger Wattenhofer, head of research at Solana development firm Anza and a professor at ETH Zurich, questioned why developers would move a major consensus overhaul into production after only a short period of public testing.
“Why would we test a protocol for only a few days before activating it?” Wattenhofer wrote, concluding: “There is no Alpenrush.”
Solana co-founder Anatoly Yakovenko reinforced the message on September 27, responding to the discussion simply with “decel” — a play on the crypto industry’s frequent “accel” shorthand for accelerating development.
The clarification is important because September 28 was never formally established as Alpenglow’s mainnet activation date.
Where the September 28 Date Came From
The confusion appears to have originated with the release schedule for Agave v4.3, the validator client developed by Anza.
That schedule identified September 28 as the date on which Solana mainnet-beta would resume feature activation. It did not identify Alpenglow as one of the features scheduled to activate that day.
The distinction subsequently became blurred as the date circulated through crypto media and upgrade calendars, effectively turning a general feature-activation window into an assumed Alpenglow launch date.
Solana’s own network data confirms that Alpenglow remained an upcoming feature rather than an activated mainnet upgrade. The Solana Explorer lists SIMD-0326: Alpenglow among upcoming features and shows testing activation epochs on non-mainnet environments.
Testing had already progressed significantly. Solana’s Explorer showed Alpenglow operating on devnet by September 27, explicitly identifying the environment’s consensus mechanism as Alpenglow and displaying certified blocks produced under the new system.
Anza’s subsequent v4.4 schedule reportedly identifies November 9 as another tentative mainnet feature-activation window, but that date also does not constitute a confirmed Alpenglow launch date.
Why Alpenglow Is a Major Solana Upgrade
Alpenglow is substantially more consequential than a routine validator software update because it changes Solana’s underlying consensus architecture.
The proposal, designated SIMD-0326, is intended to dramatically shorten the time required for the network to reach finality. Developers have targeted approximately 150-millisecond finality, compared with roughly 12.8 seconds for full finality under Solana’s existing architecture.
That would represent a major change for applications where rapid certainty that a transaction cannot be reversed is important, including trading, payments and other latency-sensitive financial applications.
But precisely because Alpenglow changes consensus, developers have greater reason to test it extensively before mainnet activation. A failure at the consensus layer carries substantially different risks from a problem affecting an individual application.
The September 28 episode is therefore better characterized as a misinterpreted schedule rather than a delayed launch. There was no official September 28 Alpenglow activation that developers subsequently postponed.
Solana’s mainnet continued operating normally after the date passed. The network’s official Explorer still categorized Alpenglow as an upcoming mainnet feature on September 29.
For validators and SOL holders, the practical conclusion is straightforward: Alpenglow remains in the testing and deployment process, but there is currently no confirmed mainnet activation date.
Wattenhofer’s “No Alpenrush” comment captures the development approach succinctly. Solana may be pursuing substantially faster consensus, but developers are signaling that one of the network’s most consequential technical changes will not be pushed onto mainnet merely to satisfy an assumed calendar date.