What Is Post-Quantum Cryptography? The Complete Guide to How It Works, Why It Matters, and What You Need to Do Before 2030

Published by: QubitChain Research Hub
URL: qubitchain.io/blog/what-is-post-quantum-cryptography
Category: Education, Cryptography, Blockchain Security
Reading Time: Approximately 20 minutes
Last Updated: July 2026

What Is Post-Quantum Cryptography in One Sentence?

Post-quantum cryptography (PQC) is the field of designing and deploying cryptographic algorithms that remain secure against attacks from both classical computers and quantum computers, using mathematical problems that even the most powerful quantum hardware cannot solve efficiently.

That one sentence matters more today than at any point in the history of digital security. Here is why.

Introduction: The Encryption You Trust Is on a Countdown

Every time you send a message, authorize a transaction, log in to a bank account, or confirm a blockchain transfer, you are relying on encryption. Specifically, you are relying on the hardness of two mathematical problems: factoring large integers, and solving discrete logarithm equations. These two problems underpin RSA, ECDSA, ECDH, and Diffie-Hellman, the algorithms that protect the overwhelming majority of the world's digital communications and financial infrastructure.

For classical computers, these problems are hard in a very specific way: they require exponential time to solve. A classical supercomputer trying to break 2048-bit RSA encryption would need more time than the current age of the universe to succeed through brute force. This hardness is the foundation of modern digital trust.

Quantum computers change the equation completely.

In 1994, mathematician Peter Shor published an algorithm that solves both integer factorization and discrete logarithm problems in polynomial time on a quantum computer. Polynomial time means the problem gets manageable as the machine gets more powerful, not exponentially harder. A quantum computer running Shor's algorithm does not brute-force RSA. It solves the underlying mathematical structure that makes RSA hard in the first place.

This is not a theoretical concern in the same category as faster classical computers making encryption slower to break. Shor's algorithm is a categorical break. When a quantum computer with sufficient qubit count and quality exists, RSA, ECDSA, and every elliptic curve-based system in production becomes trivially breakable.

The answer to this problem is post-quantum cryptography: replacing the algorithms that quantum computers break with algorithms based on mathematical problems that quantum computers cannot solve efficiently, even in principle.

This guide covers everything you need to understand about post-quantum cryptography: the mathematical foundations, the specific algorithms NIST standardized in 2024, why the migration timeline is more urgent than most people realize, and what organizations and individuals need to do before the deadline arrives.

The Mathematical Foundations of Post-Quantum Cryptography

To understand post-quantum cryptography, you need to understand why some mathematical problems are quantum-resistant and others are not. The distinction is not about computational power. It is about mathematical structure.

Why Shor's Algorithm Breaks RSA and ECDSA But Not Everything

Shor's algorithm exploits periodicity. Integer factorization and discrete logarithm problems both have a hidden periodic structure that classical computers cannot efficiently detect but that a quantum computer can find using quantum Fourier transform operations. The quantum speedup comes specifically from the ability to detect this periodicity using superposition and entanglement.

Mathematical problems that do not have this exploitable periodic structure are not efficiently acceleratable by Shor's algorithm. The four main families of post-quantum cryptographic problems have been designed specifically around mathematical structures where no such periodic structure exists and no known quantum algorithm provides an efficient attack.

The Four Mathematical Families of Post-Quantum Cryptography

Lattice-Based Cryptography

This is the most important family and the one that NIST selected as the primary basis for its 2024 post-quantum standards. A lattice is a regular grid of points in very high-dimensional space, hundreds or thousands of dimensions. Lattice-based cryptography is built on the difficulty of two related problems.

The Learning With Errors (LWE) problem asks: given many noisy linear equations about a secret vector, can you recover the secret? Adding noise makes the system appear random to any algorithm that tries to solve it linearly, and the high-dimensional structure means brute force is infeasible.

