What is Solana’s Alpenglow and What Does it Mean for Institutional SOL Staking?

By:
Conor
Keville
&

Learn what Solana’s Alpenglow upgrade and Validator Admission Ticket could mean for institutional SOL staking rewards.

As mentioned in a previous blog, Alpenglow is Solana’s next major consensus protocol upgrade, designed to reduce consensus finality times and change how validators coordinate votes.

For institutional SOL stakers and delegators, the most important question is not only what Alpenglow changes technically, but whether those changes could affect staking rewards. The short answer is: not directly at the protocol level. Alpenglow’s proposed Validator Admission Ticket, or VAT, is charged to validators rather than deducted from delegator rewards. However, it does change validator cost accounting, which may matter indirectly over time.

This blog explains what Alpenglow changes, how VAT works, and what institutional stakers should understand about the potential reward implications.

What is Alpenglow?

Alpenglow is Solana’s proposed consensus upgrade, formalized in SIMD-0326. It is designed to replace Proof-of-History and TowerBFT with Votor, a direct-vote finality protocol. The target is consensus finality as low as roughly 100-150ms, compared with about 12.8 seconds under TowerBFT.  

A key economic change proposed alongside Alpenglow is the Validator Admission Ticket, or VAT. VAT is a fee charged once per epoch to validators eligible to participate in the next epoch’s consensus set. The current SIMD-0357 proposal sets VAT at 1.6 SOL per epoch. If a validator’s vote account lacks enough SOL to cover VAT and required rent, the validator is filtered out of the eligible validator set.  

What changes with validator voting?

Today, Solana validators pay vote transaction fees because consensus votes are submitted as on-chain transactions. Validators are expected to send vote transactions as they participate in consensus, and those transactions are paid from the validator identity account. Like other Solana transactions, vote transactions pay a base fee per signature. Solana’s base fee is 5,000 lamports, or 0.000005 SOL, per signature.  

Because validators vote continuously across an epoch, these small per-vote fees become a recurring validator cost. A standard epoch is 432,000 slots; if a validator voted once per slot, the implied cost would be 2.16 SOL per epoch before accounting for missed votes, epoch timing, or runtime variation. SIMD-0357 rounds the current voting cost to approximately 2 SOL per epoch for validators that vote most of the time.  

Alpenglow changes this model by moving validator votes out of the on-chain transaction path. Instead of being posted as regular vote transactions, votes are exchanged directly between validators as part of Votor. This reduces vote-related transaction overhead. Alpenglow’s core performance goal is faster finality; the removal of on-chain vote traffic is a related efficiency change, not a guarantee of higher application-level throughput.

VAT replaces today’s recurring vote transaction fees with a fixed epoch-level validator cost.

Why is VAT burned?

Under SIMD-0357, VAT is deducted from the validator’s vote account and moved to the incinerator account. That means SOL paid through VAT is burned rather than paid to another validator, distributed to delegators, or recycled through a reward pool.  

The burn matters because VAT is not a new reward stream. It is better understood as a replacement participation cost for validators after on-chain vote transaction fees are removed.

For institutional stakers, VAT is not designed as a direct reduction to delegator rewards. It is a validator-level fee that changes how participation costs are paid. Instead of many small vote transaction fees, the proposal introduces a fixed cost once per epoch. How material that cost is will depend on a validator’s broader economics, including delegated stake, commission, block-production revenue, reward-sharing terms, infrastructure costs, and operational performance.

Will VAT affect SOL staking rewards?

VAT does not directly reduce delegator rewards at the protocol level. The fee is charged to the validator’s vote account, not deducted from delegator rewards.

The effect is therefore indirect. VAT changes validator cost accounting by replacing recurring vote transaction fees with a fixed epoch-level fee. Because the proposed 1.6 SOL VAT is lower than the current rounded estimate of roughly 2 SOL per epoch in vote transaction fees for validators that vote most of the time, it may not increase direct protocol costs for many consistently participating validators.  

However, the impact will not be identical for every validator. Validators differ by stake size, commission, block-production revenue, reward-sharing terms, infrastructure costs, and operational performance. 

For institutional stakers and delegators, the main point is the distinction between direct and indirect impact. VAT is not a protocol-level delegator reward cut. Any impact on staking rewards would likely come indirectly through validator-level decisions, such as commission or reward-sharing policy, rather than through a direct deduction from delegator rewards.

Conclusion

Alpenglow is a major Solana upgrade still under development. Its primary goal is faster consensus finality through Votor, while VAT addresses the validator-cost side of removing on-chain vote transactions.

Under the current proposal, VAT would replace recurring vote transaction fees with a fixed validator fee of 1.6 SOL per epoch. That fee would be burned. For institutional stakers, the important distinction is direct versus indirect impact. VAT is not deducted from delegator rewards, but it may influence validator economics over time.

The final impact will depend on the implemented VAT design, validator cost structures, commission policies, delegated stake, block-production revenue, and reward-sharing terms.

Share

Get Started with
Blockdaemon Today!

Contact us to learn how we can help you power your blockchain business.

Unparalleled Security & Compliance
Seamless Integration & Scalability
Dedicated Customer Support