Ethereum's New Proposal Suggests Validators Allocate Up to 10% of Staking Rewards for Ecosystem Development, Annually or Upon Accumulating Over 70,000 ETH

On June 22, the Ethereum Research Forum unveiled a new governance proposal called "Validator Redirected Revenue," which would let validators shift between 0% and 10% of their staking rewards toward funding development tools, security research, public infrastructure, and other ecosystem public goods. Under the proposal, validators would first voluntarily signal the percentage of rewards they’re willing to contribute. If more than half of all validators back a non-zero contribution rate, the mechanism would apply to every validator. Nodes can also name specific fund recipients, and the money would flow automatically via a dedicated allocation smart contract. The Ethereum ecosystem currently grapples with the so-called "free-rider problem": countless projects rely on public infrastructure, research, and security work but have no consistent way to fund these efforts. As long-term ETH holders, validators should shoulder a share of the costs of Ethereum’s growth. Current data puts Ethereum validators’ annual staking rewards at roughly 700,000 ETH. If a 5% to 10% contribution rate is eventually approved, some 50,000 to 70,000 ETH would go toward ecosystem support each year—worth roughly $1.2 billion at today’s prices. But the proposal has already sparked debate. Critics worry that validator alliances could coordinate to direct funds to favored groups. What’s more, a huge chunk of ETH is staked by third parties like crypto exchanges and liquid staking platforms—meaning delegators, not the institutional node operators running validators, would end up taking the hit to rewards. This creates what’s known as a "decision-maker/payer misalignment" problem. Other critics argue that if validators are ready to give up some rewards, Ethereum could simply cut back on ETH issuance directly instead of setting up a new fund distribution system. Right now, the proposal is still being hashed out in community discussions and hasn’t moved to a formal vote yet.