Solana Sets October 21 Date for Alpenglow's 150ms Finality

Solana has set the date for the biggest change yet to how its network agrees on transactions. Alpenglow activates on mainnet in epoch 1064, which the Solana Foundation's upgrade page says begins on Wednesday, October 21, 2026 at approximately 15:00 UTC.

If you hold SOL or use apps on Solana, the answer to "what do I have to do" is nothing. Solana says nothing about signing, sending or approving a transaction changes, and wallets and applications keep working exactly as they do today. The upgrade changes consensus, not execution, so the Solana Virtual Machine, transaction formats, programs and fees are all left alone.

Alpenglow changes consensus, not execution; the SVM, transaction formats, and fee mechanics are untouched.

The date was announced earlier in October. Here is what the upgrade actually does when it lands.

Faster Finality, and Why It Isn't Block Time

Finality is the moment a transaction becomes irreversible. On Solana today that takes about 12.8 seconds. Alpenglow targets roughly 150 milliseconds, and the word "targets" is doing real work: nothing has activated on mainnet yet, so there is no measured number to compare against the projection.

The two clocks are easy to confuse. The 150ms is how long a transaction takes to become final, not how often blocks are produced. Solana cut block time separately, through reduced slot times that went from 400ms to 200ms across four stages completed in October 2026.

The everyday version: a merchant waiting for finality before it accepts a payment, or a bridge waiting before it releases funds on another chain, currently sits through almost 13 seconds for that assurance. That wait is the thing being cut.

Votes Leave the Blocks

Today validators vote by posting transactions, and a block counts as final only once enough of those votes have stacked up over 32 slots. Alpenglow replaces that layer entirely. Validators message each other directly, bundle their votes into certificates, and a block is final after one or two rounds.

One consequence will be visible to anyone who watches a Solana explorer. Vote transactions leave blocks, so headline transaction counts and TPS figures drop sharply without any drop in real activity. Solana is telling indexers to re-baseline their transaction and TPS dashboards, so don't read that fall as a fall in usage.

Votor Finalizes in One Round, or Two at Most

Votor is the voting protocol that ships with Alpenglow, and it comes in Agave 4.3. SIMD-0326, the proposal behind the change, lays out both paths. Fast finalization means one round of votes from 80% of stake, which locks in a block on the spot. If support lands between 60% and 80%, a second round with 60% thresholds decides whether the block is finalized or skipped. The design is meant to tolerate 20% malicious stake plus another 20% offline.

The proposal doesn't hide the tradeoff. Alpenglow gives up the 33% byzantine security that two-round voting can reach, and its authors argue that one-round voting plus 40% crash-failure resilience is worth it. It also caps participation at the 2,000 highest staked validators.

What Validators Must Do Before Epoch 1064

The migration comes with real conditions attached. Validators need to be on an Agave-based client, which means Agave, Jito-Solana or Harmonic Salsa, running a release built on Agave 4.3.0. Firedancer and Frankendancer are not supported during the migration.

They also need at least 0.8 SOL in the vote account above its rent-exempt minimum. That balance pays the Validator Admission Ticket, first charged as epoch 1064 begins and covering epoch 1065. A validator that can't cover it doesn't vote or produce blocks in the next epoch. SIMD-0326 describes the fee as 80% of what vote transactions cost today, initially about 0.8 SOL a day, or 1.6 SOL an epoch, and says the whole fee is burned. It replaces the roughly 1 SOL an epoch validators spend on vote fees now.

The handover isn't instant. Solana keeps the old voting system running for the first 5,000 slots after the feature gate opens, roughly 18 minutes, before Alpenglow takes control.

For developers, the "confirmed" and "finalized" commitment levels become one and the same. Solana's advice is not to point new code at finalized until Alpenglow is live, because on TowerBFT finalized still means a 12.8-second wait.

Rotor Comes Later, With No Date Set

October 21 delivers only Votor, the first half of the upgrade. Rotor replaces Turbine, the protocol that spreads a block's data across the network, with a single relay layer. It's planned for a later release once Votor is adopted, and it still isn't scheduled. SIMD-0326 makes the same split: it says the design initially stays with Turbine, and Rotor will get its own proposal.

Devnet went first, activating Alpenglow in epoch 1167 at 19:30 UTC on September 25, 2026. Solana's page lists testnet and devnet as active and mainnet as not activated.

The date to watch is October 21. The more useful thing to watch after it is the first real mainnet finality number, since that's the one figure in this whole upgrade that nobody has yet.