Solana recently moved its Alpenglow consensus upgrade closer to public testnet deployment as developers prepare to test a major change to transaction finality. The design aims to reduce finality from approximately 13 seconds to 150 milliseconds. Testing will first take place across Solana’s established public testnet before developers consider activation on the main network.
The testnet stage gives developers a wider environment for evaluating migration procedures and network behavior. It also allows infrastructure providers and validators to assess how the new consensus system performs under broader participation.
Finality marks the point when the network considers a transaction irreversible. Exchanges can use finality before crediting deposits. Blockchain bridges also depend on it before releasing assets onto another network.
Solana currently uses TowerBFT, which requires validators to record consensus votes on-chain. Validators build enough votes across 32 slots before a block reaches finality.
Alpenglow changes this process through a protocol called Votor. Instead of relying on the same sequence of on-chain consensus votes, Votor allows validators to exchange votes directly.
The system can reach agreement through one or two voting rounds. Earlier specifications showed that one round can finalize a block when enough validator stake participates. A second round provides another route when participation falls below this level.
The design could sharply shorten the time between block production and irreversible settlement. Anza has estimated median finality near 150 milliseconds. Earlier simulations reached about 100 milliseconds under favorable conditions.
Applications would continue processing transactions through the same general interfaces. Wallet users would also continue submitting transactions as they do today. The key changes occur in validator communication and consensus.
Alpenglow has already operated for more than four months on a smaller community cluster. Developers created the environment specifically for consensus testing before expanding the rollout.
Also Read: Bitcoin, Ethereum, Solana Face Different Catalysts
Moving Alpenglow into Solana’s established public testnet brings more validators and infrastructure services into the testing process. This environment already supports a wider set of network participants.
The testnet uses tokens without monetary value. As a result, developers can restart the network, examine failures, and test migration procedures without placing mainnet assets at risk. Anza first moved Alpenglow into community validator testing in May. At the time, it described the project as the largest consensus change in Solana’s history.
Validators joining the Alpenglow test need Agave 4.3, the latest branch of Anza’s main validator software. The Alpenglow rollout has remained closely tied to Agave development for several months.
Anza recommended Agave 4.3 for broader mainnet validator adoption on September 21. Earlier stages first targeted operators representing 10% of mainnet stake. The recommendation later expanded to 25%.
The underlying Alpenglow code had already entered an earlier software branch for testing. By August, developers expected the targeted 150 millisecond finality improvement to arrive through Agave 4.3.
Anza’s Agave 4.3 schedule lists September 28 as the tentative date for resuming mainnet feature activation. The schedule remains subject to change.
The date does not confirm Alpenglow activation on Solana mainnet. Anza’s feature gate tracker still listed Alpenglow testnet activation as pending early Wednesday.
This distinction matters because Solana is pursuing several performance upgrades through separate activation processes. Finality, slot production, and transaction capacity measure different aspects of network performance.
Solana recently reduced its target slot time from 300 milliseconds to 250 milliseconds through SIMD-0525. The change brought the network to a target rate of four slots per second.
The upgrade also shortened each validator’s four-slot leader window from 1.2 seconds to one second. Network processing limits changed alongside the shorter slots, so transaction capacity did not rise by the same proportion.
SIMD-0525 ultimately targets 200 millisecond slots, or five targeted slots per second. Developers have not announced a confirmed mainnet activation date for the stage. Solana started the current slot reduction sequence in August, when its target dropped from 400 milliseconds to 350 milliseconds. The roadmap then moved through 300 and 250 milliseconds.
Alpenglow follows a separate process through SIMD-0326. Rather than shortening slots, it replaces TowerBFT with Votor and changes how validators agree that blocks have reached finality.