Solana Alpenglow Upgrade: Date, Stakers and Firedancer

Alpenglow upgrade date and status (updated 9 Oct 2026)

• Testnet: live since 24 Sep 2026. TowerBFT, the old consensus, was retired and Votor took over. Anza’s line afterwards was devnet next, then “Mainnet-beta after our observation period.”
• Devnet: live since 25 Sep 2026.
• Mainnet: pending. It ships with Agave 4.3 (Agave is Anza’s validator software) and has no confirmed date. Solana’s Alpenglow page still says “Q3 2026”, which is over, and its BLS and VAT page says Q4 2026. Neither is a date.
• 28 Sep was never real. It came from a line in Agave’s release schedule about feature activations in general resuming. Solana co-founder Anatoly Yakovenko replied “decel” and Anza’s Roger Wattenhofer said “No Alpenrush”.
• 9 Nov isn’t an Alpenglow date either. That’s when Agave 4.4 feature activations are set to resume on mainnet, which is a separate track.

What to watch: Anza on X and Agave’s feature gate tracker, where Alpenglow sits under “Pending Mainnet Beta Activation”. When it leaves that table, it’s happening. I’ll add a line to the update log at the bottom the day it activates.

Do you need to do anything?

There’s no swap, no claim and no new token. Your SOL stays where it is, and no wallet needs an Alpenglow update.

Check your validator is still earning (since 22 July)

Solana’s line is that stakers don’t need to do anything. That holds only if your validator did its part.

Since 22 July 2026, the Validator Admission Ticket (VAT) decides who gets to vote. A validator needs a registered BLS key (a new signing key Alpenglow uses) and has to sit in the top 2,000 by stake. Miss either and it’s shut out. It stops voting and goes delinquent, meaning it earns nothing, and everyone staked to it earns nothing too. Once Alpenglow is on mainnet, VAT also charges each voting validator a flat 1.6 SOL per epoch, burned.

The check takes a couple of minutes:

1. Find your stake account. Open the staking section of your wallet, or paste your wallet address into Solscan and open the stake account listed there. Our block explorer walkthrough shows where everything sits on the page.
2. Read the rewards by epoch. Rewards land once per epoch, one line each. An epoch was about two days until August. Slot times have been cut in stages since then, and from 9 Oct an epoch is about a day. So go by the epoch numbers rather than counting days: every epoch since late July should have a reward, with no gaps. Small is fine. Zero or missing isn’t.
3. Look the validator up on StakeWiz. Paste in the validator address from your stake account and see whether it’s flagged delinquent.

If an epoch shows nothing and the validator is delinquent, move. Native stake has to be deactivated and then delegated again, so expect a short gap in rewards while it switches. The staking guide linked at the top has the steps for each wallet and what to look for in a new validator.

While you’re there, check the commission. A validator charging 100% pays you nothing either, and that has nothing to do with Alpenglow.

What is Solana Alpenglow and what does it change?

Solana Alpenglow is a new consensus protocol (consensus is how validators agree on blocks). It replaces TowerBFT with two parts, Votor and Rotor, and brings finality down to roughly 150 milliseconds.

Under TowerBFT, validators post their votes as transactions inside blocks, and a block is final after about 12.8 seconds. That’s Solana’s own figure, based on the old 400ms slots. Slots were cut in stages from August and reached 200ms on 9 Oct, so it’s quicker today, but there’s no published new number.

Votor comes first, with Agave 4.3. Validators send votes straight to each other instead of writing them into blocks, then bundle them into a certificate (proof that enough stake agreed). If 80% of stake backs a block in the first round, it’s final there and then. If not, a second round needs 60%. Typically that lands around 150 milliseconds, with the two-round path a bit slower.

Rotor comes later and has no date. It replaces Turbine, the system that spreads new blocks across the network (how Solana works covers it), with a single relay layer built to cut network delay.

What you’ll notice, and what stays the same

Things settle almost instantly. Most apps already show “confirmed” in under a second, so the real change is for anything that waits for full finality. After Alpenglow, confirmed and final are close to the same moment.

That’s the part I care about. Some of my DLMM positions on Meteora last under 10 minutes, opened and closed while price is moving. Knowing a close is final almost straight away, rather than confirmed now and final a few seconds later, is one less thing to think about.

TPS charts will look like they crashed. They didn’t. Votes are more than half of all Solana transactions, about 56% in the week to 6 October 2026. Once votes leave the blocks, explorers only count the rest. That’s an accounting change, not a slowdown, so ignore anyone posting “Solana TPS down 57%”.

