Ethereum Researchers Updates First Post-Quantum Upgrade Proposal EIP-8450

Ethereum Researchers Updates First Post-Quantum Upgrade Proposal EIP-8450


Ethereum proposes post‑quantum validator key registry, signaling an industry‑wide shift toward quantum‑resistant blockchain security.

Simplified design removes execution‑layer path, reducing complexity and aligning with broader crypto standards for key management.

Early registration window gives validators and clients months to test, mirroring other platforms’ proactive quantum‑readiness strategies.

Ethereum developers have submitted EIP-8450, a proposal to give every validator a dormant, quantum-resistant public key years before it would ever actually be used.

EIP-8450, “Post-Quantum Validator Key Registry,” was created Oct. 15, 2026, by Thomas Coratger, Kevaundray Wedderburn, Tom Wambsgans, and Justin Drake. The core idea: every Ethereum validator would register a dormant, hash-based public key—a leanXMSS key—tied to its existing validator index, well before that key is ever actually used for anything.

Today, every consensus-layer signature on Ethereum uses BLS12-381, a scheme that Shor’s algorithm could break on a cryptographically relevant quantum computer (CRQC). Because every validator’s public key already sits in the beacon state, a working CRQC could theoretically recover validators’ secret keys.

Splitting the migration into separate forks, as this EIP proposes, gives the network a preparation window where validators can generate and register post-quantum keys while BLS remains the only scheme actually used for duties, a readiness signal showing what fraction of stake has registered, and a head start for client teams to build and test the new verification logic before anything depends on it.

As originally drafted, registration could happen two ways: through a validator’s existing BLS signing key (registration only, no replacement), or through the validator’s withdrawal address via a new execution-layer request, which could register or replace keys. The proposal required valid proof of possession either way to stop someone from copying a published key to claim another validator’s signatures.

What’s Changed: One Authorization Path, Not Two

A follow-up pull request, opened by Kevaundray (with Tom Wambsgans credited as co-author), makes what its own title calls “misc changes” to EIP-8450—but the most significant one is structural: it removes the withdrawal-address (“owner”) path entirely.

Under the revised draft, a validator’s BLS signing key is now the only authority that can register or replace a post-quantum key; there’s no longer a second route through the execution layer. That simplification shows up directly in the EIP’s dependency list, which shrinks from three other EIPs (7002, 7685, and 7916) to just one (7916), since the execution-layer request contract, its pending-authorization queue, and the epoch processing that supported it are all removed along with the owner path. The EIP no longer touches the execution layer at all.

The revision adds its own safeguards in place of what was removed: key changes are now rate-limited to once every MIN_PQ_KEY_CHANGE_DELAY (256 epochs, or 8 in the minimal test preset), and a new previous_change_epoch field checked against a state list called pq_key_change_epochs protects against replay. A FAR_FUTURE_EPOCH marker flags validators that have never registered a key at all.

On the cryptography side, the registered key structure (PQPublicKeys) now simply combines a leanXMSS key with a VRF root, with no version byte, and proof of possession is still required once per key. The revision also trimmed the EIP’s Rationale section from roughly 1,700 words to about 900 and dropped its Reference Implementation section, Keccak-specific implementation details, and a helper function (get_pq_registered_balance) entirely—the PR reads as a genuine simplification pass, not just wording cleanup.

Where This Fits in Ethereum’s Longer Quantum Timeline

The PR carries no shortage of “this isn’t final yet” markers: it’s still labeled Draft, with the GitHub labels e-consensus and e-review showing it’s awaiting editor consensus and review, and neither the original EIP nor the revision names a specific network upgrade or fork epoch it’s targeted for. A companion pull request on Ethereum’s consensus-specs repository implementing the same registry is also still a draft. Test vectors, the request contract bytecode, and a reference implementation remain open items.

EIP-8450 sits inside a much longer-running effort. Other reporting has described it as the first concrete protocol fork on the Ethereum Foundation’s post-quantum “Strawmap”—the roadmap that followed the Foundation forming a dedicated post-quantum security team and offering a $1 million research prize.

That team has said core Layer 1 protocol upgrades could wrap up by 2029, with full migration taking several more years beyond that, structured across three phases: readiness and infrastructure, gradual adoption, and protocol-level consolidation. More than 10 client teams are reportedly building devnets weekly as part of ongoing interoperability testing.

The Foundation has been explicit that no cryptographically relevant quantum computer exists today and that this is early, deliberate preparation for a decentralized network that can’t upgrade its cryptography quickly or easily once a real threat materializes—not a response to an active or imminent attack.

Also Read: Ethereum Developers Merge Patch for Bug That Put Staking Deposits at Risk


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *