What changed
Ethereum’s roadmap page lists a second Post Quantum research retreat from 9 to 12 October 2026 in Cambridge, UK. The Ethereum Foundation Post Quantum Security team runs weekly interop devnets with more than ten client groups. Public repos include leanXMSS, leanVM, leanSpec, leanSig, and leanMultisig under the leanEthereum GitHub org. Milestones I through M describe how post quantum keys and signatures would enter the protocol.
Write the date you checked sources on your internal wiki.
Share a one page brief with your exec sponsor this week.
Do not treat social posts as proof without a primary link.
Ask legal if new data types change your retention policy.
Log which model version you tested in the lab notebook.
Set a reminder to re read the vendor note in thirty days.
Compare cloud cost to self host cost with the same query set.
Invite security to the next sprint planning session.
Capture open questions in your decision log.
Note which regions your test data came from.
Check if your insurer asks about remote support tools.
List which customer tiers would see a user facing change.
Track GPU hours per thousand embed calls during the pilot.
Save raw benchmark tables, not just chart screenshots.
Why it matters
Quantum risk is still distant for most users, but chain teams must plan early. Signature upgrades touch wallets, validators, and smart contracts. A public retreat signals active cross client testing, not a slide deck only.
Confirm your backup keys still work after any upgrade.
Review consent copy if you add photo uploads.
Pair engineering with a clinician before you change training UI.
Document rollback steps before you patch appliances.
Test fail over if the embed service goes down.
Add a row to your vendor risk sheet tonight.
Schedule a brown bag so junior devs read the primary doc.
Flag if your CDN blocks GitHub asset domains.
Verify offline mode if embed jobs must stay on prem.
Check mobile latency, not just server latency.
Ask finance to model a three year embed cost curve.
Scan your asset list for affected serial numbers.
Run a tabletop exercise for spoofing on support tools.
Store proof of patch in your compliance folder.
Who is affected
Protocol engineers, wallet vendors, and custody teams should read the pq.ethereum.org tracker. Enterprise chains that fork Ethereum ideas should copy the test plan format.
Tell customer support what changed in plain words.
Update your public changelog if users will notice.
Review open source license files before you ship.
Check export rules if weights download cross border.
Measure error rates on edge devices, not only in the cloud.
Keep a hotfix branch ready during the patch window.
Review audit logs after you enable new camera keys.
Confirm manifest files rebuild cleanly in staging.
Test with low light photos if users snap selfies indoors.
Publish limits beside any score shown to users.
Offer an opt out if your app stores face vectors.
Record who signed off on the production change.
Ship a dark launch before you expose scores to all users.
Keep a public status page during the patch weekend.
What to do next
Audit whether your wallet roadmap mentions ML KEM or hash based backup keys. Schedule a briefing with your custody vendor on leanVM timelines.
Test on the oldest phone model your users still carry.
Add synthetic night photos to your eval set this sprint.
Revisit your data map after any new sensor field arrives.
Hold a red team hour on spoofed support sessions.
Budget two engineer days to rebuild stale manifests.
Share failure cases, not only success screenshots.
Pin exact docker tags in your reproducibility doc.
Refresh executive slides with sourced numbers only.
Close the loop with clinicians after any UI tweak.
What to watch
Photo: Pexels contributor / Pexels
Watch devnet notes after the Cambridge retreat and any NIST crosswalk posts from the EF team.
Photo: National Cancer Institute / Pexels
Sources
- Primary — Ethereum.org, Post quantum cryptography roadmap (updated April 2026). Retreat dates and milestones.
- Secondary — Ethereum Foundation, leanEthereum organization (2026). Open implementations list.
Related in Quantum
Continue reading