Solana Alpenglow Consensus Proposal Enters Community Voting Stage, Here’s The Big Catch
The post Solana Alpenglow Consensus Proposal Enters Community Voting Stage, Here’s The Big Catch appeared on BitcoinEthereumNews.com.
Solana Alpenglow consensus proposal entered its community voting phase this week. This marked a major step toward replacing the current TowerBFT system with a faster and more resilient model. The upgrade also introduced Rotor, a new block propagation method, with possible benefits for DApps and token value. Solana Community Voting Process and Key Features Notably, the Alpenglow proposal went to a community vote stage starting in epoch 840, with ballots set to close at the end of epoch 842. Before the voting began, stake weights were recorded and published in epoch 839. Validators could then claim voting tokens linked to their stake and direct them toward one of three options: Yes, No, or Abstain. Also, for the proposal to pass, Yes votes needed to equal or exceed two-thirds of Yes plus No votes with abstentions still counting toward the quorum. The minimum quorum was 33% of the total stake weight. Alpenglow was designed to replace Proof-of-History and TowerBFT with a new structure focused on speed and reliability. This is a very important feature, considering the growing clamor for spot Solana ETFs. The central element of the proposal was Rotor, a voting system that finalized blocks either in one or two rounds. If 80% of validators participated, blocks could be finalized in one round, bringing confirmation times down to 100–150 milliseconds. The new framework also included a Validator Admission Ticket, or VAT. This was a fixed fee of 1.6 SOL paid at each epoch by validators. The fee was burned rather than redistributed, ensuring it did not re-enter circulation. The VAT was introduced to keep an economic barrier in place since voting would no longer happen on-chain. Leaders in each round were also compensated for submitting aggregated vote data and finalization certificates. These changes aimed to reduce network overhead by shifting…
Filed under: News - @ August 17, 2025 10:20 pm