For Ethereum builders, post-quantum preparation is not a single upgrade. In the third article of its Ethereum post-quantum migration series, reported on November 19, 2026, LambdaClass describes a proposed “preparation” phase built around two tasks: getting the protocol ready and getting its participants ready. The article draws on Ethlabs’ PQAI concept.
LambdaClass offers an illustrative roadmap, not a list of enacted changes. In it, validators would first register post-quantum key material under EIP-8483; registration alone would not mean they had migrated. On the execution layer, Frame transactions under EIP-8141 would support post-quantum signatures. Accounts would migrate using SETCODEFROM under EIP-8298, while EIP-8151 would restrict authorization through the legacy ECDSA ecrecover mechanism.
For data availability, the article calls for a calldata fallback until post-quantum approaches such as leanDA are ready. It also stresses that making tools available is different from completing a migration: wallets, applications, validators and Layer 2 networks would each need to test and coordinate ahead of time. Publicly measurable indicators could track that progress.
The article separately discusses longer-term directions—including signature aggregation under EIP-8288, leanSPHINCS, leanVM and leanPCS—and scheduling questions around FOCIL and decoupled consensus. These are presented as planning considerations, not completed upgrades.