Fees, how transactions are built, signing, wallets and token accounts all stay as they are. Only consensus changes. Finality is already one of the big differences between Solana and Ethereum, and this widens it.

The trade-off: faster, but a thinner safety margin

TowerBFT keeps working even if up to a third of stake behaves maliciously. Alpenglow lowers that to 20% bad actors, but adds a separate allowance of another 20% for validators that are simply offline. In plain terms, it’s a bit less forgiving of a coordinated attack and more forgiving of validators dropping out. Whole-network halts caused by bugs are a different problem, and that’s where a second client like Firedancer helps.

Validators approved Alpenglow on 2 Sep 2025, with 98.27% of the stake that voted saying yes. I think it’s a fair trade for the speed, and it’s nothing a holder has to act on. Anza not rushing mainnet after a few days on testnet is a good sign.

Firedancer vs Frankendancer: validator software, separate from Alpenglow

A validator client is the software a validator runs. Agave, Jito’s version of Agave, Harmonic, Frankendancer and Firedancer are all clients. Alpenglow is the rulebook every one of them follows.

• Firedancer is Jump’s independent client, written from scratch. The full version has been live on mainnet since 12 Dec 2025.
• Frankendancer is the hybrid: Firedancer’s networking and block production on top of Agave’s runtime and consensus.

Why it matters to you: if every validator runs the same code, one bug can stall the whole chain. With a second independent client, a bug in one doesn’t take everything down.

Client share figures disagree a lot between trackers this year, so treat any single number with care. validators.app lists the client and version each validator runs.

Two dates matter. Jump announced on 11 Sep 2026 that it will end Frankendancer support when Alpenglow goes live on mainnet. And Firedancer added Alpenglow support in its 7 Oct 2026 testnet release (v26.10.0), switched on for testnet and devnet only.

If your validator runs Frankendancer or Firedancer

On testnet, only validators on Agave 4.3 took part in the switch. Firedancer and Frankendancer didn’t support it yet, and validators that weren’t on 4.3 dropped out of consensus. Firedancer’s 7 Oct notes still say it won’t support the switch from TowerBFT to Alpenglow itself, though it can now run on Alpenglow afterwards.

If mainnet goes the same way, these validators will run Agave through the switch. Frankendancer won’t come back after it, because Jump ends support at that point. Full Firedancer validators may be able to move back once Alpenglow is running, but that release is a testnet build and the mainnet steps aren’t published yet. Either way, a validator that misses the switch stops voting, the same as one with no BLS key.

What you do: look up your validator’s client on validators.app, and re-run the rewards check for the first two or three epochs after mainnet activation. If it goes delinquent and stays that way, move.

No migration, no swap, no claim

Alpenglow needs nothing from holders. Any site, DM, pop-up or “Alpenglow airdrop” asking you to connect a wallet, sign something or migrate your SOL is a scam. Upgrades happen on the validators’ machines, never in your wallet, so the usual wallet safety rules apply: don’t connect, don’t sign.

Alpenglow and Firedancer timeline

FAQ

When is the Solana Alpenglow upgrade coming to mainnet?

The Solana Alpenglow upgrade has no mainnet date as of 9 Oct 2026. It’s waiting on Agave 4.3 after Anza’s observation period on testnet and devnet. Neither 28 Sep nor 9 Nov is an Alpenglow date.

Will Alpenglow increase Solana TPS?

Reported TPS goes down, because vote transactions (more than half of today’s count) stop appearing in blocks. The transactions people actually send aren’t slowed.

Does staking APY change with Alpenglow?

Nothing in the upgrade changes how staking rewards are paid. What changes is a validator cost: voting costs a validator roughly 2 SOL per epoch today, and after Alpenglow it becomes a flat 1.6 SOL per epoch, burned. Your return still comes down to your validator’s commission and whether it keeps voting.

Is Proof of History gone?

Effectively, yes, for consensus. Under Alpenglow, Proof of History no longer paces block production.

Will Solana fees drop?

Fee rules don’t change. You still pay the base fee plus any priority fee. Votes leaving the blocks frees up space, but no fee cut comes with it.

Is Firedancer live on mainnet?

Yes. Full Firedancer has run on mainnet since 12 Dec 2025. Its Alpenglow support so far is only in a testnet release.

Update log

• 9 Oct 2026: Published. Alpenglow is live on testnet (24 Sep) and devnet (25 Sep). Mainnet is pending on Agave 4.3 with no confirmed date. Mainnet slot time reached 200ms today.