Computational cryptography › Not live yet › Hash-based
ZK PROOFPlanned, not live yetPlanned: Contingency (Ethresear.Ch 2024)

Quantum emergency fork

In plain words

A backup plan if a quantum computer appeared suddenly: freeze vulnerable accounts and let real owners prove ownership with their seed.

Why it matters: Shows funds could be saved even in a worst-case surprise.

The details

On the map: roll back, freeze ECDSA accounts, recover them with a STARK proof of knowing the BIP-32 seed

Map note, rests on: seed preimage resistance + sound STARK prover + social consensus to roll back

A contingency plan (Vitalik Buterin, ethresear.ch, 2024)[1] if a quantum computer appeared suddenly: roll back blocks with quantum thefts, disable ordinary EOA transactions, and let owners recover their accounts, converted into smart-contract wallets, with a STARK proof that they know the seed their key was derived from.

It works because seed derivation is a one-way hash: the attacker can compute the private key but not the seed. It isn't on the official roadmap and would need broad social consensus to execute.

Rests on

If any of these breaks, this breaks too.

If it falls

If this breaks, these break with it.

Nothing on the map depends on it: it is an end point of the roadmap.

References

  1. Vitalik Buterin. How to hard-fork to save most users' funds in a quantum emergency. ethresear.ch, 2024. ethresear.ch/t/how-to-hard-fork-to-save-most-users-funds-in-a-quantum-emergency/18901