Solana plans to implement its most aggressive network upgrade since its inception in 2026. This plan involves comprehensive system overhauls, from the underlying consensus mechanism to upper-layer infrastructure. The core goal is clear—create an on-chain environment at the level of centralized exchanges, enabling native centralized limit order books (CLOB) to compete directly with centralized exchanges (CEX) in terms of latency, liquidity, and fairness.
The most notable aspect of this upgrade plan is Alpenglow, a major protocol-level change.
**Thorough Reconstruction of the Consensus Mechanism**
Alpenglow breaks away from traditional validation processes. Previously, multiple rounds of voting were conducted sequentially. The new architecture allows validators to aggregate voting data off-chain and finalize the confirmation within one or two rounds. The immediate effect of this change is a reduction in the theoretical final confirmation time from 12.8 seconds to 100-150 milliseconds.
The cleverness of this new system lies in its dual-path design. The first path: if a block’s stake support exceeds 80%, it is accepted directly without waiting. The second path: if support is between 60% and 80%, a second round of voting is triggered. As long as the support in the second round remains above 60%, the block can be anchored. This mechanism ensures network security while significantly improving confirmation efficiency.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
13 Likes
Reward
13
8
Repost
Share
Comment
0/400
ContractHunter
· 38m ago
100 milliseconds? You're here bragging to me, CEX still needs to worry about Solana?
View OriginalReply0
MissedTheBoat
· 8h ago
100-150 milliseconds? If that's really achievable, what's the point of CEX anymore, haha
View OriginalReply0
LoneValidator
· 13h ago
100 milliseconds confirmation? Directly surpassing CEX, Solana is really about to take off
View OriginalReply0
DefiEngineerJack
· 01-21 11:54
well, *actually* if you're compressing finality to 100-150ms with just a dual-path consensus... have you formally verified this doesn't introduce liveness issues under Byzantine conditions? because 60% threshold on round two sounds empirically risky ngl
Reply0
BlockchainArchaeologist
· 01-21 11:50
100 milliseconds? If that really becomes practical, CEXs might be trembling in fear.
View OriginalReply0
GateUser-75ee51e7
· 01-21 11:44
100-150 milliseconds? If it can really stay stable, I would believe it. There have been quite a few promises before.
View OriginalReply0
GweiWatcher
· 01-21 11:36
100 milliseconds? Folks, this time CEX really has to panic
View OriginalReply0
RuntimeError
· 01-21 11:34
100-150 milliseconds? Really? If it could run stably, CEXs would be crying to death.
Solana plans to implement its most aggressive network upgrade since its inception in 2026. This plan involves comprehensive system overhauls, from the underlying consensus mechanism to upper-layer infrastructure. The core goal is clear—create an on-chain environment at the level of centralized exchanges, enabling native centralized limit order books (CLOB) to compete directly with centralized exchanges (CEX) in terms of latency, liquidity, and fairness.
The most notable aspect of this upgrade plan is Alpenglow, a major protocol-level change.
**Thorough Reconstruction of the Consensus Mechanism**
Alpenglow breaks away from traditional validation processes. Previously, multiple rounds of voting were conducted sequentially. The new architecture allows validators to aggregate voting data off-chain and finalize the confirmation within one or two rounds. The immediate effect of this change is a reduction in the theoretical final confirmation time from 12.8 seconds to 100-150 milliseconds.
The cleverness of this new system lies in its dual-path design. The first path: if a block’s stake support exceeds 80%, it is accepted directly without waiting. The second path: if support is between 60% and 80%, a second round of voting is triggered. As long as the support in the second round remains above 60%, the block can be anchored. This mechanism ensures network security while significantly improving confirmation efficiency.