Becoming quantum ready

Quantum won't break your future. It will break your past. Quantum computers will break the maths behind most encryption, and with it every login, digital signature and sealed record that relies on it. The fix exists, and the deadlines are already set. This page shows what ready means today, who is exposed, and what a ministry should ask before it signs.

Get the full tech report as a free PDF

This page gives you the argument. The report carries the full detail.

What breaks and what holds, layer by layer
The regulatory clock from 2024 to 2035, date by date
Eight readiness questions for any procurement conversation

Enter your work email to unlock the download.

Quantum breaks the lock, not the seal

Most encryption today rests on two mathematical problems, factoring large numbers (RSA) and elliptic curves, which sign most internet traffic. Both are hard for normal computers and easy for a large enough quantum computer. Shor's algorithm proved this in 1994. The physical machine does not exist at that scale yet, but the maths has been settled for thirty years (AlphaX, 2026).

Breaks

RSA, elliptic curves and Diffie-Hellman. The maths behind logins, signatures and certificates.
Replace with the new NIST algorithms, ML-KEM and ML-DSA.

Holds

Hash functions, hash-chained ledgers and hash-based signatures. Weakened rather than broken.
Doubling the hash length restores the security margin, which makes a tamper-evident ledger among the most quantum-durable assets in a government stack.
Keep, and lengthen.

The fix is already published. In August 2024 NIST released three post quantum standards. FIPS 203 (ML-KEM) for exchanging keys, FIPS 204 (ML-DSA) for signatures, and FIPS 205 (SLH-DSA), a fallback signature scheme built on hashes if the first is ever compromised (AlphaX, 2026). Three things about these standards matter to a buyer.

They are software

A server update, a phone update, or a firmware update on a key store. No new hardware or satellite links are required.

They form the global reference

NIST standards become the default baseline for banks, browsers and governments. Chrome, Cloudflare and Apple already run ML-KEM in hybrid mode, pairing old and new algorithms.

They come with an end date

NIST's draft transition plan deprecates the weakest RSA and elliptic curve settings after 2030, and disallows all of them after 2035.

Quantum does not break the seal on a record. It breaks the lock on the key, and the pen that signed it.

The deadlines are set. The machine is not needed to meet them

Nobody knows when a quantum computer large enough will arrive. Governments stopped waiting for that answer and set hard dates on the cryptography instead (AlphaX, 2026).

2024

Standards

NIST publishes the three post quantum standards. They are software updates for any server or phone.AlphaX, 2026

2026

Transitions begin

Executive Order 14412, signed 22 June 2026, puts US federal high-value systems on the clock, and the EU's Coordinated Implementation Roadmap asks member states to start national transitions by end 2026. NIST also retires the older FIPS 140-2 certificates, a date often misread. It is not a post quantum deadline, and vendors citing 140-2 validation are offering a retired standard.AlphaX, 2026

2030

Key exchange

US high-value systems must run post quantum key establishment by 31 December 2030. EU high-risk systems move by 2030, and the weakest RSA and elliptic curve settings are deprecated.AlphaX, 2026

2031

Signatures

US high-value systems must run post quantum signatures by 31 December 2031.AlphaX, 2026

2035

End of classical

All classical options are disallowed under NIST's draft transition plan, and the EU asks member states to cover as many systems as feasible by 2035.AlphaX, 2026

$10.7MAfrican quantum investment in 2025.AlphaX, 2026

$245BGlobal quantum investment over the same period. Procurement choices will close that gap, not research budgets.AlphaX, 2026

10 to 15Years of working life for a national platform procured in 2026. It will be in active service on every date above.AlphaX, 2026

The question for a ministry is not whether a quantum computer arrives before 2035. It is whether a system bought this year can update its cryptography before then, and who holds the authority to make that change.

Quantum won't break your future. It will break your past

Quantum capability exposes governments in two distinct ways. The first gets most of the attention. The second carries far greater long term impact (AlphaX, 2026).

Harvest now, decrypt later

An adversary does not need a quantum computer today to cause damage. They only need storage. Encrypted network traffic is intercepted today, stored, and held until a suitable machine can open it. Citizen identity files, tax records, medical histories and diplomatic traffic are all targets.

The exposure window opens the day the data moves over the wire, not the day the quantum computer turns on.

Forge later

A signature proves that a document came from an authorized source and remains unaltered. When the maths behind that signature breaks, anyone with access to the computer can generate valid signatures under the ministry's identity for land titles, court orders, birth certificates or software updates. Every historic record becomes disputable.

A broken historical signature cannot be patched after the fact. The only fix is re-signing with post quantum algorithms while the classical maths still holds. That window is limited.

The three clocks of exposure

Record lifeHow long the record must stay valid.
Migration timeHow long system migration takes.
Machine arrivalHow long until a large quantum computer exists.

If the first two combined exceed the third, the record is already exposed. For a land title that must remain valid for fifty years, the record lifespan alone settles the question.

Old signatures do not become readable. They become reproducible.

The longer a record must last, the sooner it is at risk

Prioritize systems by how long data must stay valid, and how much traffic relies on legacy algorithms (AlphaX, 2026).

Long-lived signed records

Land titles, civil status, identity credentials, court orders and academic certificates stay valid for decades. Signed once, they are expected to hold authority indefinitely. They are the primary targets for signature reproduction, and they require re-signing before legacy maths breaks, managed by a signing authority the state controls.

Traffic recorded today

Mobile money, tax filings, healthcare data and routine network communications are the primary targets for current data capture. Sub-Saharan Africa conducts a larger share of its economy over mobile money than any other region, and every transaction relies on signatures and encryption that face deprecation within ten years.