The Shortest Vector Problem (SVP) asks: given a lattice, can you find the shortest non-zero vector it contains? In high dimensions, this is computationally intractable even for quantum computers. The best known quantum algorithms for lattice problems provide only modest speedups that are well within the security margins of correctly parameterized lattice schemes.

The security of ML-KEM (FIPS 203) and ML-DSA (FIPS 204), the two primary NIST 2024 standards, both rest on the Module Learning With Errors (MLWE) problem, a structured variant of LWE that allows efficient implementation while maintaining the core security properties.

Hash-Based Cryptography

Hash-based signature schemes derive their security entirely from the security of cryptographic hash functions. There is no algebraic structure to exploit, no periodic structure for quantum algorithms to detect. The security assumption is simply: can you find a collision or preimage in a well-designed hash function? Even quantum computers face only Grover's quadratic speedup against hash functions, which is addressed by using sufficiently long hash outputs.

SLH-DSA (FIPS 205), formerly SPHINCS+, is the NIST 2024 hash-based standard. Its security is the most conservative of the three NIST standards because it relies on the single assumption that the hash function is secure, with no other mathematical structures to worry about.

Code-Based Cryptography

Code-based cryptography builds on the difficulty of decoding a random linear code. This problem dates to 1978 (the McEliece cryptosystem) and has resisted cryptanalytic attacks for almost fifty years, both classical and quantum. The primary challenge historically was large key sizes, which made code-based schemes impractical for many applications. HQC, standardized by NIST in 2025, addresses this with a quasi-cyclic structure that dramatically reduces key sizes while preserving the security properties.

Isogeny-Based Cryptography

Isogeny-based schemes compute mappings between elliptic curves, with security based on the difficulty of finding these mappings. This family suffered a significant blow in 2022 when researchers broke SIDH (Supersingular Isogeny Diffie-Hellman), the leading isogeny-based candidate, using a classical algorithm. This is precisely the kind of cryptanalytic advance that makes cryptographic agility so important. Other isogeny-based schemes such as CSIDH are still considered potentially viable but are not yet in the NIST standard suite.

The Threat That Makes Post-Quantum Cryptography Urgent Right Now

The Harvest Now, Decrypt Later Problem

The most important thing to understand about post-quantum cryptography is that you do not need to wait for a quantum computer to exist before the threat becomes real. The threat is already active.

Adversaries do not need a working cryptographically relevant quantum computer today to compromise your encrypted traffic. They need a hard drive and patience. The technical name is Harvest Now, Decrypt Later (HNDL).

HNDL works like this: an adversary intercepts and stores encrypted data today, at scale, across millions of communications. The data is useless now because they cannot break the encryption. But once a sufficiently powerful quantum computer exists, every stored communication becomes readable. The encryption protecting that data was chosen years ago and cannot be retroactively upgraded.

For data with long-term sensitivity: government communications, healthcare records, financial transaction histories, intellectual property, and cryptocurrency blockchain data, the HNDL threat is not future risk. It is current risk. High-risk data categories include government secrets, financial data, healthcare records, and intellectual property with 10-plus year sensitivity.

For blockchain specifically, the HNDL threat is even more acute because blockchain data is public and immutable. Anyone can archive the entire Bitcoin or Ethereum blockchain today, permanently, at essentially zero cost. Every public key ever used on those networks is already harvested. The decryption happens later.

The Hardware Timeline That Makes This Urgent

Post-quantum cryptography transitions are estimated to take three to eight years for most organizations depending on organizational size and complexity. The process involves cryptographic inventory, risk assessment, architecture planning, hybrid deployment, and full migration with monitoring.

If CRQC capability arrives anywhere in the 2030 to 2035 window that intelligence agencies are projecting, organizations that have not started planning by 2026 face a real risk of missing the transition window.

