Alpenglow cuts Solana finality from 12.8 seconds to about 150 milliseconds
The protocol replaces TowerBFT and shifts validator voting off the blockchain, changing how blocks become final and how network capacity is used. Reports describe different activation milestones and schedules, so the timing accounts do not align. (facts: ["f1","f2","f3","f9","f20","f22"])
Alpenglow brings reported finality time down from about 12.8 seconds to roughly 150 milliseconds.12
A block can be finalized instantly when affirmative votes represent 80% of stake.2
Validators voted in favor of the Alpenglow proposal, SIMD-0236, in September 2025.2
Story
What Alpenglow changes on SolanaAlpenglow reduces Solana’s reported finality time from about 12.8 seconds to roughly 150 milliseconds, a change from a multi-second wait to a fraction of a second.12 Finality is the point the sources describe as a block becoming final; under the new protocol, conditional confirmation and full finality are combined into one step.2 The change replaces TowerBFT, Solana’s previous consensus system, with Alpenglow, whose voting mechanism is called Votor.1 The reported speed comparison concerns finality time, not a stated increase in transaction volume or a measurement of every application’s performance.12 CoinPost quoted Helius chief executive Mert Mumtaz describing the change as Solana becoming “95% faster.”1
The protocol changes how validators communicate their votes: they send them directly to one another, outside the blockchain, with each vote weighted by stake.12 The cited threshold for immediate block finality is affirmative votes representing 80% of stake.2 Moving votes off-chain leaves more blockchain capacity available for user transactions, according to CoinPost.1 CoinDesk also says the migration may sharply reduce reported transaction counts because validator votes will no longer be recorded on-chain.3 That possible count change concerns what is included in the reported total; the cited source does not say that user trading activity must fall.3
Alpenglow’s stated safety tolerance covers malicious stake of up to 20% and a further 20% of stake that is offline.12 Together, those categories amount to 40% of stake, while the protocol is described as able to continue operating safely under that combination.12 The threshold for finalizing a block is expressed differently: it requires affirmative votes representing 80% of stake.2 These percentages refer to stake, not to a count of validators, and the sources provide no corresponding number of participating validators.2 If finality does not occur for 10 seconds, validators are to lengthen block times gradually until messages can pass through.2
The upgrade was implemented in Agave validator software, and independent validators activated it, according to Decrypt.2 For the migration described by CoinDesk, validators must use Agave 4.3.0; operators using Firedancer or Frankendancer need to change software temporarily.3 The sources therefore describe software coordination across validator implementations, and one account characterizes that handoff as complex.23 Before mainnet, Alpenglow went through public testing, red-team work, penetration testing, migration rehearsals and a security competition.2 Those steps are reported as preparation for the change; the source does not provide results or findings from the tests.2
Decrypt reports that validators approved proposal SIMD-0236 in September 2025, with 98% voting in favor.2 Decrypt says the community test cluster began running Alpenglow in May 2026; that report set a late-Q3 or early-Q4 target for mainnet activation.2 A separate Decrypt account says the protocol went live on mainnet-beta at slot 459,653,000, replacing TowerBFT.2 That account places TowerBFT’s retirement at around 14:00 UTC and says the existing ledger continued through the change.2 The test-cluster and mainnet descriptions identify different deployment stages, while the reports do not reconcile their stated timing.2
CoinDesk gives another schedule: Solana planned the upgrade for Oct. 21, with finality targeted at about 150 milliseconds.3 CoinDesk’s plan places the migration in epoch 1064 and forecasts its start at about 15:00 UTC on Oct. 21.3 Under that plan, the older system would continue through the first 5,000 slots, with Alpenglow taking over about 18 minutes later.3 This planned sequence differs in presentation from the Decrypt account describing mainnet-beta as already live at a particular slot.23 The reports supplied here do not establish how the Oct. 21 schedule relates to the stated mainnet-beta activation, so both accounts are presented separately.23
CoinDesk says vote transaction fees, previously about 1 SOL per epoch, are to be removed and replaced by a flat admission charge of 0.8 SOL.3 The two amounts use different fee descriptions: one is tied to an epoch, while the replacement is described as a flat admission fee.3 The source does not specify the number of validators affected or provide a total change in fees paid across the network.3 CoinDesk’s software requirement also means that operators using the named alternative clients must switch temporarily for this migration.3
CoinPost presents faster settlement as useful to institutions, citing transactions that settle in about 150 milliseconds.1 It also says Web3 applications could operate at speeds comparable to Web2 applications.1 These are descriptions of potential benefits in the source, alongside the measured change in finality time, rather than separate measurements of institutional or application performance.12 Anza chief executive Brennan Watt called the upgrade the largest and most ambitious blockchain upgrade since Ethereum’s Merge, as reported by Decrypt.2
Alpenglow’s rollout is not described as fully complete in CoinPost’s account, which says a new block-propagation mechanism named Rotor is still planned.1 The protocol change and that planned propagation system are distinct items in the account: Alpenglow changes consensus, while Rotor is identified as a way to propagate blocks.1 A post-quantum form of Alpenglow, called Quantumglow, is also planned, but Decrypt reports no committed date for it.2 The available accounts therefore describe the faster-finality protocol, a further planned propagation change and a separate future version without a fixed date.12
Disagreements
Where the sources do not matchMainnet activation timing
Decrypt2
CoinDesk3
Possibly: The accounts give different descriptions of mainnet timing, and the supplied reports do not explain how the stated live activation relates to the Oct. 21 migration schedule; they may refer to different stages or reporting contexts.
History
How it came to this- September 2025Validators approve the proposalValidators voted in favor of proposal SIMD-0236.
- May 2026Community test cluster goes liveAlpenglow began running on Solana's community test cluster.
- Oct. 21CoinDesk's scheduled migrationThe plan placed the migration in epoch 1064, with the older system running through the first 5,000 slots before Alpenglow took over about 18 minutes later.
- Around 14:00 UTCTowerBFT retired on mainnet-betaDecrypt reports validators retired TowerBFT while carrying the existing ledger forward.
- Nowroughly 150 milliseconds Solana finality time
- Oct. 21CoinDesk's migration schedule calls for Alpenglow to take over after the old system runs through the first 5,000 slots; the reports also differ on mainnet timing.
Impact
Spreading outward, level by level- Level 1Block finality
Alpenglow combines conditional confirmation and full finality into one step; affirmative votes representing 80% of stake finalize a block instantly.2
Fact - Level 2Validator communication and capacity
Validators send stake-weighted votes directly to one another off-chain. CoinPost says moving votes off-chain leaves more blockchain capacity for user transactions.12
Fact - Level 3Reported transaction counts
Reported on-chain transaction counts may fall because validator votes are no longer included, even if trading activity does not change.
Analysis - Level 4Payments and applications
CoinPost presents near-instant settlement and Web3 applications operating at Web2-like speeds as potential benefits, rather than measurements of application performance.
Analysis
Ahead
Checked automatically when due; the result goes to the track recordCoinDesk's migration schedule calls for Alpenglow to take over after the old system runs through the first 5,000 slots; the reports also differ on mainnet timing.
Sources
What each source supportsWritten by AI from the sources listed below: every fact was checked word for word against its source, and inference is marked apart. How we write