Systems procured this year

A national system purchased in 2026 on classical cryptography, lacking a native migration mechanism, will remain in service long past the expiration of its underlying security. The procurement decision creates the exposure.

Bank regulators, land registries and identity authorities share a common problem. They issue records that must hold legal weight in 2050, evaluated by people who were not alive when those records were created (AlphaX, 2026). Identity systems face a second front as well, covered in our page on deepfake identity fraud.

Signed once. Trusted forever. That is the problem.

Three ways a ministry can meet 2035

Every government will arrive at 2035 through one of three operational approaches. Only one leaves the ministry in control of its data (AlphaX, 2026).

Path one. Wait for the vendor

Maintain current systems and request a post quantum upgrade as deadlines approach. The vendor dictates the price, schedule and scope. Records signed during the waiting period rely on algorithms scheduled for deprecation, and if the vendor shuts down or drops support, the path to an upgrade disappears.

Path two. Add external protection later

Place a post quantum encryption layer in front of a classical system. Network transport gets wrapped, but the underlying signatures and stored records remain unchanged. This addresses current data interception without solving historic signature reproduction, and every added proxy adds complexity for future maintainers.

Path three. Build crypto-agile today

Decouple algorithm selection behind a clean interface. Keep signing keys in hardware the state controls. Run classical and post quantum algorithms together during transition, matching standard browser implementations. When NIST updates its standards, update the configuration rather than replacing the platform, and re-sign historic archives on a schedule the ministry sets, using keys the ministry holds.

Path three requires higher initial procurement focus, but lowers ongoing costs over time. The unstated option is avoiding a decision entirely. That behaves exactly like path one, without explicit planning (AlphaX, 2026).

Change the configuration, not the platform.

What ready looks like in October 2026

Quantum readiness applies to individual components, not complete platforms. Each layer either runs post quantum cryptography today, or it does not. A vendor who cannot detail readiness layer by layer is not prepared, and a vendor claiming complete post quantum security is misleading you (AlphaX, 2026).

Running post quantum today

The application, credential, key management and data at rest layers of AlphaX Identity and Registry services.
NIST standards in production. ML-KEM for key exchange, with ML-DSA and SLH-DSA for signatures.
Keys reside in hardware security modules under client control. Algorithms sit behind an abstraction layer, so future updates are configuration changes rather than platform rebuilds.

In transition, named and dated

The ledger. Our rollup relies on Ethereum components, where base protocol cryptography is not yet post quantum. We align with the Ethereum Foundation's open roadmap targeting Layer 1 upgrades by 2029. The hash-chained ledger history remains durable against quantum attacks today.
Transport. Current deployments run standard TLS, and post quantum hybrid TLS will be enabled as sovereign customer networking environments stabilize. Payloads are already protected by application layer algorithms and zero knowledge design.

Transmitting less worth stealing is the other half of readiness. Zero knowledge proofs let a system verify age, residency, statutory rights or property ownership without taking custody of the underlying data. How that works is covered in our explainer on zero-knowledge proofs in identity verification.

"There is no need to wait for future standards." Dustin Moody, NIST, 13 August 2024

Questions to ask any vendor

Use these questions in any procurement conversation, including ours. Each warrants a clear, single-line answer. Extended explanations indicate technical gaps (AlphaX, 2026).

Which layers run post quantum today?

Name them explicitly.

Which layers do not?

Name them, and state the target deployment date.

Which NIST algorithms, and where?

Specify ML-KEM, ML-DSA, SLH-DSA, or custom alternatives.

Who holds the signing keys?

The ministry, the vendor, or an external party?

What happens when NIST updates its standards?

A configuration edit on our side, or a software rebuild?

Can we re-sign our archive independently?

What tools are required, and how long does execution take?

How much citizen data moves unnecessarily?

What attributes do you verify without transmitting raw records?

If our contract ends, what stays with us?

Which assets remain under ministry control?

Six concrete answers alongside two clear target dates show genuine progress. Complete claims of full readiness do not match reality in October 2026 (AlphaX, 2026).

If you leave, what leaves with you?

Questions readers ask next

Do quantum computers exist at the scale needed today?

No. Shor's algorithm proved the maths in 1994, but a machine large enough does not exist yet. Governments set deadlines on the cryptography anyway, because records signed today must stay valid long after the transition (AlphaX, 2026).

Does a hash-chained ledger break under quantum attack?

Hash functions are weakened rather than broken. A quantum computer makes them cheaper to attack, not trivial, and doubling the hash length restores the security margin. A tamper-evident, hash-chained ledger is among the most quantum-durable assets in a government stack (AlphaX, 2026).

What is harvest now, decrypt later?

Encrypted traffic is intercepted and stored today, to be opened when a suitable machine exists. Citizen identity files, tax records, medical histories and diplomatic traffic are all targets. The exposure window opens the day the data moves over the wire, not the day the quantum computer turns on (AlphaX, 2026).

What can a ministry do this year?

Two things. Inventory what is signed, what is stored and how long each must stay valid. Then mandate crypto-agile signatures, so the algorithm can be swapped from one place without the vendor. Old records can be re-signed in batches. New ones should stop adding to the pile (AlphaX, 2026).

Nobody can promise quantum safe in October 2026, and nobody needs to. Two things are within any ministry's reach this quarter. List what is signed, what is stored and how long each must stay valid. Then sign every new record with an algorithm chosen behind an interface, with keys in hardware the state controls. Everything else follows from those two.

The record must outlast the maths.

Becoming Quantum Ready tech report cover