Q-Day, PQC, and Why RE Built on a Protocol, Not a Product
Quantum Computers Will Break Encryption by 2029. RE's Evidence Layer Was Designed to Survive It.
On March 25, Google's VP of Security Engineering Heather Adkins published a timeline that should concern every developer building on cryptographic trust: Google now expects Q-Day — the moment quantum computers can break current encryption standards — to arrive by 2029.
This isn't speculation. Google is accelerating its own migration to post-quantum cryptography (PQC) ahead of the NSA's 2031 target. Android 17 will ship with ML-DSA, a quantum-resistant digital signature algorithm. Chrome already supports post-quantum key exchange. Google is telling the industry: the threat is real, and it's closer than you planned for.
The specific danger is called "harvest now, decrypt later." Adversaries intercept encrypted data today and store it, waiting for quantum computers to unlock it later. Every encrypted communication sent today with classical cryptography is a future liability. Every signed record using RSA or ECDSA has an expiration date that just moved up.
Why this matters for AI governance — and for RE:
RE's evidence chain is cryptographically signed. Every session log, every thought signature, every policy decision is serialized as an RFC 5322 email object — timestamped, hash-chained, stored in the user's inbox. The integrity of that chain depends on the cryptographic signatures being unbreakable.
If quantum computers can forge those signatures, someone could alter the evidence chain and produce valid-looking hashes. The append-only guarantee fails. The tamper-evidence fails. The entire audit trail becomes unreliable.
This would be a critical vulnerability — if RE had built its own cryptographic infrastructure.
It didn't.
In Update #2, we explained why RE uses email as its evidence layer: "What already exists, already works, and already won't go away?" SMTP was born in 1982. It has survived every technology cycle for over four decades. Not because email is elegant. Because email is a protocol — and protocols don't die. They evolve.
SMTP added TLS for encryption. Added DKIM for sender verification. Added SPF for domain authentication. Added S/MIME for end-to-end signing. Each upgrade was layered onto the same bones. The protocol absorbed every security advance without breaking backward compatibility.
PQC will be the next layer.
Google, Microsoft, and Apple — the companies that operate email infrastructure for billions of users — are the ones with the strongest incentive to upgrade email's cryptographic stack before Q-Day. Their users' bank statements, legal correspondence, medical records, and business contracts all live in email. They cannot afford to let quantum computers compromise that infrastructure. They will upgrade it. They are already upgrading it.
When Gmail migrates S/MIME to ML-DSA, every RE evidence email stored in a user's Gmail archive inherits quantum-resistant signatures. RE doesn't need to implement PQC. RE doesn't need to swap algorithms. RE doesn't need to touch a line of code. The infrastructure RE sits on gets upgraded by the largest technology companies on earth, at their expense, on their timeline.
This is not an accident. This is the architectural thesis.
In Update #7, we wrote: "The model died. The protocol didn't." Gemini 3 Pro was retired. RE kept running. The lesson was: build on protocols, not products. Products have lifecycles. Protocols have upgrades.
Update #9 is the same lesson at a deeper layer. Models are the variable. The evidence protocol is the constant. And now: classical cryptography is the variable. The email protocol is still the constant.
A project that builds its own evidence database has to implement its own PQC migration — hire cryptographers, swap algorithms, re-sign every historical record, and hope they don't make a mistake. A project that builds on email delegates that problem to the largest, most motivated, most heavily regulated infrastructure operators in the world.
In Update #2, we called this "infrastructure that should outlive its creator." We meant it literally. If RE's developer disappears tomorrow, the evidence chain doesn't depend on him. It depends on email. And email will still be here when quantum computers arrive — upgraded, quantum-resistant, and maintained by companies whose survival depends on it.
RE doesn't make AI quantum-proof. RE makes AI answerable — on infrastructure that other people are making quantum-proof.
Build on protocols. Let products come and go.
Source: Google, "Quantum frontiers may be closer than they appear," The Keyword, March 25, 2026. https://blog.google/innovation-and-ai/technology/safety-security/cryptography-migration-timeline/
— Che, Solo developer, Project RE, Taipei Taiwan
Log in or sign up for Devpost to join the conversation.