EIP-8449: consensus clients tell execution clients their proposal slots an epoch ahead
A new Ethereum proposal, EIP-8449, Engine API Proposal Lookahead, was merged into the EIPs repository as a draft on 3 November. Its author is Csaba Kiraly; it was created on 19 October and requires EIP-7917.
The EIP adds one Engine API method, engine_proposalLookaheadUpdatedV1. With it, a consensus-layer client tells its execution-layer client the slots, timestamps, fee recipients and target gas limits of the blocks its validators are scheduled to propose in the current and next epoch. The text stresses that it is a notice, not a command: it starts no build, names no parent block and changes no consensus rule. The execution client can use it to prepare in ways that do not depend on the parent block, such as fetching blob data, warming state, pre-executing pending transactions and keeping its own heavy work and network traffic away from the slot.
The motivation section measures how late execution clients learn about a proposal today. In the Engine API up to Amsterdam, an execution client learns it must build a block when forkchoiceUpdated arrives with payload attributes, which also starts the build and depends on the parent. Before Gloas, according to the EIP, Prysm, Teku and Grandine send that call when the parent is imported, Lighthouse and Lodestar four seconds before the slot and Nimbus 1.5 seconds before, and only Lighthouse's lead is configurable. That leaves at least 8 seconds when the parent is on time. The consensus client, by contrast, knows its proposal slots much earlier, since EIP-7917 made the proposer schedule known in advance.
The merge adds test vectors alongside the specification.

What it means
Block builders inside the execution client get minutes of notice instead of seconds. The practical gain is at the edges: blob fetching and state warming done before the slot rather than in it.