The Alpenglow mainnet launch is not happening on September 28, despite reports pointing to that date. Solana co-founder Anatoly Yakovenko answered the rumor with a single word, “decel.”
Alpenglow is a consensus overhaul that targets 150-millisecond finality, down from roughly 12.8 seconds for full finality today. Some outlets had also warned that SOL could drop if the switch did not happen.
Alpenglow Mainnet Launch Date Traced to a Validator Schedule
Roger Wattenhofer, head of research at Anza and a professor at ETH Zurich, pushed back on the reports on X. Anza develops Agave, Solana’s main validator client.
Why would we test a protocol for only a few days before activating it? There is no Alpenrush.
His point was that Alpenglow had entered public testing only days earlier.
Yakovenko then quoted the post and added “decel,” crypto slang for slowing down. In contrast, “accel” signals a push to move faster.
The date likely came from Anza’s Agave v4.3 release schedule. It lists September 28 as the day mainnet resumes feature activation. However, the entry never mentions Alpenglow.
Meanwhile, the follow-up v4.4 timeline sets the next mainnet activation window for November 9. Anza calls that schedule tentative, and it does not name Alpenglow either.
SOL Price Barely Reacts to the Clarification
Solana (SOL) traded at $119.85 at press time, down 0.36% over 24 hours, according to BeInCrypto Markets data. The muted move suggests few traders had priced in a September 28 Alpenglow mainnet launch.
The cautious tone also has a recent backdrop. In August, a routing fault pushed Solana close to a network halt. Against that record, Wattenhofer’s comments suggest developers want to avoid a rushed consensus change.
Alpenglow is also not the only speed upgrade in progress. In August, Solana began halving its block time from 400 to 200 milliseconds. That change speeds up block production, while Alpenglow targets how quickly blocks become final.
Solana has been preparing validators for Alpenglow since July. For now, the upgrade stays on testnet, and neither Agave schedule gives it a mainnet date.