Solana rolls out Alpenglow testnet as SOL nears January highs
Solana has begun rolling Alpenglow to testnet, introducing Votor for faster finality as SOL trades near late-January price levels.
Solana has started rolling the Alpenglow consensus upgrade onto testnet, beginning a staged public deployment intended to replace the current TowerBFT consensus. The first phase introduces Votor, which moves validator votes off-chain so validators send votes directly to each other and aggregate them into certificates that can finalize a block in one or two voting rounds. Finality is expected near 150 milliseconds, down from about 12.8 seconds under TowerBFT.
The upgrade does not change the Solana Virtual Machine, transaction formats, programs or the fee structure. A later component called Rotor is planned to replace Turbine, the network’s block-distribution layer; Rotor will be scheduled separately. Validators and infrastructure providers must update systems that stream blocks, track votes or rely on existing commitment indicators to maintain compatibility.
Solana activated Transaction V1 earlier this month, increasing maximum transaction size to 4,096 bytes from 1,232 bytes. The network’s slot-time roadmap has reduced target slot lengths from 400 milliseconds to a 200-millisecond target. These changes are designed to support larger transactions and lower settlement latency.
Market activity has risen in parallel. SOL traded near $117–$120 this week, up roughly 25% over the past month, with a market capitalization around $67 billion. On-chain figures show tokenized real-world assets on Solana at about $4.6 billion in early September. Decentralized exchanges on the chain recorded about 208 million spot trades in the week ending Sept. 13, compared with roughly 190 million on the New York Stock Exchange; Jupiter accounted for more than 80 million trades during September.
An investor expects SOL’s market capitalization to surpass Ethereum’s in the current market cycle, citing developer activity and recent fee levels. Testnet will expand to devnet and, if operational stability and compatibility are confirmed by validators and infrastructure providers, advance to mainnet-beta.








