EIP-8071 Preventing withdrawal abuse of validator consolidation (Prevent using consolidations as withdrawals)

No call decision · Consensus & staking · EIP status Draft · created 2025-10-29

If processing a validator consolidation request would push the target validator's balance above the maximum effective balance, the request is cancelled. This blocks the abuse of using the consolidation queue as a withdrawal shortcut.

Why it is needed

Ethereum has a consolidation feature that merges two validators into one. Under the existing design, even if the target validator's balance exceeds the cap, the maximum effective balance, after consolidation, the request is still processed and the excess is automatically withdrawn. So when the exit queue for withdrawals is long and the consolidation queue is short, a workaround emerges that lets funds be pulled out faster through consolidation instead of the formal exit process. The source states that at the time of writing, this loophole was being heavily abused in practice, and that public posts exist explaining how to use it to speed up withdrawals. The source explains that although this is more a usability (UX) issue than a security incident, the consolidation queue was never designed for withdrawal purposes, so a fix blocking this is important.

What changes

Today

After EIP-8071

Who is affected

In depth

Background: why the consolidation queue became a withdrawal shortcut

Consolidation is a feature that moves the source validator's balance to the target validator. Under the existing design, even if the target's balance exceeds the maximum effective balance after consolidation, the request is still processed as is and the excess balance exits as a withdrawal. When the exit queue and consolidation queue speeds are imbalanced and the consolidation side is faster, this property becomes a means of accelerating withdrawals. The source states that at the time of writing, this flaw was being heavily abused, and that public documents exist covering how to use this vulnerability to speed up withdrawals. However, while classifying this as a UX issue rather than a security problem, it explains that since the consolidation queue was not built for withdrawal purposes, this fix is an important change.

New check: cancel if the post-consolidation balance exceeds the cap

The modified process_consolidation_request performs a new check last, after passing all the existing validations. It computes target_balance_after_consolidation as get_pending_balance_to_consolidate(state, target_index) + source_validator.effective_balance + state.balances[target_index], and if this value exceeds get_max_effective_balance(target_validator), the function returns as is and the request is cancelled. This structure only lets consolidation go through when the entire incoming balance becomes active balance, and does not accept it when it would produce an excess that gets withdrawn. From the start of the epoch in which this EIP activates, consensus layer clients MUST use the modified function.

get_pending_balance_to_consolidate and blocking the split workaround

The new helper function get_pending_balance_to_consolidate iterates over state.pending_consolidations and returns the sum of the effective balances of the source validators of pending consolidations that share the same target_index. The reason for this is to catch cases where multiple consolidations are sent to the same target that individually stay under the cap but exceed it when combined. The source's Rationale acknowledges that this design of iterating over pending consolidations increases the complexity of consolidation processing, but explains that it is necessary to handle exactly this multiple-consolidation case.

The existing validation steps remain unchanged

All existing validations before the new check are kept. If it is a compounding-switch request, switch_to_compounding_validator is called and processing ends. Otherwise, the request is rejected if source and target are the same (preventing consolidation from being used as an exit), and ignored if the pending consolidation queue has reached PENDING_CONSOLIDATIONS_LIMIT or the consolidation churn limit is at or below MIN_ACTIVATION_BALANCE. The source and target public keys must exist in the validator list, the source's execution withdrawal credentials must match the request address, and the target must have compounding withdrawal credentials. Both must be active and must not have started exiting (exit_epoch is FAR_FUTURE_EPOCH), and the source must have passed SHARD_COMMITTEE_PERIOD since activation and have no pending withdrawals. If all checks pass, the source's exit_epoch and withdrawable_epoch are set and a PendingConsolidation is added to the queue.

Compatibility, fee handling, and tests

This EIP introduces a backward-incompatible change to the consensus layer, so it must be activated through a scheduled network upgrade. When a consolidation request is cancelled at the consensus layer for exceeding the cap, neither the request fee nor the transaction gas cost is refunded. The source specifies 8 test cases, including test_single_consolidation_request_at_max_eb, test_multiple_pending_consolidations_exceeding_max_eb, and test_exceeding_max_eb_with_the_target_balance_but_not_eb, and an implementation is included in the EIP's assets directory.

Current status: Draft

This EIP was created on October 29, 2025, and its status is Draft. Proposals at the Draft stage can have their spec changed or withdrawn during review, so the check logic described here may also differ in the final version. The placeholder ([New in EIPXXXX]) still left in the spec code comments also shows that this is a draft still being refined. The core developer call notes used for this explainer contain no decision to include this EIP in a specific fork.

Original EIP · ← EIPs