Ethereum Consolidation Request
Pronunciation: ih-THEER-ee-um kuhn-sol-ih-DAY-shuhn ree-KWEST
Also known as: Validator Consolidation Request, EIP-7251 Consolidation Request
Definition
An Ethereum consolidation request is an execution-layer request that asks the consensus layer to combine the balance of one validator into another eligible validator. Introduced with EIP-7251, it supports larger effective validator balances and reduces the number of separate validator records an operator may need. The request includes source and target validator public keys, enters a rate-limited queue, and is processed only after protocol authorization and consensus-layer eligibility checks succeed.
Overview
An Ethereum consolidation request is the protocol message used to initiate an in-protocol consolidation of validator stake under EIP-7251. The request identifies a source validator and a target validator by their BLS public keys and records the execution-layer address that submitted it. Its purpose is to let eligible operators combine validator balances instead of exiting multiple validators and depositing the funds again.
The request begins with a transaction that calls a designated predeploy contract on the execution layer. The caller supplies the source and target public keys and pays the current request fee. The contract places the request into a queue. At the end of block processing, a system call dequeues a limited number of requests and exposes them through the EIP-7685 execution-request mechanism for processing by the consensus layer.
Submitting the request does not guarantee immediate consolidation. Consensus rules verify authorization, withdrawal credentials, validator status, target eligibility, and churn limits. The source address must correspond to the withdrawal credential authorized to control the source validator. Requests can wait in a queue, and the protocol limits how quickly consolidations consume validator churn. The target can use compounding withdrawal credentials and may hold an effective balance above the original 32 ETH ceiling, up to the protocol limit introduced by EIP-7251.
For staking infrastructure, a consolidation request should be tracked as a multi-stage operation: execution transaction submitted, request included, request queued, consensus processing started, and consolidation completed. A successful blockchain confirmation of the calling transaction proves that the request entered the execution-layer process, not that the validator balances have already merged. Operators should monitor validator indices, credentials, queue status, effective balances, and any rejection condition before updating accounting or operational ownership records.
Key Takeaway
An Ethereum consolidation request starts a rate-limited protocol process for merging validator stake; transaction inclusion alone does not mean consolidation is complete.
Sources
- EIP-7251: Increase the MAX_EFFECTIVE_BALANCE — Ethereum Improvement Proposals (2026-08-02)
- EIP-7685: General Purpose Execution Layer Requests — Ethereum Improvement Proposals (2026-08-02)
- EIP-7600: Pectra Hardfork Meta — Ethereum Improvement Proposals (2026-08-02)