Google's Willow chip, announced in December 2024, proved below-threshold quantum error correction at 105 qubits, confirming the engineering path to a CRQC is open with no fundamental physics barrier remaining. IBM's roadmap targets fault-tolerant quantum computing modules by 2027 and 100,000 physical qubits by 2033. Multiple independent quantum hardware programs in the United States, China, and Europe are converging on the same threshold.

The CRQC is not here yet. The post-quantum migration needs to be.

The NIST 2024 Post-Quantum Cryptographic Standards

In August 2024, NIST published the most important cryptographic standards since the introduction of RSA in 1977. After an eight-year public competition involving 82 submissions from cryptographers in 25 countries, NIST finalized three post-quantum cryptographic standards: ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205).

FIPS 203: ML-KEM (The Replacement for Key Exchange)

ML-KEM, the Module Lattice Key Encapsulation Mechanism, is the post-quantum replacement for RSA key exchange and Elliptic Curve Diffie-Hellman (ECDH). Every time your browser establishes a secure TLS connection, every time a VPN creates an encrypted tunnel, every time two blockchain nodes establish an encrypted communication channel, some form of key exchange is happening. ML-KEM is what those operations need to use to be quantum-safe.

ML-KEM is the primary standard for key encapsulation and key exchange. ML-KEM-512 provides NIST Security Level 1 equivalent to AES-128. ML-KEM-768 provides Security Level 3 equivalent to AES-192. ML-KEM-1024 provides Security Level 5 equivalent to AES-256.

The underlying mathematics is the Module Learning With Errors (MLWE) problem. The security assumption: given a noisy system of modular linear equations where the solution is a small-coefficient vector, recover the solution. No known quantum algorithm solves this efficiently. Shor's algorithm provides no speedup because there is no periodic structure to exploit.

Cloudflare, Google, and Apple have already deployed ML-KEM in hybrid TLS implementations, meaning a classical key exchange and an ML-KEM key exchange are performed simultaneously and both are required to succeed, extending hybrid post-quantum key exchange to billions of users. The migration is not theoretical. It is in production at the bottom of the internet stack.

FIPS 204: ML-DSA (The Replacement for Digital Signatures)

ML-DSA, the Module Lattice Digital Signature Algorithm, is the post-quantum replacement for ECDSA and RSA digital signatures. This is the most critical standard for blockchain security. Every Bitcoin transaction, every Ethereum smart contract call, every validator attestation on every Proof of Stake network is authorized by a digital signature. ML-DSA is what those signatures need to use to remain secure against quantum adversaries.

ML-DSA is the primary standard for digital signatures. It replaces RSA and ECDSA signatures for code signing, document signing, and authentication.

ML-DSA signatures are significantly larger than ECDSA signatures: approximately 2,420 bytes for ML-DSA-65 compared to 71 bytes for ECDSA-256. This size difference is the central engineering challenge for any system migrating from ECDSA to ML-DSA. For blockchain networks specifically, where block size and transaction throughput depend on signature sizes, this overhead must be designed around, not retrofitted.

QubitChain.io was designed from genesis with ML-DSA-65 signatures as the baseline. Block structure, throughput targets, and network bandwidth budgets were all calculated around 2,420-byte signatures. This is what quantum-native design means: the engineering decisions reflect the post-quantum reality from the beginning, not as a retrofit. See the full technical specification at qubitchain.io/whitepaper.

FIPS 205: SLH-DSA (The Hash-Based Backup)

SLH-DSA, the Stateless Hash-Based Digital Signature Algorithm, is the NIST 2024 backup signature standard. Unlike the lattice-based schemes, SLH-DSA relies only on the security of cryptographic hash functions, making it the most conservative choice. It produces larger signatures of approximately 8,000 bytes for the smallest security level but offers the advantage of having no known mathematical vulnerabilities beyond those of the underlying hash function.

