# EIP-8450 revision changes draft gossip checks for differing chain views

Canonical: https://forkbrief.com/news/663063cd-8ef0-457f-8b88-3a7f8b65a293
Published: 2026-11-05T20:41:13.852Z
Publisher: Fork Brief

The November 5 draft edit separates head-dependent registration checks from REJECT checks while retaining block-processing requirements and dormant keys.

A November 5 revision of Ethereum’s EIP-8450 changes how nodes would handle proposed consensus-key registrations when their local views of the chain differ. The document remains a Draft Core proposal; the repository edit does not activate the registry on Ethereum.

The [revision](https://github.com/ethereum/EIPs/commit/e51d38a636dddbc9d823dd3ba66357fb61e85db6), titled “Address post-merge review,” separates checks that depend on a node’s current head state from checks of the registration’s contents. Its gossip rules describe which messages nodes would forward before those registrations appear in a block.

For the stored change epoch and whether a leanXMSS key is already registered, the draft now uses IGNORE where the previous text used REJECT. It explains that nodes can hold different stored epochs or see different holders of a key at their respective chain heads. A newly added index-existence check also uses IGNORE because a recently processed deposit might not yet appear in every node’s head state.

Consider a node that has not yet seen the most recent key change. A message can name a previous-change epoch different from that node’s stored value. The revised text classifies that head-dependent mismatch under IGNORE. This is a documented example of the proposed rule, rather than an executed network test.

The [full specification](https://github.com/ethereum/EIPs/blob/e51d38a636dddbc9d823dd3ba66357fb61e85db6/EIPS/eip-8450.md) continues to require a matching stored epoch during block processing. It also retains REJECT classifications for failed signature and proof-of-possession checks. Changing gossip handling therefore does not remove those listed validation requirements.

The update concerns the draft’s message-handling rules, following earlier changes to registration and replacement authorization. Registered keys would still remain dormant until a later fork switches signing duties. No activation date or deployed client support is established by this edit.

Earlier coverage of this event: [Ethereum EIP-8450 draft adds builders and changes key authorization](https://forkbrief.com/news/01f5ebb6-168a-4a81-a097-d84884d14b06).

## Sources

- [EIP-8450: Post-Quantum Consensus Key Registry \[Draft, November5 revision e51d38a\]](https://github.com/ethereum/EIPs/blob/e51d38a636dddbc9d823dd3ba66357fb61e85db6/EIPS/eip-8450.md) — Ethereum EIPs specification repository
- [Update EIP-8450: Address post-merge review](https://github.com/ethereum/EIPs/commit/e51d38a636dddbc9d823dd3ba66357fb61e85db6) — Ethereum EIPs

## Related reporting

- [Ethereum EIP-8450 draft adds builders and changes key authorization](https://forkbrief.com/news/01f5ebb6-168a-4a81-a097-d84884d14b06) — Fork Brief

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