Is Solana's Alpenglow Upgrade Live? How to Tell a Release Schedule From an Activation

Over the weekend, a date started circulating in crypto feeds: Solana's Alpenglow consensus upgrade would switch on for mainnet on Sunday, September 28, 2026. It did not. So the question readers are actually asking is a practical one: is Alpenglow live on Solana, and how can you tell when any blockchain upgrade has really been activated rather than merely scheduled?

The short answer

No. As of September 29, 2026, Alpenglow runs on Solana's testnet, not on mainnet, and no mainnet activation date has been announced. The September 28 date came from a general software release calendar that never named Alpenglow, which is a useful lesson in the difference between a client release, a feature gate and an actual activation.

Where the September 28 date came from

Solana's main validator client, Agave, is maintained by Anza and ships on a published rollout calendar. The Agave v4.3 release schedule on GitHub lists a sequence of milestones: testnet adoption, devnet upgrade, volunteer stake on mainnet, a recommendation for general adoption on September 21, and finally "Mainnet-beta: Resume feature activation" on September 28. The page describes itself as informational only, with all dates subject to change, and asks operators to wait for Discord announcements before acting.

Because v4.3 is the release that carries Alpenglow's consensus code, some readers joined the dots and treated "resume feature activation" as "Alpenglow goes live." The line never said that. A September 23 correction appended to a Solana Compass report clarified that the September 28 entry was not an Alpenglow date but the point at which Anza resumes processing queued feature gates in general.

The rumour still travelled far. CoinDesk's Crypto Week Ahead calendar, published on the morning of September 28, listed that day as the launch of Solana's Alpenglow upgrade. That is a reminder that even established outlets can compress a nuanced schedule into a single headline date.

What the developers said

On September 28, two of the people closest to the protocol pushed back publicly. According to reports from DiarioBitcoin and CryptoTicker, Anza head of research Roger Wattenhofer wrote "No Alpenrush," and Solana co-founder Anatoly Yakovenko replied with one word: "decel." DiarioBitcoin and KuCoin News also report that Wattenhofer pointed out the protocol had only been in public testing for a matter of days. We relied on those reports rather than viewing the original posts directly.

What Alpenglow actually changes

The substance explains why developers are in no hurry. Alpenglow is not a routine patch; it replaces the core of how Solana agrees on blocks.

Voting and finality

According to Anza's Alpenglow documentation, the upgrade replaces Tower BFT's voting and finality logic with a new component called Votor, and targets finality in roughly 150 milliseconds under normal network conditions. Anza's original May 2025 announcement described a median of about 150 ms, sometimes as fast as 100 ms, based on simulations using mainnet stake distribution. Blockworks put current Solana finality at about 12.8 seconds. These are design targets and simulations, not measured mainnet performance.

Fewer on-chain vote transactions

Today, validators post vote transactions on-chain and pay fees for them. Blockworks reported in 2025 that these votes made up roughly 70% of Solana's on-chain transactions; a later Solana Compass estimate put the figure nearer 59%. Estimates differ, but the direction is the same: Alpenglow moves voting off-chain into direct validator messaging and records aggregated results as compact certificates.

A new validator economy

Anza's documentation describes a validator admission mechanism that admits at most 2,000 eligible validators, prioritised by stake, with a validator admission ticket deducted from vote accounts each epoch. Operators also need to register BLS keys. The protocol claims "20+20" resilience, meaning it is designed to stay safe with up to 20% adversarial stake plus a further 20% of stake offline. When the governance proposal, SIMD-0326, passed in September 2025, Blockworks reported 98.94% of participating votes in favour, with 52% of network stake taking part, while noting concerns that the admission ticket could raise barriers for smaller validators.

Why caution is rational here

Three details from the rollout itself explain the slower pace.

• Client diversity is a constraint. Solana Compass reported that Anza warned Firedancer and Frankendancer, the alternative clients developed by Jump Crypto, do not support the Alpenglow migration, and that testnet nodes running them had to switch to Agave. On mainnet, any stake still running an unsupported client at activation would be a risk.
• Adoption started from a low base. The same outlet reported that in early September only about 0.39% of active stake ran v4.3.
• Testnet time is short. Alpenglow activated on testnet in the week of September 22, according to Solana Compass and CryptoTicker. A consensus change usually needs a longer period of observed behaviour, including failure and recovery scenarios, before it touches real value.

How to tell whether an upgrade is really live

The Alpenglow episode offers a reusable checklist for any network upgrade, not just Solana's:

1. Separate the release from the activation. A client version shipping, or being recommended for adoption, does not mean new rules are in force. On Solana, many changes sit behind feature gates that are switched on separately.
2. Look for the feature name, not only a date. A calendar line that says "resume feature activation" without naming a feature is not an announcement for that feature.
3. Prefer the maintainers' own channels. Release notes, the project's documentation and official announcements outrank aggregated calendars and social posts.
4. Treat "tentative" literally. Both the v4.3 and v4.4 schedules say dates can change.
5. Check price reaction with care. CryptoTicker reported SOL at $118.75 on September 28, down 3.29% on the day, while DiarioBitcoin cited $119.85 at its time of writing. A small move tells you little about the upgrade itself; broader market conditions were weak the same day, and CoinDesk reported bitcoin down more than 2% over 24 hours.

What we know vs. what we're inferring

What we know

• The Agave v4.3 schedule lists September 28 as "Mainnet-beta: Resume feature activation" and does not mention Alpenglow.
• Alpenglow is live on testnet and not on mainnet as of September 29, 2026, according to multiple reports.
• Anza documents a roughly 150 ms finality target, a cap of 2,000 admitted validators and per-epoch admission tickets.
• The Agave v4.4 schedule lists November 9, 2026 for "Mainnet-beta: Resume feature activation," again marked tentative.

What we're inferring

• That developers want a longer testnet period is our reading of their public comments, not a stated timeline.
• November 9 is a feature activation window. Nothing we found says Alpenglow will be activated then, and reports say it is not listed for that window.
• Real-world finality on mainnet may differ from simulation results; that cannot be known until activation.

What to watch next

• October 5, 2026: the v4.4 schedule targets resumed feature activation on testnet and a devnet upgrade.
• October 19 and 26, 2026: calls for volunteers to move 10% and then 25% of mainnet stake to v4.4.
• November 2 and 9, 2026: general adoption of v4.4 on mainnet, followed by the next feature activation window.
• An explicit Alpenglow announcement from Anza or the Solana Foundation naming the feature gate and a date. Until that exists, treat any launch date as speculation.
• Client support: whether Firedancer-based clients add Alpenglow support before mainnet activation.

Educational information only — not financial advice.