The strategic importance of SLH-DSA is its mathematical independence from lattice-based schemes. ML-KEM and ML-DSA share the MLWE hardness assumption. If a future cryptanalytic breakthrough weakened that assumption, both would be affected simultaneously. SLH-DSA's security rests on an entirely different foundation: hash function security. A breakthrough against lattice problems would not affect SLH-DSA.

This is why cryptographic diversity at the protocol level matters. Systems that implement both ML-DSA as primary and SLH-DSA as backup have defense in depth at the mathematical level. QubitChain.io implements both.

HQC: The 2025 Fourth Standard

NIST also selected HQC for standardization in 2025, providing a code-based alternative that will be standardized for specific properties and use cases. HQC (Hamming Quasi-Cyclic) is a key encapsulation mechanism based on the hardness of decoding quasi-cyclic codes, a third distinct mathematical foundation from both lattice-based schemes and hash-based schemes. Adding HQC to the standard suite gives system designers a mathematically diverse fallback for key encapsulation independent of ML-KEM's MLWE assumption.

Who Needs Post-Quantum Cryptography and When

The Regulatory Mandate Landscape

The regulatory framework has moved far beyond voluntary adoption. The NSA's CNSA 2.0 mandate requires all U.S. national security systems to use quantum-safe algorithms for new systems by January 2027 and complete full migration by 2030. Federal agencies, defense contractors, and critical infrastructure operators are bound by this timeline.

The EU's post-quantum cryptography roadmap requires high-risk sector operators in finance, healthcare, and critical infrastructure to begin PQC transitions by end of 2026. ENISA coordinates migration guidance across all member states. MiCA-licensed crypto asset service providers face dual obligations: MiCA compliance and EU PQC alignment.

The UK NCSC, Germany's BSI, Singapore's MAS, Japan's NISC, Australia's ASD, and South Korea's ETRI have all published equivalent national guidance aligning on the NIST 2024 standard suite. Post-quantum cryptography has moved from a government research priority to a global regulatory baseline within the span of 18 months.

Which Organizations Face the Highest Urgency

The urgency of post-quantum migration is not uniform. It scales with two factors: how sensitive is the data, and how long does it need to stay protected?

Organizations facing the highest urgency right now include any entity transmitting or storing data that must remain confidential for more than five years, financial institutions processing transactions that are permanently recorded, government agencies handling classified or sensitive communications, healthcare providers maintaining long-term patient records, any operator of public blockchain infrastructure where historical transaction data is already publicly archived and unharvested by default, and technology companies whose intellectual property has decade-long commercial value.

Organizations that have not started planning by 2026 risk missing the CNSA 2.0 compliance deadline of 2030.

The Six-Step Migration Process

CISA, working jointly with NSA and NIST, has published a migration playbook. The standard migration framework:

Step 1: Cryptographic Inventory. Identify every place in your infrastructure where RSA, ECDSA, ECDH, or Diffie-Hellman is used. This means TLS certificates, SSH keys, code signing certificates, blockchain wallet keys, VPN tunnels, email encryption, and hardware security modules. Most organizations discover they use cryptographic algorithms in significantly more places than they knew.

Step 2: Risk Classification. Prioritize assets by HNDL exposure. Data that is already transmitted in encrypted form is at HNDL risk now. Data that needs to stay confidential for more than five years is at elevated risk. Internal communications and short-lived session data are lower priority.

Step 3: Cryptographic Agility Planning. Design your migration architecture to support multiple algorithms simultaneously. Cryptographic agility means your systems can switch algorithms without being rebuilt. This is the infrastructure investment that enables the actual migration rather than requiring a complete rebuild.

Step 4: Hybrid Deployment. Run classical and post-quantum algorithms in parallel. A hybrid TLS handshake using both ECDH and ML-KEM ensures security against both classical and quantum adversaries during the transition period. Validation of correct hybrid implementation before removing classical fallbacks prevents security gaps.

Step 5: Full Migration. Once hybrid deployment is validated, migrate to PQC-native implementations for new systems and gradually phase out classical cryptography. This phase is typically the longest, running 12 to 36 months for enterprise-scale infrastructure.

