Solana’s Alpenglow Goes Live Oct. 21: TowerBFT Out, ~150 ms Finality Target In, and Why TPS Charts Are About to “Crash”

Not financial advice. This article is for informational purposes only.

Solana is about to replace the consensus system it has run since 2020. According to the Solana Foundation, Alpenglow activates on mainnet in epoch 1064, which is expected to start at approximately 15:00 UTC on Wednesday, Oct. 21, 2026. The network keeps running TowerBFT for the first 5,000 slots of that epoch, and Alpenglow takes over at slot 459,653,000 about 18 minutes later. The headline target is finality in roughly 150 milliseconds, down from about 12.8 seconds today. Validators must run Agave, Jito-Solana, or Harmonic Salsa built on Agave 4.3.0, and Anza named Agave v4.3.2 its recommended release on Oct. 16. Firedancer isn’t supported for the migration. Traders should also expect transaction-count dashboards to drop sharply.

The switch: track the epoch, not the clock

• Feature gate: A1pengvuM6JEcyNuTnMqepBKhwHE3N6PmUrdATGawhJS, activating at the start of epoch 1064
• TowerBFT tail: the first 5,000 slots of the epoch, about 18 minutes
• Alpenglow takeover: slot 459,653,000

Epoch start times drift with slot timing, so 15:00 UTC is an estimate. Anza’s own Oct. 13 post put the start at about 14:50 UTC. Every operator deadline is the start of epoch 1064. Alpenglow has been running on devnet since epoch 1167 (Sept. 25, 2026).

What changes in phase one (Votor)

• Votes stop being transactions. Validators send votes directly to each other and aggregate them into BLS certificates. A block can be finalized in one round if at least 80% of stake votes to notarize it. Otherwise a second round uses 60% stake thresholds.
• confirmed and finalized become the same thing. The Solana Foundation advises developers not to switch to finalized until Alpenglow is live. confirmed will be removed in a later release.
• Proof of History stops pacing block production. Tick entries leave the shred stream. The leader now sets Clock.unix_timestamp within a bounded range, instead of it being a stake-weighted median of vote timestamps.
• Execution doesn’t change. The SVM, transaction formats, programs, and fees stay the same.

The 150 ms figure is a target, not a guarantee. The Solana Foundation calls it “an expectation, not a constant” that depends on stake distribution and on whether a block finalizes in one round or two. Phase two, Rotor, will replace Turbine for block propagation. It is planned for later and hasn’t been scheduled.

The client situation

• Agave 4.3.0 is the minimum. Anza posted on Oct. 16: “Agave v4.3.2 is the recommended version for all validators. Upgrade now.”
• Firedancer v26.10.2 (released Oct. 14) adds Alpenglow support, and its release notes cite lower memory use (183 GiB to 159 GiB) and faster snapshot loading (about 40 seconds). However, Firedancer and Frankendancer can’t perform the Tower-to-Alpenglow migration. Validators running them must switch to an Agave-based client before activation.

Validator economics: the Validator Admission Ticket

Under TowerBFT, voting costs about 1 SOL per epoch in vote-transaction fees, paid from the identity account. Under Alpenglow, the Validator Admission Ticket (VAT, SIMD-0357) charges each voting validator a flat 0.8 SOL per epoch. It is taken from the vote account, above that account’s rent-exempt minimum, and burned. The first fee is charged at the start of epoch 1064 and pays for epoch 1065. If a vote account can’t pay, that validator doesn’t vote or produce blocks in the next epoch.

Why it matters for traders and developers

• Near-instant finality helps DEX settlement and point-of-sale confirmations.
• Indexers, bots, and routers that count ticks or vote transactions have to adapt. Geyser/gRPC consumers should buffer per (slot, bank_id).
• Reported TPS will fall because vote transactions disappear from blocks, not because real activity dropped. Expect some “Solana activity collapses” charts from tools that haven’t re-baselined.

How to verify it actually happened

Call the new getAgGenesisCert RPC method, or run solana alpenglow-genesis-info (both need v4.3). It returns null while the cluster is still on TowerBFT and returns the Alpenglow genesis certificate once the cluster has migrated. Don’t rely on the date. Check the cluster.

Sources

• Solana Foundation, Alpenglow upgrade page (updated Oct. 2026)
• Anza on X, Agave v4.3.2 recommended (Oct. 16, 2026) and activation timing post (Oct. 13, 2026)
• Anza, Agave releases on GitHub
• Firedancer, v26.10.2 release notes (Oct. 14, 2026)
• CoinDesk, “Solana sets Oct. 21 for Alpenglow upgrade” (Oct. 14, 2026)

Not financial advice. This article is for informational purposes only.