# EIP-8449 draft proposes advance block-building notices between Ethereum clients

Canonical: https://forkbrief.com/news/7ac9a4a3-a308-4373-b3de-94063fb65b4e
Published: 2026-11-04T14:41:51.684Z
Publisher: Fork Brief

The new repository draft separates advance proposal schedules from the Engine API call that starts a block build, with optional support and complete schedule replacement.

Ethereum’s EIPs repository added EIP-8449 on November 3, proposing a way for consensus clients to give execution clients advance notice of upcoming block proposals. The draft separates preparation from the later instruction that actually starts building a block.

The [repository commit](https://github.com/ethereum/EIPs/commit/46976b2a9bf99f727fb87dc8c809e3a3cdc6b445) added the specification at 23:14 UTC. Its creation field is October 19. The new development is repository inclusion of the draft, rather than the first discussion of the idea or a network activation.

The [proposed method](https://eips.ethereum.org/EIPS/eip-8449), `engine_proposalLookaheadUpdatedV1`, would send the slots, timestamps, fee recipients and target gas limits of upcoming proposals for validators attached to the consensus client. It covers the current and next epoch. The execution client could use that schedule to fetch blob data, warm caches or arrange maintenance before a proposal slot, choosing its own preparation strategy.

The notice contains no parent block and must not start a build. That remains the job of `engine_forkchoiceUpdated` with payload attributes. If those later attributes differ from the advance notice, the payload attributes take precedence. This distinction lets a client announce a schedule without prematurely choosing which head to build on.

Each request would replace the entire stored schedule. An empty list clears it, while an invalid request leaves the previous schedule unchanged. The draft caps a request at 256 entries and requires validation before replacement. A new notice therefore represents a complete schedule update, rather than a series of additions that the execution client must reconcile.

EIP-8449 remains a Standards Track Core draft. Its optional-support section requires capability negotiation before a consensus client calls the method. Repository addition does not establish implementation by any particular client, and the document does not tie support to a scheduled fork.

## Sources

- [EIP-8449: Engine API Proposal Lookahead](https://eips.ethereum.org/EIPS/eip-8449) — Ethereum Improvement Proposals
- [Add EIP: Engine API Proposal Lookahead](https://github.com/ethereum/EIPs/commit/46976b2a9bf99f727fb87dc8c809e3a3cdc6b445) — Ethereum EIPs

- [Editorial policy](https://forkbrief.com/editorial-policy)
- [Request a correction](https://forkbrief.com/corrections)