A new Ethereum draft proposes charging validators when their total number remains above a target. The author says it could encourage operators with multiple validators to combine stake into fewer entries and reduce the work Ethereum needs to reach finality.
According to the Ethereum draft, the draft, posted on November 18 to a forum used by Ethereum developers, describes a deduction that would vary with both the validator count and the size of each validator’s stake. A validator with 32 ETH would face the largest deduction under the formula. The charge would fall to zero at an effective balance of 2,048 ETH.
How the Ethereum validator consolidation draft would work
The proposal would start with a target validator count. That target would fall on a schedule until it reaches a lower level, then stay there. When the active count sits above the target, the proposed deduction increases as Ethereum moves from one epoch to the next. An epoch is a recurring span of blocks that the network uses to organize validator duties.
A larger gap between the actual count and the target would make the charge rise faster. If the actual count falls below the target, the charge would drop toward zero at ten times the rate specified for increases. If operators consolidate quickly enough to keep pace with the target, the author says the deduction would stay at zero.
The author links the idea to the work the network does to finalize blocks. Validators cast votes on the chain, and an expanded set means the protocol has more validator entries to account for. The draft aims to lower that count without using the total amount of ETH staked as its target.
What the draft could mean for 32 ETH validators
The size of the deduction would depend on a validator’s effective balance, the amount the protocol uses for its calculations. The author proposes the largest deduction at 32 ETH, capped at that validator’s full attestation reward. From there it would fall in a straight line as effective balances rise.
The existing EIP-7251 specification allows larger effective balances while keeping 32 ETH as the lower bound. That gives operators who control several eligible validators an option to consolidate. A solo operator who has 32 ETH in a single validator has to consider the proposal from a different starting point, since there is no second validator under that operator’s control to combine.
The open question for review is how those incentives would affect operators of different sizes. A large operator could consolidate several validator entries, while an operator with one minimum-size validator might need to add stake to reduce the proposed charge. The target, the rate at which the deduction moves and the balance formula all affect that trade-off.
The discussion post presents a draft protocol change. The proposed deduction has no activation date in the post. Review of the draft and its parameters is the next milestone to watch before anyone can assess the practical effect on validator rewards.
