The same job as a KEM, a different foundation

HQC stands for Hamming Quasi-Cyclic. Its designers describe a code-based key-encapsulation mechanism whose security is based on the difficulty of quasi-cyclic syndrome decoding. The construction provides shared key material; it is not a method for producing publicly verifiable transaction signatures.

This distinction matters when reading cryptocurrency claims. A project discussing HQC may be evaluating a communication layer or another key-establishment service. That statement does not identify the algorithm that authorizes asset transfers. An evaluation should name both the protected service and its actual cryptographic role.

Sources:HQC designersNIST SP 800-227

Why an additional KEM matters

NIST selected HQC for standardization in March 2025 after the fourth round of its process. The announcement describes it as an additional KEM following ML-KEM. A code-based construction offers an alternative foundation to a module-lattice construction.

Our interpretation for system planning is that algorithm diversity can support contingency choices. It is not a guarantee against future cryptanalysis, nor a reason to install several algorithms without a protocol design. A migration plan should explain what would trigger a change, how implementations would interoperate and how older peers would be handled.

Sources:NIST HQC selection announcement

Selected is a distinct publication stage

The NIST process page checked for this entry lists HQC as selected for standardization. Its selection announcement describes a subsequent drafting and public-comment process. We therefore label this entry “selected; standard in development” rather than assigning it a final FIPS number.

For a technical review, record the specification revision and implementation release. Research software, a draft and a future final standard can differ. Do not silently update an old implementation claim when terminology changes; check the actual code and compatibility evidence for the new revision.

Sources:NIST HQC selection announcementNIST PQC standardization process

Measure the relevant exchange

The designers publish sizes for encapsulation keys, decapsulation keys, ciphertexts and shared secrets, with performance measurements tied to a specified implementation and processor. These categories are appropriate for a KEM. A ciphertext-size column should not be relabeled as signature size.

Our recommended integration review measures the complete handshake: transmission, parsing, memory, key derivation and error behavior. A wallet connection on a constrained network can face different tradeoffs from a persistent server-to-server channel. CoinTalk has not run an HQC benchmark, and this entry does not rank it against ML-KEM by speed.

Sources:HQC designers

From a candidate library to a service

KEM guidance treats key establishment as part of a surrounding protocol. Authentication and secure use of the resulting key material remain necessary. The mere presence of HQC code does not show that an application negotiates it, requires it or protects against an unwanted fallback.

A useful project record therefore identifies the network service, peer-authentication method, supported algorithm version and deployment stage. Mark research, testing and production separately. That makes it possible to follow future standardization without implying that a chain has already completed a transaction-signature migration.

Sources:NIST SP 800-227