Key Takeaways
- • Alpenglow, Solana's largest consensus change since launch, is scheduled to go live on mainnet on Wednesday, October 21, 2026, at the start of epoch 1064, according to Galaxy.
- • Finality is designed to fall from roughly 12.8 seconds under TowerBFT (about 6 seconds at 200ms slots) to around 150 milliseconds, with votes moved off-chain and aggregated into BLS certificates.
- • A flat Validator Admission Ticket of 0.8 SOL per epoch replaces per-vote fees, which Galaxy estimates at about 2 SOL a day at 200ms slots, meaning validators' voting cost falls by more than half.
- • The fault model shifts from tolerating up to 33% Byzantine stake to up to 20% Byzantine stake, with an additional 20% offline tolerance, for 40% combined.
- • Galaxy has run a validator on the Alpenglow community test cluster since June 18, 2026, through six re-geneses, a failed network-wide migration, and a rollback, and says its validators are ready.
Summary
Solana is scheduled to activate Alpenglow, the largest change to its core protocol since the network launched, on mainnet on Wednesday, October 21, 2026, according to Galaxy Digital's account of its validator operations. Designed by Anza, Solana's core development team, Alpenglow replaces TowerBFT, under which validators submit votes as transactions on chain. Under the new design, validators exchange BLS-signed votes directly, and the aggregated certificate is included in the next block in place of hundreds of individual vote transactions. A block notarized by 80% of stake finalizes in a single round; otherwise a second round finalizes it once 60% notarization and 60% finalization certificates exist. The stated finality target is around 150 milliseconds.
The upgrade also changes validator economics. Under TowerBFT, validators paid a fee on every vote, which the slot-time reductions completed on October 9 pushed to roughly 2 SOL a day at 200ms slots, up from about 1 SOL a day at 400ms. Alpenglow replaces this with a Validator Admission Ticket, specified under SIMD-0357 at 1.6 SOL against the original 400ms slot and 48-hour epoch. At today's 200ms slots and roughly 24-hour epochs, the ticket equals 0.8 SOL per epoch, or about 0.8 SOL a day. Galaxy notes that half of each vote fee previously went to block leaders, so the net effect depends on how many blocks a validator produces, and hardware, bandwidth and hosting costs are unaffected. Vote rewards are not changed under SIMD-0326, though vote credits will be derived from BLS certificates. A vote account that cannot cover the ticket at an epoch boundary is excluded from consensus for that epoch.
Alpenglow also shifts the fault model. TowerBFT tolerates up to 33% Byzantine stake and no offline stake above that threshold. Alpenglow tolerates up to 20% Byzantine stake for safety and a further 20% offline for liveness, for 40% combined. Galaxy says the designers accepted this tradeoff because Solana's outages have stemmed from bugs, congestion and correlated crashes rather than coordinated attacks.
Galaxy has operated a validator on the community cluster since June 2026, which launched in early May 2026 with about 50 operators and has grown to roughly 100 validators. The cluster went through six re-geneses, a network-wide migration that failed, and a rollback before the first successful migration. Validators are asked to run an Agave-based client during migration, while Firedancer operators can fail over to Agave and return afterward. Frankendancer will not be supported once Alpenglow is active. The rollout is phased: Phase 1 (Votor) is the voting change, Phase 2 is a fast leader handover, and Phase 3 (Rotor) flattens block propagation. Slashing for double voting is defined but not enabled in the first iteration.
The upgrade also changes validator economics. Under TowerBFT, validators paid a fee on every vote, which the slot-time reductions completed on October 9 pushed to roughly 2 SOL a day at 200ms slots, up from about 1 SOL a day at 400ms. Alpenglow replaces this with a Validator Admission Ticket, specified under SIMD-0357 at 1.6 SOL against the original 400ms slot and 48-hour epoch. At today's 200ms slots and roughly 24-hour epochs, the ticket equals 0.8 SOL per epoch, or about 0.8 SOL a day. Galaxy notes that half of each vote fee previously went to block leaders, so the net effect depends on how many blocks a validator produces, and hardware, bandwidth and hosting costs are unaffected. Vote rewards are not changed under SIMD-0326, though vote credits will be derived from BLS certificates. A vote account that cannot cover the ticket at an epoch boundary is excluded from consensus for that epoch.
Alpenglow also shifts the fault model. TowerBFT tolerates up to 33% Byzantine stake and no offline stake above that threshold. Alpenglow tolerates up to 20% Byzantine stake for safety and a further 20% offline for liveness, for 40% combined. Galaxy says the designers accepted this tradeoff because Solana's outages have stemmed from bugs, congestion and correlated crashes rather than coordinated attacks.
Galaxy has operated a validator on the community cluster since June 2026, which launched in early May 2026 with about 50 operators and has grown to roughly 100 validators. The cluster went through six re-geneses, a network-wide migration that failed, and a rollback before the first successful migration. Validators are asked to run an Agave-based client during migration, while Firedancer operators can fail over to Agave and return afterward. Frankendancer will not be supported once Alpenglow is active. The rollout is phased: Phase 1 (Votor) is the voting change, Phase 2 is a fast leader handover, and Phase 3 (Rotor) flattens block propagation. Slashing for double voting is defined but not enabled in the first iteration.
Go deeper than the headline
Research every firm in this story, track the ones that matter and get the daily briefing — free for 7 days.