ETH Daily
Menu

Ethlabs proposes a 2027 target for Ethereum’s post-quantum readiness

Originally reported by The Block on November 12, 2026, at 15:26 UTC+8.

Ethlabs has proposed moving Ethereum’s post-quantum target to 2027. The group calls its plan pqai27 and argues that AI is making the timing of quantum and other cryptographic risks harder to predict. This is a proposal, not an activated Ethereum upgrade or an agreed network schedule.

Two levels of readiness

Ethlabs describes two possible outcomes for 2027. Under “pqai-ready,” Ethereum’s consensus would be post-quantum, users would have a post-quantum route for their accounts, and the network would continue operating at scaled capacity. “Pqai-scaled” would go further: the network would operate at full capacity with post-quantum transactions and data availability.

The group also wants Ethereum to be “post-AI,” which it describes as cryptography relying on as few assumptions as possible and clients hardened against AI-assisted bug discovery through formal verification and client diversity. These are Ethlabs’ proposed goals, not confirmed properties of the network.

Ethlabs proposes a 2027 target for Ethereum’s post-quantum readiness

What Ethlabs would change

Ethlabs said the Ethereum Foundation had previously set December 2029 for full post-quantum readiness. In arguing for an earlier target, it cited a U.S. government quantum-risk goal of 2030, moved from 2035, and Google’s stated 2029 post-quantum aim. It also pointed to AI progress in mathematics and vulnerability discovery; those examples form part of Ethlabs’ case for urgency.

To prioritize pqai27, Ethlabs said upcoming hard forks, including Hegotá, should be reassessed for work outside the critical path. It stated that it will withdraw its “quick slots” proposal—which would speed up block production—from Hegotá and redirect its resources to pqai27. The report does not establish that the withdrawal or the proposed reprioritization has been adopted.

Source: theblock.co (originally published 2026-11-12 15:26 UTC+8)