On September 16, 2024, Ethereum Foundation researchers will sit inside a Reddit AMA and explain quantum safety to a community that wants reassurance. The roadmap document they are defending contains one sentence that should end the conversation: Hegotá is not a quantum-resistant fork. The important signal is not the date of the AMA. It is the grading list hiding inside the upgrade plan. Exactly two proposals carry the highest internal rating, the must-ship S grade. One is FOCIL. The other is Frame Transactions. Neither is a post-quantum signature scheme. That is not an oversight. That is the thesis.
Ethereum's exposure is textbook applied cryptography. Execution-layer accounts rely on secp256k1 and ECDSA. Consensus nodes sign with BLS. Shor's algorithm, once scaled to enough logical qubits, breaks both discrete-log and elliptic-curve assumptions. The roadmap therefore sets a hard migration target: December 2029, with a formal re-evaluation checkpoint in January 2027. The immediate forks are Hegotá and Glamsterdam. Neither contains a final post-quantum implementation. They belong to an earlier stage of the sequence. MV-PQ is the architectural milestone where execution layers can start accepting new signature types; J and L come later as the enforcement and completion forks. Anyone reading those names as event guarantees is misreading dependency declarations as delivery dates.
Let me start with an observation from auditing contracts. When a team tells me it is preparing for key migration, I do not read the whitepaper; I read the bytecode. The reason is simple. On Ethereum, every address that has broadcast even one transaction has already revealed its secp256k1 public key. The private key remains protected only by the hardness of the discrete-log problem. A sufficiently advanced quantum attacker does not need to wait for a live transaction. It can copy the public data now, then solve offline once enough qubits exist. That makes migration less like changing a lock and more like evacuating a building while the fire is hypothetical. Urgent, necessary, and a perfect invitation to chaos.
Now examine what Ethereum actually ranked as mandatory. FOCIL, meaning fork-choice enforced inclusion list, is not a cryptographic primitive. It is a power constraint on block builders. It forces inclusion of transactions that validators want, even when builders prefer censorship. Why would a post-quantum roadmap depend on an anti-censorship mechanism? Because key migration is a transaction-level event. Users must broadcast new authorization logic from old addresses. If a builder does not want migration to happen, because it extracts value from static users, or because state changes reduce control, the migration can be delayed indefinitely. FOCIL is not quantum defense. It is the game-theoretic guarantee that defense transactions will land. In my experience, security migrations fail at coordination before they fail at mathematics.
Frame Transactions are the second S-grade proposal and the actual prerequisite. Ethereum's transaction schema is welded to secp256k1 signatures. You cannot simply bolt a post-quantum signature algorithm onto the current object; the format assumes one elliptic-curve world. Frame Transactions decouple execution logic from cryptographic format. They create a neutral container for account abstraction, future signature schemes, and multiple authorization flows. Without them, replacing the signature primitive would demand a hard fork inside a hard fork. With them, J and L can install a new signature schedule through an application-level frame. The order is correct: change the container, then change the key.
There is also a validator-side problem hiding beneath the roadmap. More than 34 million ETH are currently staked. Each validator controls BLS key material that will eventually have to rotate. This is not only a user migration; it is an institutional coordination problem across staking pools, solo stakers, and infrastructure providers. A consensus-layer signature migration touches finality, withdrawal credentials, and slashing conditions simultaneously. The S-grade ranking says the execution-layer frame comes first, but the consensus rotation must be scheduled without ever dropping finality. That constraint is harder than any quantum algorithm ever proposed.
What the roadmap does not address is cost. Post-quantum signature schemes are not drop-in replacements for BLS. Many candidates produce signatures larger than current elliptic-curve signatures by orders of magnitude. Witness sizes grow, block propagation changes, and the EVM gas schedule must adapt. The source material for this upgrade cycle does not publish those numbers. A migration plan that cannot quantify its own gas overhead is still a research proposal, not an engineering schedule. The December 2029 deadline may be real, but the accounting has not been done in public.
One detail is absent from the entire discussion: external peer review. No independent post-quantum cryptographer is cited. No audit of Ethereum's migration assumptions is mentioned. Internal S-grade labels are planning tools, not proofs. For a transition whose failure mode includes mass loss of funds, the absence of public verification is its own risk factor.
The dates reinforce this. January 2027 is not project-management ornament. It is a quantum-intelligence checkpoint. If the field moves faster than the consensus layer expects, Ethereum will need emergency forks before the MV-PQ sequence matures. A hard deadline with zero tolerance for slippage is either discipline or denial. The 2029 target says the Foundation believes quantum computers will not arrive early. It does not say what happens if they do.
The standard counter-narrative is not worthless. Ethereum is ahead of nearly every major L1 on paper. Bitcoin has no public post-quantum timeline. Solana's Ed25519 stack has no migration schedule. Ethereum announced a concrete deadline without pretending the cryptography is ready now. The 2027 re-evaluation is honest about uncertainty. Hegotá deliberately avoids locking in a half-mature signature algorithm. That restraint deserves credit. But complexity is not free. FOCIL, Frame Transactions, signature migration, and account abstraction are not four independent workstreams. They are four interacting state machines. Every interaction creates a new exploit surface. The probable crisis is not a quantum computer arriving early; it is an unanticipated bug in the migration sequence, a wallet signing the wrong frame, or an inclusion list that works in testnet and gets gamed in production. Roadmaps are not attack-resistant. Ledgers are witnesses.
By December 2029, the result will not be judged by a press release. It will be visible on-chain. Watch for a public migration drill: millions of legacy EOA addresses moving through Frame Transactions under FOCIL. If that drill has not happened by January 2027, the hard deadline is a narrative, not a plan. The Reddit AMA will answer questions. The network will answer only when old keys stop moving.