Ethlabs is asking Ethereum developers to make quantum protection and resilience against advanced AI-assisted attacks the priority for 2027, according to a Nov. 11 proposal. The group also proposes withdrawing its quick-slots work from Hegotá and reconsidering work that falls outside that security objective.
The proposal is a contribution to Ethereum's development process, not an activation date. A research group's preferred timetable still requires specifications, implementations and testing, and client teams must agree on what to build and demonstrate together. Ethlabs separates basic readiness, which means keeping Ethereum operational with quantum-safe options, from the more ambitious goal of matching full network capacity.
Account signatures are a key building block
One component cited is EIP-8141, the frame-transaction proposal. It would allow a transaction to contain separate steps for validation, fee approval and execution, giving accounts more flexibility over how they authorize activity. That includes a path away from today's elliptic-curve signatures, along with key rotation, batched operations and alternative fee payment.
Protocol flexibility alone does not deliver protection. Wallet developers would need to expose safer signature schemes clearly, exchanges would need to recognize them, and users would need a recovery path they understand.
Multiple areas need preparation
Ethereum's quantum-security overview identifies exposure in ordinary account signatures, validator signatures, data commitments and some proof systems. Each component has a different role, so replacing one would leave other migration work outstanding. The overview also says present-day quantum computers cannot break Ethereum's cryptography; preparation is proceeding because a network-wide transition takes time and future hardware capability is uncertain. Hash-based approaches are among the routes being researched.
The next test is coordinated delivery
The proposal's significance lies in resource allocation. Adding features creates implementation and review work, while focusing on security can defer improvements other users want sooner. A credible programme would need measurable milestones: working clients, agreement on migration behavior and evidence about performance under new cryptography, plus a clear account of which guarantees are available at each stage.
For ETH holders, those milestones are more informative than a calendar target alone. The debate now asks developers to turn an ambitious security objective into a sequence the wider Ethereum ecosystem can deliver.

