Mission 2028: Ethereum's cryptography can't wait for Q-Day

Mission 2028: Ethereum's cryptography can't wait for Q-Day

Our takeaways from Devcon 8 and the Ethereum L1 R&D workshop.

At LambdaClass, we have spent the past two years building ethrex, our execution client, and the past year building ethlambda, our consensus client. We want both to contribute to an Ethereum that is still running in twenty years. Helping the protocol prepare for threats to its cryptography is part of that responsibility.

Devcon 8 gave us the chance to discuss those threats with the people working on them. We are grateful to everyone who made the event possible and took the time to exchange ideas with us. The Ethereum L1 R&D workshop, held alongside it, brought client teams, researchers, and the Ethereum Foundation (EF) together to work through the protocol roadmap.

We arrived at Devcon already convinced that Ethereum needed to accelerate its transition to stronger cryptography. We were glad to see that sense of urgency shared by the client teams and researchers at the workshop. Getting Ethereum ready by the end of 2028 will require difficult decisions about the roadmap, including revisiting priorities agreed on only recently. We think those decisions are worth making.

This post offers a high-level overview of the transition and its implications for Ethereum's roadmap. We'll explore these topics in greater depth in future posts.

Why 2028 matters

At the workshop, EF leadership asked whether Ethereum's cryptography could be brought to a safe place by the end of 2028. That question deserves to shape the work we prioritize now. The Post-Quantum Transition keynote by Justin Drake and Kev provides public background on these questions, as does Drake's PQ Ethereum Q&A.

We do not know when Q-Day will arrive: the point at which quantum computers can break the public-key cryptography Ethereum currently relies on. But the time required to prepare Ethereum is substantial. Candidate schemes need scrutiny, clients need implementations, and the network needs a workable transition. An uncertain threat date leaves less room for delay than it might seem.

The March 2026 research from Google Quantum AI and collaborators, together with the work tracked at ecdsa.fail, shows another reason to take that uncertainty seriously. Estimates of the quantum resources needed to attack elliptic-curve cryptography can fall as algorithms improve. Our planning has to account for progress in the attack itself as well as in the machines that could carry it out.

Quantum computing also isn't the only concern. Justin Drake used the phrase "alien math" in his Devcon talk to describe the possibility of unexpected mathematical breakthroughs undermining today's cryptographic assumptions. AI-assisted research adds urgency to that possibility. We should take it seriously without pretending that we can predict which breakthrough will happen or when.

A more resilient cryptographic foundation

A central part of the transition is replacing BLS for validators and giving users alternatives to ECDSA. The direction discussed at the workshop favored hash-based signatures, whose security rests on hash functions. We believe this is the right direction for Ethereum's long-term security because it relies on assumptions we expect to be more resilient to quantum attacks and unexpected mathematical breakthroughs.

The engineering challenge is size: these signatures are much larger. STARKs offer a way to aggregate them by proving that many signatures are valid, allowing others to verify a shared proof. On the execution side, EIP-8288 explores this approach to make post-quantum user transactions practical.

Preparing the migration can also begin before the signature switch. EIP-8483 and EIP-8450 explore different ways to register post-quantum material or keys ahead of a later migration fork. That preparation needs to happen while the mechanisms used to authorize registration can still be trusted.

The exact schemes and parameters remain open. XMSS and SPHINCS+-style designs are among the candidates, and choosing between them will require further research, benchmarking, and testing in real clients. The roadmap needs to make room for both that work and the preparation we can start earlier.

Reopening the roadmap is a responsible choice

Reopening a recently agreed fork scope has a real cost. Teams have committed engineering time, built dependencies, and planned around it. But the roadmap has to respond when our assessment of a security risk changes. The cost of waiting belongs in that decision, too.

The Strawmap, a draft L1 roadmap maintained by EF Architecture, helps put these choices in context. Bringing post-quantum readiness forward means reconsidering how it fits with other upgrades: what needs to happen earlier, what can proceed in parallel, and what may have to wait.

Accelerating post-quantum work was not the workshop's original purpose. We still think raising it was the right call. Having so many of the people responsible for the transition in one room made it possible to discuss the tradeoffs directly. People challenged the timing, scope, and meaning of readiness. As we understood the discussion, everyone agreed that the work needed to accelerate.

The next decisions belong in the public process

Agreement on urgency leaves important decisions open: which changes should ship first, what gets delayed, and what evidence will show that the proposed designs are ready.

Those choices belong in Ethereum's public process, including All Core Devs calls and the technical discussions around them. The workshop's alignment is a starting point for proposals that still need public scrutiny and rough consensus.

Client implementations, benchmarks, and testing will help turn that urgency into concrete decisions. We intend to contribute to that work.

Correct implementations are part of the goal

Formal verification belongs to the roadmap alongside new cryptography. Strong primitives only help if clients implement them correctly, and formal proofs can give us stronger assurance that the code satisfies its specification.

Devcon gave this work a prominent place. Derek Sorensen and Certora co-founder Mooly Sagiv delivered the opening keynote Reducing the Trust Surface. Sorensen's Lean workshop and evm-asm talk, Sagiv's Bug-Free Solidity Coding Agents, and Cody Gunton's zkEVM verification talk explored practical approaches across client code, smart contracts, and proving systems.

The EF's Verified zkEVM project addresses correctness in Ethereum's proving infrastructure. EthLib develops shared Ethereum definitions and proofs in Lean, including work on post-quantum signatures. Etheorem brings executable consensus specifications into Lean 4, with formal verification progressing across its components.

We are also working with Lean 4 ourselves. Our takeaway is that the 2028 effort needs to advance implementation and verification together.

What we will contribute

Alongside its implementation of today's Beacon Chain, ethlambda participates in Lean Consensus, the experimental redesign of Ethereum's consensus layer. Our work on devnets with hash-based signatures gives us a working environment for exploring candidate schemes and measuring how they behave in a client. Ethrex's small codebase makes it well-suited to testing the execution-layer changes needed to support new user signatures.

We will use both to contribute to the transition, publish benchmarks and results as they become available, and bring what we learn to the ACD discussions.

We believe the 2028 goal is achievable. The building blocks exist, and capable teams are already working on them. Reaching that goal will require teams across the Ethereum ecosystem to prioritize this work now and carry it through research, implementation, and testing. We are ready to do our part.

What comes next

This post opens a series on Ethereum's post-quantum transition. Here, we have focused on the roadmap: why the work needs to accelerate, how that affects other priorities, and how the next decisions should be made.

The posts that follow will explain exactly which parts of Ethereum would break under quantum attacks and why. We will explore some of the potential solutions already on the table, the tradeoffs they introduce, and how we can prepare for the transition. Finally, we will examine the remaining steps toward a fully post-quantum Ethereum across execution, consensus, and data availability: what still needs to change and how those changes fit together.

You can follow our work in ethrex and ethlambda, both open source, and on X.