EF Protocol published its Hegotá tier list and a priorities document on 7 September. The headline was December 2029. The operative numbers are 7.2 months per fork, a 12-month fallback to a minimum-viable milestone with reduced guarantees, and the fact that the execution layer gets cryptographic agility while the consensus layer explicitly does not.
On 7 September the Ethereum Foundation's Protocol cluster published two documents on the same day: a priorities post setting out what the cluster will work on through 2029, and a companion tier list grading all 62 Ethereum Improvement Proposals put forward for the Hegotá hard fork. Nearly every outlet that covered them led with the same figure — December 2029, the date by which EF says Ethereum's base layer should be quantum-resistant across its execution, consensus and data layers.
That date is the least binding number in either document. The number that governs what actually gets built is 7.2.
EF states the arithmetic itself: “Shipping Glamsterdam in December 2026 and L in December 2029 requires an average cadence of 7.2 months per fork.” Under the July Strawmap, full post-quantum readiness sits at L, five hardforks after Glamsterdam. Thirty-six months divided by five forks is 7.2. EF's own assessment follows in the next sentence: “That schedule is quite aggressive, and leaves little room for error should a fork take longer to ship than anticipated year in advance.”
Hegotá is the first of those five. That is the whole reason this fork matters more than its contents suggest.
“Hegotá is not the PQ fork; it is the fork that decides whether the PQ forks happen on time. — Ethereum Foundation Protocol cluster, 7 September 2026”
The part of the priorities post that went almost entirely unreported is that EF publishes more than one route to December 2029. A Strawmap update on 19 August added a minimum viable post-quantum milestone — MV-PQ — at J, two forks earlier than L. The post-quantum public-key registry sits at I. The post-quantum heartbeat on the consensus layer, leanDA sampling on the data layer and leanSPHINCS transactions on the execution layer sit at J. And, as EF puts it, “A 12-month cadence from Glamsterdam can reach that contingency milestone by December 2029.”
So there are at least three December 2029s in a single document, and they are not the same commitment:
The third option is not equivalent to the first, and EF does not pretend otherwise. MV-PQ is described as “a temporary safeguard,” “designed to keep Ethereum operating through Q-day with reduced guarantees.” The next sentence is the honest one: “Researchers are still defining exactly what that reduction in guarantees would look like.” Nobody yet knows what the fallback costs, because the fallback has not been specified.
This matters for anyone reading the 2029 date as a security promise. What has been committed to is a schedule with a documented degraded mode. What has not been committed to is that the degraded mode is acceptable, because its contents are undefined.
Hegotá's two must-ship items are EIP-7805, Fork-choice enforced Inclusion Lists (FOCIL), on the consensus layer, and EIP-8141, Frame Transactions, on the execution layer. FOCIL is a censorship-resistance measure: it lets validator committees force the inclusion of valid public-mempool transactions. It is not a cryptography item. Frames is.
Frames makes transaction validation, execution and gas payment programmable at the protocol level. In EF's description it “gives accounts a native route away from vulnerable secp256k1 keys, supports signature aggregation, and lets new signature schemes be introduced without a hard fork for each scheme.” That last clause is the load-bearing one. Native account abstraction converts signature-scheme migration from a fork-scale coordination problem into an account-level choice.
Here is the mechanism the coverage skipped. Cryptographic agility is available on the execution layer and explicitly unavailable on the consensus layer. EF is direct about it: the consensus layer “cannot rely on cryptographic agility; its cryptography and aggregation schemes can only change through a hard fork.” The stated consequence is that consensus cryptography “gets battle-tested and hardened before rollout, and consensus components wait for the complete PQ design instead of shipping one at a time.”
Read those two facts together and the schedule stops looking arbitrary. On execution, EF can ship the enabling machinery now and swap in post-quantum signature schemes later without spending a fork on each. On consensus, it gets one attempt per fork, and it cannot begin until the complete design exists. The calendar is therefore binding on exactly one side of the protocol — which is also why EF says its “appetite beyond it is close to zero unless an addition directly supports post-quantum readiness” when discussing further consensus-layer scope in Hegotá.
The account-side retirement work has already started, and does not wait for the consensus design. EIP-8365 begins retiring BLS withdrawal credentials tied to vulnerable cryptography — EF notes this “can begin now.” EIP-8151, which blocks legacy key authentication once an account has real code, and EIP-8298, which lets delegated accounts become full smart-contract accounts, are described by EF as “the account path for retiring secp256k1 as a master key.”
Three limitations should be stated plainly, because they are all in the source document and none of them made the headlines.
First, the deadline is self-imposed and unenforceable. The Ethereum Foundation cannot compel a single node operator or client team to upgrade on any schedule. EF calls it “a self-imposed deadline” and says the cluster “will treat this self-imposed deadline as non-negotiable at least until January 2027, when quantum progress will be reassessed with the guidance of outside experts.” Non-negotiable, in this usage, has an expiry date roughly four months out.
Second, the threat model is explicitly uncertain, and EF says so rather than hiding it: “For now, Ethereum L1 should plan for Q-day happening as early as 2030. Planning for Q-day in 2030 is a deliberately aggressive assumption. Most credible estimates place Q-day later, some much later, and we may never see it at all.” A publication that reports the 2029 target without that sentence has reported half the document.
Third, the date is doing coordination work, not forecasting work. EF's stated reasoning — “Its timing is outside anyone's control, which is exactly why we have fixed a target rather than waiting for certainty” — is an argument about organisational behaviour, not about quantum computing. The 2029 alignment with migration timelines independently published by Google, Cloudflare and Microsoft reinforces that reading: the value of a shared date is that other people are working to it.
The strongest objection is one EF raises against itself. The post links Vitalik Buterin's 2020 essay on concave decision-making and concedes that “Ethereum's instinct, rightly, is to distrust all-in bets, and so do we. Here, though, we are making that bet deliberately.” The critique that follows from that admission is straightforward: a fixed calendar target front-loads engineering risk onto a schedule rather than onto evidence. When the date is immovable and the research is not finished, the adjustment happens to scope.
There is evidence for that in the same documents. Of the 62 EIPs graded for Hegotá, 28 were marked declined for inclusion. The priority ladder published in the post shows post-quantum work moving out of the long-horizon research tier entirely: the P3 row goes from holding research capability for five multi-fork arcs to four, because post-quantum has been promoted into P1 near-fork delivery. Privacy, state, fast finality and zkEVM now share what post-quantum used to share with them. EF says privacy work “should start in Hegota” — it is competing for capacity against a fork whose core engineering commitment is already spoken for.
The defence is equally straightforward, and it is not weak. The alternative to a self-imposed date is drift, and a protocol with no ability to force upgrades has very few coordination instruments available to it. A published date that other infrastructure providers are also working to is one of the few things that functions without authority. The MV-PQ contingency is best understood as EF hedging that bet in public rather than privately.
The honest summary is narrower than the headlines. Ethereum has not promised to be quantum-safe by December 2029. Its foundation's protocol cluster has committed, for the next four months, to planning as though it will be — while publishing, in the same document, a slower route to a weaker version of the same milestone whose costs have not yet been worked out. That is a more defensible position than the headline, and a considerably less quotable one.
Q-day is the point at which a quantum computer can break the elliptic-curve cryptography securing blockchain signatures. Nobody knows when it is. The Ethereum Foundation says Ethereum should plan for it happening as early as 2030 while explicitly calling that assumption deliberately aggressive, adding that most credible estimates place it later, some much later, and that it may never arrive at all.
A third of all ether is staked, and Ethereum's own researchers have proposed making staking pay less. The governance mechanics are the same ones at work here.
Read the analysisThe revised CLARITY Act creates a category that did not exist last week. Its registration trigger is not a decentralisation metric — it is retained authority, which points straight at upgrade keys, admin multisigs and timelocks.
A race condition between the display logic and the signing buffer breaks the one promise a hardware wallet exists to make — that what the screen shows is what the key signs — without breaking any cryptography at all.
$26 billion. $31 billion. $38.17 billion. Tokenized Treasuries at $6.8bn, $12.88bn, $15bn, $16.21bn. All published in 2026, all defensible, none reconcilable without knowing the date and the definition.