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, 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 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.