Step 6: Continuous Monitoring and Agility. Post-quantum cryptography is not a one-time migration. NIST will continue publishing new standards. The cryptographic landscape will evolve. Systems need ongoing cryptographic agility to absorb new standards and deprecate weakened ones without disruption.

Post-Quantum Cryptography and Blockchain

Blockchain infrastructure faces a uniquely severe version of the post-quantum cryptography problem because it combines three compounding factors that no other digital infrastructure shares.

Factor 1: Public key permanent exposure. Approximately 25 percent of Bitcoin's circulating supply sits in Pay-to-Public-Key (P2PK) addresses where the public key is permanently embedded on-chain. Every Ethereum address that has ever signed a transaction has its public key permanently recorded. There is no way to remove this data from the blockchain after the fact.

Factor 2: Immutable harvest surface. Classical infrastructure that is hacked or compromised can, in many cases, be migrated, re-encrypted, or isolated. Blockchain data is permanent and public by design. The harvest is complete. The question is only when the decryption happens.

Factor 3: Governance complexity of migration. Upgrading Bitcoin or Ethereum to ML-DSA signatures requires a community-wide hard fork, simultaneous wallet updates for tens of millions of users, and handling of dormant wallets that nobody can migrate. This coordination problem has no credible solution on the timescale required.

The only structurally sound solution to this combination of factors is what QubitChain.io represents: a blockchain built from its genesis block on the NIST 2024 post-quantum standard suite, with no classical cryptographic legacy to carry, no migration coordination problem to solve, and no HNDL exposure accumulating from day one of operation.

See how every major blockchain compares on quantum security at qubitchain.io/compare. Read the full Q-Day threat analysis at qubitchain.io/q-day.

The Most Common Misconceptions About Post-Quantum Cryptography

Misconception 1: Post-quantum cryptography is the same as quantum cryptography. These are fundamentally different things. Post-quantum cryptography uses classical mathematical algorithms running on classical computers that happen to resist quantum attack. Quantum cryptography (or Quantum Key Distribution, QKD) uses actual quantum hardware to distribute encryption keys. PQC is software. QKD is hardware. NIST standardized PQC, not QKD, as the primary solution for quantum-safe security.

Misconception 2: AES-256 is already quantum-safe, so we do not need to do anything. AES-256 symmetric encryption is considered quantum-safe because Grover's algorithm only halves its security from 256-bit to 128-bit, leaving it operationally secure. However, AES-256 only encrypts data. It does not authenticate identities, sign documents, or establish keys. All of those functions use asymmetric cryptography (RSA, ECDSA, ECDH), which is completely broken by Shor's algorithm. AES-128 would offer only 64-bit quantum security and is not recommended for long-term use.

Misconception 3: We can wait until quantum computers actually arrive to migrate. This is the most dangerous misconception. The HNDL threat means data encrypted or recorded today is at risk on Q-Day regardless of when you migrate. The three-to-eight-year migration timeline means the migration needs to begin well before Q-Day arrives. And the CNSA 2.0 deadline of 2030 is a regulatory compliance date, not a suggestion.

Misconception 4: Post-quantum algorithms are unproven and risky to deploy. The NIST 2024 standards are the product of an eight-year public competition with global participation from the world's top cryptographers. ML-KEM and ML-DSA have been subjected to more cryptanalytic scrutiny than most widely deployed classical algorithms received before adoption. The risk of deploying them is significantly lower than the risk of not deploying them.

Misconception 5: Only governments need to care about this. Any organization whose customers trust it with data that needs to remain confidential, any organization that signs code or documents, any developer who generates key pairs for users, and any individual who holds digital assets is affected by the post-quantum transition.

The Future of Post-Quantum Cryptography

Post-quantum cryptography is not a transition event with a completion date. It is a shift in how cryptographic infrastructure is designed and maintained.

