Solana’s Alpenglow is a planned change to how the network reaches consensus. Its first phase, Votor, is designed to replace TowerBFT’s on-chain voting transactions with validator-to-validator votes and aggregated certificates, targeting much faster finality. It has not yet activated as the network’s consensus protocol: the live BLS-key and Validator Admission Ticket requirements are prerequisites, not the switch itself.
What Alpenglow changes
Alpenglow is a proposed core protocol migration. Its initial phase replaces Solana’s current Proof-of-History and TowerBFT consensus arrangement with Votor. It does not initially replace the system that distributes block data: Turbine remains in place until a later Rotor phase. The proposal describes Alpenglow as incompatible with the old consensus protocol, so this is a coordinated network upgrade rather than a setting users can opt into individually. SIMD-0326
Votor: votes and certificates
Under the proposed Votor design, validators send votes directly to other validators instead of submitting each vote as an on-chain vote transaction. Validators’ signatures are combined into certificates that show whether the required share of stake voted for a block. Solana’s proposal gives TowerBFT finality as 12.8 seconds and describes Votor as using one- or two-round paths; these are proposal comparisons, not measurements of an activated Alpenglow mainnet.
Rotor: data dissemination later
Rotor is planned as a later phase to replace Turbine’s tree-based block propagation. It is not part of Votor’s initial scope, and the rollout guide does not give Rotor a scheduled release. Thus, Alpenglow’s first consensus change should not be confused with a simultaneous replacement of every part of Solana’s block-delivery system. Solana’s Alpenglow overview
#1 Best Overall
How Votor’s finality paths work
The proposal defines two ways to finalize a block, depending on how much stake participates and how many rounds are available. The percentages below are proposal thresholds, not a report of current validator participation.
| Path | Rounds | Proposal threshold | What it means |
|---|---|---|---|
| Fast finalization | One | 80% of stake | A notarization certificate at this threshold can finalize the block. |
| Slow finalization | Two | 60% thresholds | Two rounds and the relevant certificates provide the slower path to finality. |
A finalized block also determines earlier undecided slots in its ancestry; slots omitted from that chain are skipped, according to SIMD-0326. The one-round path can be faster when the higher threshold is reached, while the two-round path is designed for cases where that fast certificate is unavailable.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
Is Solana finality already 150 milliseconds?
No. Approximately 150 milliseconds is Solana’s stated target for Votor finality, not an achieved post-activation mainnet result. Solana’s upgrade page contrasts that target with the 12.8-second TowerBFT figure in the 2025 proposal. The comparison describes intended protocol performance; it is not an independent benchmark or a guarantee that every transaction will be final in 150 milliseconds. SIMD-0326 and Solana’s upgrade guide
What the proposal trades for speed
Participation and security assumptions
Solana summarizes Alpenglow’s resilience target as a “20+20” model: 20% malicious stake plus 20% offline stake. In its security discussion, SIMD-0326 acknowledges that the design does not provide the 33% Byzantine security associated with two-round voting protocols. The proposal authors argue that the one-round fast path and 40% crash-failure resilience make this trade-off worthwhile. That is their rationale for the design, not a universal conclusion about which consensus model is preferable. SIMD-0326 and Solana’s Alpenglow overview
Recommended Free Tools
Less vote overhead, more migration risk
The proposal aims to reduce latency, bandwidth use, and consensus computation overhead by changing vote transport and aggregation. Its stated drawback is the risk and difficulty of implementing a large, incompatible protocol change. Lower overhead and faster finality are intended benefits; they should not be read as proof that the migration itself is simple or risk-free.
What is live, and what remains ahead
Solana Foundation’s July 2026 update says BLS public-key registration activated on mainnet on July 8, 2026, and Validator Admission Ticket (VAT) gating activated on July 22, 2026. These are validator admission prerequisites; VAT activation did not turn on Alpenglow consensus. Validators without registered BLS keys stop participating in consensus, according to that update. BLS Pubkey and the Validator Admission Ticket
Rank #4
The remaining consensus switch is associated with Agave 4.3. Solana’s pages differ on the expected quarter: the Foundation’s BLS/VAT update gives Q4 2026, while the Alpenglow rollout overview lists Q3 2026 for Votor. Those are forecasts, not a confirmed activation date; timing can move. Rotor is described as a later release without a scheduled date.
Validator admission and costs
The Foundation update lists a maximum admission of 2,000 validators under VAT. It also gives a VAT fee of 1.6 SOL per epoch after full Alpenglow migration. Before the consensus switch, voting validators continue paying on-chain vote transaction costs. These are rollout-specific figures from Solana Foundation’s 2026 guidance, not a statement that the future fee has already replaced current vote costs. Foundation VAT update
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Who needs to prepare
Ordinary Solana users
Solana says users do not need to migrate wallets or change how they sign, send, or approve transactions. The execution experience is intended to remain unchanged. Solana’s Alpenglow overview
Application developers
Apps that only submit transactions and read account state are not expected to need changes. Developers who consume streams of slot or bank data should account for more than one candidate bank per slot and the new bank_id field. This distinction matters for infrastructure that assumes one bank maps neatly to each slot, even when the app’s ordinary transaction flow is unaffected. Solana’s upgrade guide
Validators
Validators must have a registered BLS public key to meet the active admission requirement. Solana’s guidance also calls for Agave 4.3 before joining Alpenglow consensus. Because BLS/VAT gating is already active, key registration is a present operational requirement; installing the consensus-capable client is tied to the later switch. Consult current Solana operator guidance before scheduling an upgrade, since the activation quarter is not consistent across the official pages.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
