Someone on the Ethereum Research forum has proposed letting validators vote to send a fraction of their staking rewards into a public goods fund. The ceiling is 10%, but validators would choose whether to participate and how much to contribute. The idea: use the protocol's own yield stream to finance infrastructure development without issuing new tokens or tapping the treasury.
The proposal hinges on one key mechanic. Staking rewards accrue continuously as validators produce blocks and attest to the chain. A redirect would siphon a portion into a separate fund before rewards hit validator accounts. Governance would decide which projects get funded and how much each receives. The opt-in design means validators unhappy with the fund's allocation can simply skip the redirect and pocket their full yield.
What makes this thorny: staking yield is the primary reason many operators run validators in the first place. Ethereum currently has around 32 million ETH staked. Even a 1% or 2% redirect—far below the 10% cap—would compress returns enough to matter for validators operating on tight margins. Smaller operators might feel the pressure to exit; larger ones might absorb it as a cost of participation. The real question isn't whether the mechanism works, but whether enough validators stay if their economics shift.
There's a second-order problem baked in. A validator-controlled fund introduces new governance surface. Who decides which projects qualify? How do you prevent the fund from becoming a capture target for well-connected teams? Ethereum's existing treasury, which holds protocol-owned assets, already grapples with these tensions. Adding a second stream funded by ongoing yields rather than one-time allocations could amplify them.
The forum discussion touches on whether this setup actually strengthens Ethereum's base layer or shifts capital away from security-critical work toward developer tooling and networking perks. One framing: a tax on the people securing the network to fund the people building on top of it. Another: a sustainable way to fund work the market otherwise wouldn't pay for. Both are defensible, and the tension between them isn't new.
Implementing this would require a consensus change—essentially a soft fork or protocol upgrade—plus months of discussion about fund governance and what counts as a qualifying project. Ethereum's upgrade cycle is already crowded with competing priorities. Even if the proposal gains traction, execution could drift.
The core appeal is simple: Ethereum's yields could fund its own ecosystem without leaning on VC capital or token mints. The core risk is equally plain: validators might defect if they judge the yield compression not worth the governance upside, or if they lose confidence in how the fund allocates capital.