Alpenglow explained
The largest change to Solana's core protocol since launch, live since epoch 1064. What it replaced, what it costs validators, and what is still to come.
Alpenglow is Solana's consensus protocol since epoch 1064, which began on 21 October 2026 at about 13:36 UTC. Validators now send votes directly to each other instead of as transactions, and a block is final after one round of votes from 80% of stake or two rounds from 60%, targeted at about 150 ms instead of TowerBFT's 12.8 seconds; only the voting half (Votor) is live, and the data-relay half (Rotor) is not yet scheduled.
- Block time
- 215 ms
- Real transactions a second
- 1,771
Consensus is how the validators that run Solana agree on which block comes next and when a block can no longer be reversed. From 2020 until October 2026 Solana did this with TowerBFT, layered on a hash-chain clock called proof of history. Since epoch 1064 it does it with Alpenglow, a protocol set out by Quentin Kniep, Kobi Sliwinski and Roger Wattenhofer in a white paper published by Anza, with security proofs (SIMD-0326).
What changed, side by side
| TowerBFT | Alpenglow (Votor) | |
|---|---|---|
| Votes | transactions in blocks, about 1 SOL a day per validator in fees | messages sent directly between validators, aggregated into one BLS signature per certificate |
| Finality | after 32 slots of stacked votes, about 12.8 s | one round at 80% of stake, or two rounds at 60%; about 150 ms targeted |
| Clock | proof of history paces blocks | local timeouts; proof of history no longer paces block production |
| Safety model | one-third of stake Byzantine | “20+20”: 20% Byzantine plus 20% crashed or offline |
| Validator set | unlimited | the 2,000 highest staked |
| Paying to take part | vote transaction fees, half burned | 0.8 SOL Validator Admission Ticket per epoch, all burned |
| Proof | no published security proof (SIMD-0326’s words) | safety and liveness proofs in the white paper |
How a block is finalized now
Each validator watches for the leader’s block in its slot and casts one first-round vote: notarize the block, or skip the slot if no valid block arrived before its local timeout.
- If 80% of stake notarizes the same block, that is a fast-finalization certificate: the block is final after one round.
- If at least 60% notarizes, validators cast a second-round finalize vote; 60% of finalize votes plus the notarization certificate finalize the block (the slow path).
- If 60% votes to skip, the slot is skipped and the chain moves on.
When a block is finalized, every earlier block it builds on is final too. The thresholds come from SIMD-0326; the 150 ms target from solana.com, which is careful to say that is the time to finality, not how often blocks are produced. Blocks still come every slot: 215 ms on average on November 16, 2026.
The 20+20 security model
TowerBFT, like most two-round protocols, stays safe as long as less than a third of stake misbehaves. Alpenglow trades that for speed: SIMD-0326 states it is safe against up to 20% of stake acting maliciously plus another 20% simply offline, and it keeps working with up to 40% crashed.
That moves the number worth watching. The usual “Nakamoto coefficient” counts how many validators together pass a third of stake: 18 on November 16, 2026. Under Alpenglow the more telling threshold is 20%, which far fewer validators reach. Our validators page reads all three thresholds (20%, a third and 40%) from the network, along with how much stake sits with one hosting provider, which matters for the “offline” half of the model.
What validators had to do
- Run an Agave-based client for the switch. solana.com lists v4.3.2 of Agave, Jito-Solana or Harmonic Salsa; Firedancer and Frankendancer “were not supported for the migration”. Firedancer’s own release notes say “Migration from Tower to Alpenglow will not be supported” (v26.10.2); Firedancer-based clients returned afterwards on Alpenglow builds (validators and clients).
- Register a BLS key. Certificates combine thousands of votes into one signature, which Solana’s usual ed25519 keys cannot do. Registration became mandatory with the admission ticket on 22 July 2026.
- Fund the admission ticket. Each validator must keep at least 0.8 SOL above the rent-exempt minimum in its vote account; the ticket charged at the start of epoch E pays for taking part in epoch E+1. Unpaid means no voting and no blocks next epoch. The amount was 1.6 SOL per 48-hour epoch in SIMD-0326 and was scaled with each slot-time step so it stays about 0.8 SOL a day (SIMD-0525).
What stayed the same
Execution: the virtual machine, transaction formats, programs, accounts and fees are unchanged. Validators are still rewarded from inflation in proportion to their stake and their voting; SIMD-0326 carried the existing reward rules across “as they are” and leaves economic changes to later proposals.
What is not live yet
- Rotor, the replacement for Turbine that spreads block data in a single relay hop. solana.com: planned “for a later release … and is not yet scheduled”.
- Fast leader handover, which lets the next leader start before the previous block is final. solana.com says it ships in Agave 4.4 and that Anza expects more than one candidate block per slot in under 1% of slots; we did not find its feature active on mainnet on November 16, 2026.
What this means for you
If you send, swap or stake, nothing changed in what you do. Settlement is faster, explorers now treat “confirmed” and “finalized” as the same, and any throughput figure from before 21 October 2026 that included votes cannot be compared with today’s. If you follow decentralization, look at the 20% threshold, not only the one-third one. The dated list of every 2025 and 2026 protocol change is on the upgrades page.
Questions people ask
When did Alpenglow go live?
At the start of epoch 1064, on 21 October 2026 at about 13:36 UTC (solana.com). The feature activated at slot 459,648,000; the last TowerBFT block was slot 459,652,999, and Alpenglow consensus ran from slot 459,653,000.
Is Alpenglow live on mainnet?
Yes, its voting half, Votor, is. Rotor, which would replace Turbine for spreading block data, is planned for a later release and not yet scheduled, according to solana.com on our last check.
What does Alpenglow mean for users?
Nothing to do: wallets and apps work as before, and a transaction is final in a fraction of a second instead of about 12.8 seconds. Exchanges and apps that waited for finality can credit deposits much sooner.
Is Alpenglow less secure than TowerBFT?
It makes a different trade. SIMD-0326 says it gives up the one-third Byzantine tolerance of two-round protocols for a 20+20 model: safe with up to 20% malicious stake plus a further 20% offline. On November 16, 2026 the 18 largest validators held more than a third of stake; see our validators page for the 20% figure.
Sources
- solana.com: Alpenglow upgrade page (activation, breaking changes, migration)
- SIMD-0326: Alpenglow
- Alpenglow white paper v1.1 (Kniep, Sliwinski, Wattenhofer)
- SIMD-0357: Alpenglow Validator Admission Ticket
- solana.com: BLS pubkey and the Validator Admission Ticket
- SIMD-0525: VAT scaled to 0.8 SOL per epoch at 200 ms slots
- Firedancer v26.10.2 release notes (Alpenglow support; no migration from Tower)