Invest2 publishers2 min readPublished Updated
Alpenglow cuts finality on Solana's test networks from 12.8 seconds to about 150 milliseconds
Anza moved Solana's testnet and devnet to Alpenglow on Sept. 24 and 25, cutting finality from about 12.8 seconds to a 100 to 150 millisecond target. Mainnet-beta follows an observation period with no date set, the window exchanges and app teams have to retest what they count as settled.
The Investor · Invest desk
What happened
- Validator votes on Solana's testnet and devnet now travel off-chain instead of riding as ordinary transactions packed into blocks.
- Each cutover opened a feature gate at an epoch boundary, ran a 5,000-slot countdown of about 17 minutes, and needed 82 percent of stake to confirm a final TowerBFT block.
- Rotor, a later part of the Alpenglow design, is scheduled separately and does not change how blocks propagate in this first phase.
- Solana Foundation engineer Ilan Gitter cited more than 25,000 transactions per second with 150-millisecond finality on testnet, a figure from a test environment.
Compiled by The InvestorSomething wrong?How this is made
Why it matters
- decision Exchanges, bridges and liquidation engines that now wait out a 12.8-second settlement have to decide whether one Votor certificate is enough to act on, and devnet is where they can rehearse that choice.
- constraint Because the Foundation ties the 150-millisecond figure to a stake map, a custodian cannot promise it as a fixed settlement time across regions or at peak load.
- exposure A mainnet-beta switch before Firedancer or Frankendancer supports Votor would leave finality on the chain that holds user funds dependent on the Agave client alone.
TowerBFT produced irreversible settlement on the order of 12.8 seconds [7]. Votor's fast path aims for roughly 100 milliseconds when a large share of stake agrees in a single round, and its second path aims for about 150 milliseconds when another round is needed [8]. Divide the old figure by each target and the fast path is 128 times quicker, the slower one about 85 times [1]. The Solana Foundation's own upgrade materials describe the 150-millisecond number as an expectation measured against a given stake map, not a constant that will hold in every geography or under every load [9].
Anza is changing how long a transaction stays reversible and leaving what it costs alone. Execution, programs and fees are intended to stay the same [10].
The testing work falls on application teams first. Devnet is where most programs are exercised with valueless tokens [17], and Anza's devnet post told developers to "test your programs and integrations now during our observation period leading up to mainnet-beta migration" [12]. According to Crowdfund Insider, millisecond settlement would change how wallets, exchanges, bridges and liquidation engines treat confirmation [18]. Operators will watch whether "confirmed" and "finalized" can safely collapse into one state [16].
Solana co-founder Anatoly Yakovenko answered Anza's devnet countdown with five words: "You are not ready for this." [14] The same account says the speeds remain largely unproven under full mainnet conditions [19].
If the observation window closes cleanly, mainnet-beta could cross on Agave alone, the client both public migrations leaned on because Firedancer and Frankendancer still lacked Votor support [15]. The window could also stretch while those clients catch up. Or finality could come in slower once real balances, real latency and a full validator set are involved, the conditions under which hidden assumptions surface [20].
I think the mainnet date will be set by client support more than by latency. Anza's sequencing puts mainnet-beta after an observation period with no live-network date attached [6], and client diversity is on the list operators will watch [16]. The counter-case is that Anza has already taken two public clusters through the handoff leaning on Agave [15] and could do the same with the third. A mainnet-beta date announced before Firedancer supports Votor would prove this view wrong.
What to watch
- Anza naming a mainnet-beta date, and whether it lands before Firedancer or Frankendancer ships Votor support.
- Measured finality on mainnet-beta across the full validator set, set against the 100 and 150 millisecond targets.
- Whether exchanges and bridges cut deposit confirmation to a single Votor certificate during or after the observation window.