Solana has set Oct. 21 for Alpenglow, a network upgrade that aims to make transactions irreversible in roughly 150 milliseconds. The Solana Foundation published the timetable. It is the biggest change to how the chain reaches consensus since launch.

The target number deserves a caveat. Actual finality will depend on network conditions, according to the Foundation's schedule. The 150-millisecond figure is a goal, not a guarantee.

Alpenglow will replace TowerBFT, the validator voting system Solana has run since 2020. Today, validators submit votes as ordinary transactions recorded on the blockchain. Under Alpenglow, they will exchange votes directly and bundle enough approvals into a certificate that finalizes a block after one or two voting rounds.

A Solana payment already looks successful almost instantly. What it lacks today is the hard guarantee that it cannot be undone. Alpenglow closes that gap. A merchant waiting for certainty before accepting a payment, or a bridge before releasing funds on another chain, could act within a fraction of a second.

What happens to the transaction count?

Here is the odd part. Solana's headline transaction count may fall sharply on activation day, even if user activity stays flat. The reason is mechanical: validator votes, which currently fill blocks as transactions, will move off-chain. Dashboard numbers will drop. Real usage will not.

Anyone tracking Solana's throughput metrics should treat the post-upgrade figures as a new baseline rather than a collapse in demand.

What must validators do?

Operators face concrete migration requirements:

• Validators must run software built on Agave 4.3.0 for the transition.
• Firedancer and Frankendancer clients will not support the initial migration, forcing their operators to switch software temporarily.

The economics of running a validator shift too. Current voting charges run roughly 1 SOL per epoch. Those disappear. A flat admission fee of 0.8 SOL replaces them. An epoch is the period during which Solana assigns validators their network responsibilities.

The clock on activation day

The migration is scheduled for epoch 1064, expected to begin around 15:00 UTC on Oct. 21. Solana will keep its old voting system for the first 5,000 slots, the short block-production windows, before switching to Alpenglow roughly 18 minutes into the epoch.

What does this change for builders? Payment flows and cross-chain bridges that currently wait through confirmation delays can compress their settlement logic down to near-instant finality, assuming the network hits its target.

For now, the deadline is fixed. Validators running non-compliant clients have until epoch 1064 to move, or risk falling out of consensus when the switch lands.