Insights on Crypto Payments, Infrastructure, and Operations

Ethereum Execution Request

Abbreviation: EL Request

Pronunciation: ih-THEER-ee-um ek-sih-KYOO-shuhn ree-KWEST

Also known as: Execution Layer Request, EIP-7685 Request, EL Request

Definition

An Ethereum execution request is a typed protocol message produced by execution-layer activity for later processing by the consensus layer. EIP-7685 defines a general request bus, encoding each request with a type byte and request data, then committing the block’s non-empty requests in requests_hash. Withdrawal and validator-consolidation requests can use this framework.

Overview

Meaning and scope

An Ethereum execution request is a typed protocol message produced by execution-layer activity for later processing by the consensus layer. EIP-7685 defines a general request bus, encoding each request with a type byte and request data, then committing the block’s non-empty requests in requests_hash. Withdrawal and validator-consolidation requests can use this framework.

Mechanism and operation

An Ethereum execution request is a message passed from the execution layer to the consensus layer through the framework defined by EIP-7685. It allows transactions and designated system contracts to trigger protocol operations that require consensus-layer processing. Each request consists of a one-byte request type followed by request-specific data. During execution-block processing, the client collects request objects produced by the active request mechanisms. Non-empty request objects are ordered by type, hashed, and committed through the requests_hash field in the execution block header. This commitment allows clients to verify that the request data delivered to the consensus layer matches what was derived from the execution block.

Practical payment example

An Ethereum client processes a typed execution-layer request and confirms it is included in the appropriate consensus-layer processing flow.

Operational checks

Request-specific proposals determine where data comes from, how fees and rate limits work, and what the consensus layer must validate. For example, validator withdrawal and consolidation mechanisms can collect calls in predeploy contracts, dequeue a limited number at the end of a block, and expose them as typed requests.

Distinctions and limits

Different request types can use different internal encodings and validation rules. The framework acts as a general bus rather than defining the business rules of every request. The consensus layer may later reject or delay an item if credentials, validator state, or churn conditions are not satisfied.

Related definitions: contract transaction, consensus layer.

Example

An Ethereum client processes a typed execution-layer request and confirms it is included in the appropriate consensus-layer processing flow.

Comparison

The framework acts as a general bus rather than defining the business rules of every request. The consensus layer may later reject or delay an item if credentials, validator state, or churn conditions are not satisfied.

Key Takeaway

Ethereum execution requests provide a committed, typed channel from execution activity to consensus processing without making every request automatically valid or immediate.

Sources

  1. EIP-7685: General Purpose Execution Layer Requests — Ethereum Improvement Proposals (2026-08-02)
  2. EIP-7251: Increase the MAX_EFFECTIVE_BALANCE — Ethereum Improvement Proposals (2026-08-02)
  3. EIP-7600: Pectra Hardfork Meta — Ethereum Improvement Proposals (2026-08-02)