Anza says no Alpenrush as Solana Alpenglow stays off mainnet September 28
By Node Zero
September 28, 2026
Solana’s Alpenglow consensus upgrade did not flip live on mainnet on September 28—the watchlist snag day after prior coverage framed Anza’s Agave calendar as the start of feature activation (9836). A same-day desk check against Solana’s public mainnet RPC returned null from getAgGenesisCert, the Foundation-documented probe that stays empty while a cluster is still on TowerBFT and only populates once an Alpenglow genesis certificate exists. That null is the operational UPDATE: activation-day rumors of a mainnet Alpenglow cutover do not match the live cluster state.
BeInCrypto, timestamped about 09:54 UTC September 28, wrapped the pushback under the line “no Alpenrush.” Roger Wattenhofer, head of research at Anza (Agave’s developer) and an ETH Zurich professor, posted that a protocol tested for only a few days should not be activated: “Why would we test a protocol for only a few days before activating it? There is no Alpenrush.” Solana co-founder Anatoly Yakovenko quoted that stance with a one-word reply, “decel,” in a post BeInCrypto dates to September 27—slow-down slang versus “accel.” Attribute the quotes to those X posts as relayed by BeInCrypto; this desk is not inventing a separate Anza blog post.
What September 28 actually was on the schedule. Anza’s Agave v4.3 release calendar lists the date as when mainnet resumes feature activation—a software window, not a labeled Alpenglow mainnet launch. BeInCrypto notes the entry never names Alpenglow, and the follow-on v4.4 tentative window around November 9 likewise does not assign Alpenglow a mainnet date. The Solana Foundation’s Alpenglow upgrade page still frames expected mainnet activation in Q3 2026 language tied to Anza’s v4.3 schedule, while instructing operators to gate Alpenglow-specific behavior on the genesis-certificate call rather than on a calendar day. Prior chapters already cleared both public testnets and the Sep. 21 general-adoption recommendation; those steps do not equal a mainnet consensus flip.
Why NFT and marketplace desks still care. Faster finality targets (~150 ms in Foundation copy versus roughly 12.8 seconds today) change how NFT venues, mint bots, and settlement rails time confirmations—but only after mainnet actually migrates. Shipping day rumors without a non-null genesis cert are liquidity noise. SOL tape barely moved on the rumor collapse in BeInCrypto’s market note (~$119.85, down about 0.36% over 24 hours at its press time)—treat that print as secondary market color, not proof of who was positioned for a Sep 28 switch.
How this UPDATE differs from 9836. That chapter correctly reported that Anza’s schedule begins feature activation on September 28 and warned begin ≠ finished. Today’s new facts are the day-of snag package: mainnet getAgGenesisCert still null; Wattenhofer’s “no Alpenrush” line; Yakovenko’s “decel” reply (dated Sep 27 in the wrap); and BeInCrypto’s Sep 28 confirmation that media mainnet-launch rumors collapsed against those primaries. Do not rewrite 9836—link it and append the tracker.
Client and observation context still matter for the next chapter. Prior desk notes and Anza’s feature-gate tracker language have tied public Alpenglow testing to Agave v4.3 while marking Firedancer and Frankendancer support as not yet available for that activation path—so a mainnet consensus flip would also be a client-mix story, not only a calendar story. Foundation operator docs already tell validators to confirm cluster state with the genesis-certificate RPC or CLI rather than assuming a date. Until that probe stops returning null on mainnet-beta, NFT settlement desks should keep treating ~150 ms finality as a testnet/target figure, not a live mainnet property. Watchlist stop rule remains: confirm activation with no material incidents for roughly 24 hours after a real flip—not after a rumor day.
What not to invent: that Alpenglow activated on mainnet today; that every Agave feature gate flipping on Sep 28 equals Alpenglow consensus; that Firedancer or Frankendancer already support the mainnet switch (prior trackers flagged testnet limits); that November 9 is a firm Alpenglow date; or that “decel” is an official Foundation roadmap amendment. Stick to the null mainnet genesis-certificate check, Anza research-head wording via BeInCrypto, the Agave calendar distinction, and Foundation docs that tell builders to wait for the certificate rather than the calendar.
Bottom line: On September 28, Solana mainnet still returns a null Alpenglow genesis certificate while Anza’s research head says there is no Alpenrush—Dev Pulse UPDATE for the Alpenglow tracker after the Sep 28 feature-window chapter (9836).
Disclaimer: This article is provided for informational and educational purposes only. It does not constitute financial, investment, legal, or trading advice. The NFT market is highly volatile, and past performance is not indicative of future results. Readers should conduct their own research and consult qualified professionals before making any decisions related to digital assets. The cover image for this article may have been created using artificial intelligence (AI).
