Source finding: an additional KEM selected
On March 11, 2025, NIST announced its selection of HQC for standardization after the fourth evaluation round. The announcement points to IR 8545 for the selection reasoning and describes a subsequent drafting and public-comment process. It identifies HQC as a second PQC key-encapsulation mechanism following ML-KEM.
This is a selection event, not the publication of a final HQC FIPS. The announcement's expected schedule should be read as the plan expressed at that time. A current implementation decision must check subsequent official publication records rather than turn that expectation into a guaranteed deadline.
Sources:NIST: HQC announced as a fourth-round selectionNIST IR 8545: Fourth-round status report
Source context: what key encapsulation supplies
A KEM establishes shared secret material under specified conditions. That material can be used within a protocol with symmetric cryptography to protect communication. NIST SP 800-227 explains the definitions and the care needed in implementing and using KEMs.
ML-KEM is the standardized module-lattice-based option defined in FIPS 203. HQC provides an additional code-based design direction. The cryptographic function remains key establishment. Neither name identifies the signature a node checks to decide whether a cryptocurrency transfer was authorized, and replacing a connection's key establishment does not itself alter transaction-validity rules.
Sources:NIST SP 800-227: Recommendations for KEMsNIST FIPS 203: ML-KEMNIST IR 8545: Fourth-round status report
CoinTalk analysis: locate a realistic integration point
A digital-asset ecosystem includes communication between wallets, servers, operators and other services. Those connections can have confidentiality and authentication requirements separate from on-chain spending. A KEM announcement may consequently be relevant to infrastructure research even when no coin changes its transaction signature.
The right next question is which protocol could use the mechanism, how peer identity is authenticated and what software supports the intended combination. Record those answers at the service or connection level. Describing the entire currency as quantum-resistant because one communication layer uses a KEM would obscure the remaining dependencies.
Sources:NIST SP 800-227: Recommendations for KEMsNCCoE migration project: discovery and interoperability
CoinTalk analysis: track the remaining milestones
For HQC, useful updates include a draft specification, public feedback, a finalized standard and reviewed implementations of the specified version. For an application, the follow-up milestones include interoperability, error handling, resource measurements and the actual rollout. These are related workstreams, but they need separate evidence.
Readers can use the HQC algorithm profile to follow that distinction and the signatures-versus-KEM guide to identify the relevant task. The selection broadens the research and standardization portfolio; whether an individual wallet, node connection or service benefits depends on its own integration and deployment decisions.
Sources:NIST: HQC announced as a fourth-round selectionNCCoE migration project: discovery and interoperability