Wallet custody, cryptographic trust boundaries, vulnerabilities, audits and practical defensive habits

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

For Ethereum holders, the practical question in Ethlabs’ proposal is whether every user would have a path to move to a post-quantum account if today’s cryptography became unsafe. That path is a proposed goal, not a feature already in place.

As reported on November 12, 2026, Ethlabs had posted a roadmap in the Ethereum developer forum called “pqai27.” It proposed 2027 as a target for strengthening Ethereum against potential quantum-computing and AI-related security risks. Ethlabs argued that advances in quantum computing and AI-assisted software vulnerability discovery make earlier protocol-level preparation worthwhile. It also said there was no evidence that AI would necessarily break existing cryptographic primitives, and that the risk was difficult to predict.

The proposal separates the work into two goals:

  • “pqai-ready”: Upgrade Ethereum’s consensus layer for post-quantum security and give all users a route to post-quantum accounts. If existing cryptography failed sooner than expected, the network could continue operating at reduced throughput.
  • “pqai-scaled”: Support post-quantum transactions and data availability at full network capacity. Ethlabs identified post-quantum signature aggregation and data-availability schemes as part of reaching ordinary transaction-processing scale.

Ethlabs cited its understanding that the US government had moved a quantum-risk target from 2035 to 2030 and that Google planned to achieve post-quantum capability before 2029. These were points in Ethlabs’ case for prioritizing the work, not evidence that Ethereum’s current cryptography had been broken.

To make room for the roadmap, Ethlabs suggested reconsidering features planned for the later Hegotá hard fork that are not on pqai27’s critical path. It regarded Frames and related post-quantum account proposals as important, while calling for a reassessment of FOCIL’s effect on timing and compatibility. Developers would also need to choose between adapting the existing Gasper consensus protocol and moving to a decoupled consensus design.

Ethlabs said it would withdraw its earlier push to include Quick Slots in Hegotá and instead seek to advance that feature in 2028. It proposed leaving Glamsterdam and its scaling plans on their existing course. The roadmap remained an Ethlabs proposal for Ethereum core developers to discuss and decide, not an agreed upgrade schedule or a reason for holders to assume a new account migration is available.

Further reading