NIST is already developing additional post-quantum signature standards. The Falcon digital signature algorithm (FN-DSA) and the HQC key encapsulation mechanism were selected for ongoing standardization in 2025. FN-DSA (Falcon) produces significantly smaller signatures than ML-DSA (approximately 1,280 bytes vs. 2,420 bytes for comparable security levels), which will make it attractive for applications where signature size is a critical constraint.

The principle of cryptographic agility, the ability to swap cryptographic algorithms at the infrastructure level without rebuilding systems, is becoming a fundamental design requirement rather than an optional feature. Organizations that build cryptographic agility into their systems now will be able to absorb future NIST standards and respond to future cryptanalytic advances without the kind of disruptive forklift upgrades that characterize the current classical-to-PQC transition.

For blockchain infrastructure, cryptographic agility is especially important. QubitChain.io's modular cryptographic engine incorporates it at the protocol level, allowing algorithm transitions through governance-approved parameter updates with no hard fork required. When future NIST standards are published, QubitChain.io absorbs them through governance rather than through the coordination catastrophe that algorithm changes require on classical networks.

Read the full roadmap and cryptographic agility architecture at qubitchain.io/whitepaper.

Frequently Asked Questions

Q: What is post-quantum cryptography?

A: Post-quantum cryptography (PQC) refers to cryptographic algorithms designed to be secure against attacks from both classical and quantum computers. Unlike RSA and ECDSA which are broken by Shor's algorithm on a quantum computer, PQC algorithms are based on mathematical problems such as the Module Learning With Errors problem in lattices, hash function security, and linear code decoding that have no known efficient quantum attack. NIST standardized three PQC algorithms in August 2024: FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA).

Q: Why do we need post-quantum cryptography now?

A: Post-quantum cryptography is needed now because of the Harvest Now Decrypt Later (HNDL) threat: adversaries are already archiving encrypted data today for decryption once a quantum computer exists. For data that needs to stay confidential for more than 5-10 years, this represents a current threat. Additionally, the NSA CNSA 2.0 mandate requires all new U.S. national security systems to use PQC by January 2027, and full migration by 2030. Migration takes 3-8 years, meaning organizations that have not started planning by 2026 risk missing the compliance deadline.

Q: What is the difference between post-quantum cryptography and quantum cryptography?

A: Post-quantum cryptography (PQC) uses classical mathematical algorithms running on classical computers that happen to resist quantum attack. It is software-based. Quantum cryptography, also called Quantum Key Distribution (QKD), uses actual quantum hardware to distribute encryption keys using quantum mechanical properties. PQC is a software upgrade that can run on existing infrastructure. QKD requires specialized fiber-optic or satellite hardware. NIST standardized PQC (not QKD) as the primary quantum-safe security solution.

Q: What are the four families of post-quantum cryptographic algorithms?

A: The four main families are: (1) Lattice-based cryptography, based on problems like Module Learning With Errors (MLWE), the foundation of ML-KEM and ML-DSA; (2) Hash-based cryptography, based on hash function security, the foundation of SLH-DSA; (3) Code-based cryptography, based on linear code decoding problems, the foundation of HQC; (4) Isogeny-based cryptography, based on mappings between elliptic curves, though the primary candidate SIDH was broken in 2022 and this family is not yet in the NIST standard suite.

Q: What is ML-KEM and what does it replace?

A: ML-KEM (Module Lattice Key Encapsulation Mechanism), standardized as NIST FIPS 203 in August 2024, replaces RSA key exchange and Elliptic Curve Diffie-Hellman (ECDH) for key establishment. It is based on the Module Learning With Errors (MLWE) problem and has no known efficient quantum attack. ML-KEM provides three security levels: ML-KEM-512 (equivalent to AES-128), ML-KEM-768 (AES-192), and ML-KEM-1024 (AES-256).

Q: What is ML-DSA and what does it replace?

