The Quantum Countdown:
Is the Financial System Ready?

A blockchain can’t re-secure its past. It can adopt post-quantum cryptography going forward, but coins in exposed addresses, and every signature ever published, stay exposed forever. Permanence is the feature and the liability.

The clock that already started is harvest-now-decrypt-later, not Q-Day. The machine that breaks this is ~2030–2035 away, but anything recorded today that must stay secret for a decade is already in the window.

Three different things get called “quantum,” and they’re worth separating:

• Quantum computing is the machine. It’s the threat—and it’s not yet at useful scale.
• Post-quantum cryptography (PQC) is new mathematics that runs on ordinary computers and resists that machine. NIST finalized the standards in August 2024, and it’s deployable today.
• Quantum communications (QKD) uses physics itself to distribute keys. Real, but it needs dedicated hardware—and in space, dedicated satellites.

This is about the middle one: ordinary software you already use, upgraded so that what it protects today stays protected when quantum computers arrive.

What holds: AES, the encryption that actually scrambles data—on a satellite link, a hard drive, every HTTPS session. A quantum computer weakens it, but nowhere near enough to matter.

What breaks: the math for handing over keys and proving identity—RSA, Diffie-Hellman, elliptic curve. In practice, that’s the handshake that opens a secure connection, the signature on a software update, and the certificate that proves who you’re talking to.

Why now: because of the attack the industry calls “harvest now, decrypt later”—an adversary records encrypted traffic today and decrypts it in ten years, when the capability arrives. Anything transmitted now that must stay confidential into the 2030s is already exposed—migrating in 2032 won’t protect what was captured in 2026.

No, for three reasons.

1) The clock starts when data is created, not when the machine arrives. “Harvest now, decrypt later”—an adversary recording traffic today to decrypt when the machine exists—means anything that must stay secret for more than about five years is already inside the exposure window.

2) Hardware compresses the timeline further: spacecraft designed this year fly into the 2040s with the cryptography they launch with.

3) The deadline moved. The general federal target is 2035, but the DoD’s Post-Quantum Cryptography Strategy (June 2026) requires DoD systems to support PQC by the end of 2030 and employ it by the end of 2031, with CMMC requirements to follow for the industrial base. If your customer is a prime, your effective deadline is theirs—not 2035.

For half the problem, yes—and that half is largely fixed already. By late 2025, more than half of web traffic was post-quantum protected because browsers, servers, and CDNs upgraded by default. Nobody who benefited did anything.

No vendor can fix the rest. Post-quantum signatures are roughly forty times larger than the elliptic-curve ones they replace, which breaks size assumptions in certificate chains, firmware images, and narrow downlinks. A verification key burned into a chip at manufacture can’t be replaced without new hardware—on the ground that’s a recall; in orbit it’s a new launch. And as with Y2K, the expensive part is discovery: finding every place cryptography and sensitive data actually live.

The analogy also argues against waiting. Y2K was a non-event because roughly $100 billion was spent fixing it in the US alone—and it had a known date, and nothing about it was retroactive. This has an unpredictable date, an adversary, and a permanent cost: data captured today is permanently exposed, no matter how good the tools get later.

It is discussed, constantly, but in cryptography and national security circles rather than in operations and procurement. NIST runs a dedicated migration project, CISA and the NSA have published guidance, and the UK, German, French, and Dutch security agencies have all issued formal positions.

The real gap is between awareness and action. In ISACA’s 2025 survey, 62% of security professionals said they were worried quantum computing would break current encryption; only 5% had a defined strategy. The reasons are structural, not carelessness: nothing has visibly broken yet, the cost lands on this year’s budget while the benefit lands a decade out, and the first step—a cryptographic inventory—is expensive, invisible, and delivers a list of bad news.

In the space sector it’s quieter still, because security conversations focus on spacecraft and ground segments—so the layer where operators and suppliers exchange documents has no natural owner.

Each is ahead at something different, because each is pursuing a different strategy.

China leads decisively on quantum communications hardware: an operational quantum network reported at over 12,000 km, and the first quantum communication satellite (Micius, launched in 2016). No other nation has anything comparable. The EU is building an equivalent of its own, EuroQCI, whose first satellite—Eagle-1—is now expected in late 2027.

The US chose software over hardware. The NSA—like the UK’s NCSC and Germany’s BSI—does not recommend QKD for national-security systems and prefers post-quantum cryptography. And the US wrote the post-quantum standards (NIST FIPS 203, 204, and 205) that Europe and everyone else are now adopting.

The caveat: writing the standards is not the same as deploying them. Where the US is behind is deployment, not direction.

That depends on which of three tiers you’re in.

National security systems: CNSA 2.0 is binding—software and firmware signing first, new systems compliant on acquisition from 2027, broad milestones at 2030 and 2031.

Defense contractors and their supply chain: DFARS 252.204-7012 requires FIPS-validated encryption for controlled technical data, explicitly including information with space application, and ITAR governs technical-data transfers. CMMC’s Phase 2 assessment mandates were suspended in July 2026—but that paused an assessment deadline, not the underlying obligations, which still flow down to subcontractors.

Purely commercial operators: nothing binding yet. This reaches you through your customers’ contracts long before it reaches you through a regulator—if you sell to a prime, it arrives as a contract clause years before it arrives as a law.

Half of it is—which is where the confusion comes from. A blockchain’s hashing, the part that makes it tamper-evident, survives quantum computing. But its signatures—the mechanism that authorizes every transaction—are almost always ECDSA or EdDSA, elliptic-curve algorithms that are exactly what a quantum computer breaks.

A public ledger is actually worse-placed than most systems: every public key is published on-chain forever by design, history can’t be re-encrypted after the fact, and anyone can download the entire record today and hold it until quantum computers arrive.

The deeper point: immutability is not confidentiality. A blockchain proves a record hasn’t been altered; it keeps nothing secret. Chains can be made quantum-safe by replacing their signatures—but that’s a migration, like everywhere else, not a built-in property.

emedia is a digital transformation consulting company.

• We guide businesses in the adoption of frontier tech, from AI and post-quantum strategies to blockchain and tokenization.
• We also build custom enterprise software.

emedia is part of the founding team of SIX3RO, a startup in post-quantum decentralized secure information exchange.