Doctorcrypto About RSS Subscribe
Doctorcrypto
HomeOpinion › Ethereum Proposal Would Burn Staking Rewards to Zero if Half of ETH Is Staked
Opinion

Ethereum Proposal Would Burn Staking Rewards to Zero if Half of ETH Is Staked

By Priya Chen · · 1 min read

A new Ethereum proposal is aiming to cap how much of the network's supply gets locked away in staking by gradually eliminating rewards once half of all ETH is committed to securing the chain.

What the Proposal Suggests

The idea centers on a mechanism that would drive staking yields toward zero if the amount of staked ETH reaches 50% of the total supply. Under the plan, the financial incentive to stake beyond that threshold would vanish at the point of activation, discouraging further growth in the staking ratio.

Rather than flipping the change on all at once, the proposal calls for a gradual rollout. The reduction in yield would phase in over an 18-month window, giving stakers and validators time to adjust their strategies as the payout structure shifts.

Once half the supply is staked, the reward for locking up more ETH would effectively disappear.

Why It Matters

Ethereum's shift to proof-of-stake has spurred ongoing debate about the ideal proportion of the supply that should be staked. Too much ETH locked into staking can reduce the amount circulating for everyday use, decentralized finance, and other on-chain activity, potentially concentrating influence among large staking operators.

By tying rewards to the staking ratio, the proposal seeks to create a natural ceiling that balances network security against liquidity and broader participation in the ecosystem. The measured 18-month phase-in is designed to avoid shocking the market or destabilizing validator economics.

Key features of the proposal include:

  • A target threshold at 50% of total ETH supply staked
  • Staking rewards trending toward zero beyond that point
  • A gradual 18-month implementation timeline

As with any Ethereum change, the concept would need to move through community discussion and developer review before it could be considered for adoption on the network.

Was this useful?👍 Yes👎 No