As reported on November 19, 2026, the third article in LambdaClass’s series on Ethereum’s post-quantum transition focuses on preparation—not a completed migration. Borrowing Ethlabs’ concept of “PQAI Day,” it separates that work into two tracks: preparing the protocol and preparing the people and systems that use it.
A proposed protocol roadmap
The article offers an illustrative sequence, not a list of changes already in force:
- Validators would first register post-quantum key material under EIP-8483. Registration would not itself complete their migration.
- The execution layer would use Frame transactions under EIP-8141 to support post-quantum signatures. Accounts would migrate using SETCODEFROM under EIP-8298, while EIP-8151 would restrict authorization through the older ECDSA
ecrecovermechanism. - For data availability, a calldata fallback would be prepared until post-quantum approaches such as leanDA are ready.
What readiness would require
LambdaClass argues that making tools available is different from users completing a migration. Wallets, applications, validators and L2s would each need to test and coordinate ahead of time, with progress tracked through publicly measurable indicators.
The article also discusses longer-term work on signature aggregation under EIP-8288, leanSPHINCS, leanVM and leanPCS, alongside scheduling questions involving FOCIL and decoupled consensus. These are directions under discussion, not reported outcomes of the proposed preparation plan.