A: ML-DSA (Module Lattice Digital Signature Algorithm), standardized as NIST FIPS 204 in August 2024, replaces ECDSA and RSA digital signatures. It is the post-quantum standard for authenticating identities, signing transactions, and verifying digital documents. ML-DSA signatures are approximately 2,420 bytes for the ML-DSA-65 parameter set, compared to 71 bytes for ECDSA-256. This size difference is the central engineering challenge for systems migrating from ECDSA to ML-DSA.

Q: Is AES-256 post-quantum secure?

A: Yes, AES-256 is considered post-quantum secure for symmetric encryption. Grover's algorithm halves its effective security from 256-bit to 128-bit, which remains far beyond practical brute-force capability. However, AES-256 only encrypts data. It does not sign documents, authenticate identities, or establish keys. All of those functions use asymmetric cryptography (RSA, ECDSA, ECDH) which is completely broken by Shor's algorithm. The post-quantum migration requirement is for asymmetric cryptography, not AES.

Q: How long does post-quantum cryptography migration take?

A: Enterprise PQC migration typically takes 3-8 years depending on organizational size and complexity. The process includes cryptographic inventory and discovery (2-6 months), risk assessment and prioritization (1-3 months), architecture planning and cryptographic agility design (3-6 months), hybrid deployment and testing (6-18 months), and full migration with continuous monitoring (12-36 months). Organizations that have not started planning by 2026 risk missing the CNSA 2.0 compliance deadline of 2030.

Q: What is cryptographic agility and why does it matter for post-quantum cryptography?

A: Cryptographic agility is the ability to swap cryptographic algorithms at the infrastructure level without rebuilding systems. It matters for post-quantum cryptography because NIST will continue publishing new standards, and future cryptanalytic advances may require algorithm transitions. Systems with cryptographic agility can absorb new standards through configuration changes rather than full rebuilds. For blockchain, cryptographic agility is especially important: QubitChain.io builds it into the protocol itself, allowing algorithm transitions through governance-approved parameter updates with no hard fork required.

Q: Why does blockchain specifically need post-quantum cryptography from genesis?

A: Blockchain faces uniquely severe post-quantum risk because: (1) public keys are permanently exposed on-chain after the first transaction, creating an unharvested-by-default HNDL surface; (2) blockchain data is immutable and public, meaning the entire harvest is already complete; (3) upgrading existing blockchains requires contested community-wide hard forks with no credible execution timeline, especially given that ML-DSA signatures are 34 times larger than ECDSA signatures. The only structurally complete solution is a blockchain built natively on NIST PQC standards from genesis block one, which is what QubitChain.io is.

References

* NIST FIPS 203: Module-Lattice-Based Key-Encapsulation Mechanism Standard (August 2024). csrc.nist.gov/pubs/fips/203/final * NIST FIPS 204: Module-Lattice-Based Digital Signature Standard (August 2024). csrc.nist.gov/pubs/fips/204/final * NIST FIPS 205: Stateless Hash-Based Digital Signature Standard (August 2024). csrc.nist.gov/pubs/fips/205/final * NSA CNSA 2.0 Cybersecurity Advisory (September 2022). media.defense.gov * CISA Post-Quantum Cryptography Initiative (2023). cisa.gov/quantum * Shor, P.W. (1994). Algorithms for Quantum Computation. Proceedings of the 35th Annual Symposium on Foundations of Computer Science. * NIST IR 8547: Transition to Post-Quantum Cryptography Standards (2024). csrc.nist.gov * Bernstein, D.J. and Lange, T. (2017). Post-Quantum Cryptography. Nature 549, 188-194. * QubitChain.io Technical Whitepaper v2.0 (2026). qubitchain.io/whitepaper * Webber et al. (2022). The Impact of Hardware Specifications on Reaching Quantum Advantage in the Fault-Tolerant Regime. AVS Quantum Science.