NIST IR 8610: What 9 Additional PQC Signature Candidates Change

Bottom line: this is a standards-maturity update, not another Q-Day clock

NIST IR 8610 does not say quantum computers will break today’s public-key cryptography by a specific date. It says something narrower: NIST is still evaluating additional post-quantum digital signature schemes, and 9 candidates have moved into a third round.

Read it beside Google’s 2029 post-quantum cryptography timeline, but do not collapse the two signals into one claim. Google’s 2029 date is a company migration target; NIST IR 8610 is a standards-process update about additional digital signatures.

That distinction matters because PQC headlines tend to collapse several ideas into one anxious question: “Is Q-Day now scheduled?” The safer reading is more practical. Approved standards, additional candidates, vendor roadmaps, and migration targets are different kinds of evidence.

My working rule would be simple: do not rewrite a migration plan because of IR 8610 alone. Do update the labels you use when reading PQC claims.

What happened in NIST IR 8610

NIST IR 8610 summarizes the second round of NIST’s additional post-quantum digital signature process. NIST moved 9 of 14 second-round candidates into a third round: FAEST, HAWK, MAYO, MQOM, QR-UOV, SDitH, SNOVA, SQIsign, and UOV.

That list matters because digital signatures sit inside trust infrastructure: certificates, code signing, document signing, firmware updates, identity systems, and authentication workflows.

A signature algorithm is not just a mathematical object. It has to fit systems that care about signature size, public-key size, signing cost, verification cost, implementation risk, side-channel resistance, and deployment constraints.

The easy mistake is to hear “NIST advanced a candidate” and translate it into “this is now the standard.” IR 8610 does not support that leap.

Evidence level

Source	What it supports	What it does not support
NIST IR 8610	NIST is continuing to evaluate additional digital signature candidates, with 9 advancing to a third round	The candidates are final standards
NIST FIPS announcement	NIST approved FIPS 203, FIPS 204, and FIPS 205 in 2024	Every system has already migrated to those standards
NIST NCCoE migration FAQ	Migration planning involves discovery, inventory, risk management, testing, and validation	A single universal private-sector deadline exists for all systems
Google PQC timeline	Google introduced a 2029 PQC migration timeline	2029 is proven to be the year current public-key cryptography breaks

IR 8610 is official NIST process evidence. It is not a product deployment announcement, a validation certificate, or a quantum hardware forecast.

What does not change: FIPS 204 and FIPS 205 remain the approved signature standards in this source set

NIST’s 2024 announcement approved three post-quantum FIPS standards. FIPS 203 covers ML-KEM for key encapsulation. FIPS 204 covers ML-DSA for digital signatures. FIPS 205 covers SLH-DSA for digital signatures.

IR 8610 should not be read as a quiet reversal of FIPS 204 or FIPS 205. The report describes additional algorithms that could complement the existing signature portfolio, including FIPS 204, FIPS 205, FIPS 186-5, and SP 800-208.

That matters in procurement and engineering conversations. If a tool claims “post-quantum signature support,” the follow-up question should be specific: which standard, which implementation, what validation path, and what deployment status?

What does change: the future signature portfolio is still open

IR 8610 changes how to interpret post-quantum signature news. It shows that NIST’s work on signatures is not finished just because initial standards exist.

That is normal for infrastructure-grade cryptography. One standardized option may fit many cases, while additional schemes are explored for different tradeoffs.

Some systems care intensely about small signatures. Others care about small public keys, fast verification, conservative assumptions, or implementation simplicity. The report’s evaluation categories point in that direction: security, cost and performance, and algorithm and implementation characteristics all affect whether a signature scheme can become useful in real systems.

How to read the 9 third-round candidates

The 9 candidates advanced in IR 8610 are FAEST, HAWK, MAYO, MQOM, QR-UOV, SDitH, SNOVA, SQIsign, and UOV.

For a general technical reader, the useful move is not to memorize every acronym. The better move is to classify the claim being made about any candidate.

Claim you may see	Safer interpretation
“Advanced to the third round”	Still under NIST evaluation, not yet an approved FIPS standard
“Promising signature size or performance”	Interesting, but check the exact evaluation context before comparing it with deployed standards
“Post-quantum signature candidate”	Candidate status is not the same as validation, interoperability, or broad product support
“Could complement existing standards”	Potential future portfolio role, not a reason to abandon FIPS 204 or FIPS 205 planning

This is where I would slow down in a vendor briefing. A roadmap slide can make candidate status sound close to availability. Standards status, product support, testing, and validation are separate checkpoints.

Where Google’s 2029 timeline fits, and where it does not

Google’s March 2026 PQC timeline remains relevant background because it shows how a large technology company is treating post-quantum migration as operational work. But your decision should not treat that date as a countdown to a confirmed cryptographic break.

The Google date is not a Q-Day prediction. It is a migration target. IR 8610 is also not a Q-Day prediction. It is about additional digital signatures that may shape the future standards portfolio.

For most readers working from the sources here, the clean split is this: approved NIST standards guide current standards-aware planning, while IR 8610 candidates are watchlist items for future signature options.

Decision frame for engineers, buyers, and policy readers

If you are comparing PQC signature claims, use four questions before treating a claim as actionable.

Question	Why it matters
Is this an approved FIPS standard or an additional candidate?	Approved standards and candidates sit at different maturity levels
Is the claim about signatures, key establishment, or both?	FIPS 203, FIPS 204, and FIPS 205 solve different cryptographic jobs
Is there a validation or testing path?	Product support language is not the same as validated deployment readiness
Is the algorithm being positioned as replacement, complement, or experiment?	IR 8610 supports additional evaluation, not a blanket replacement story

The practical friction point is that security planning often happens through mixed documents: standards memos, vendor roadmaps, cloud platform notes, compliance language, and internal migration spreadsheets.

IR 8610 helps because it lets you label one slice of that pile correctly. These are additional signature candidates in a standards process, not approved replacements and not evidence that a cryptographic break date has been found.

What remains uncertain

IR 8610 does not say which, if any, of the 9 third-round candidates will become future standards. It also does not settle how vendors will implement them, how validation will proceed, or which candidates will prove attractive for specific deployment settings.

It also does not remove broader uncertainty around the timing of cryptographically relevant quantum computers. The NIST NCCoE migration FAQ treats CRQC timing estimates as varied, which is why migration planning is framed as risk management rather than date prediction.

That uncertainty is not a reason to ignore signature migration. It is a reason to avoid false precision.

What to watch next

The next useful signals are standards-process updates, implementation evidence, validation paths, and actual product deployment plans.

IR 8610 gives two concrete process markers. Third-round package updates are due August 14, 2026, and NIST plans another PQC Standardization Conference in the first half of 2027.

On the NIST side, watch whether the third-round discussion changes the security analysis, performance tradeoffs, implementation characteristics, or standardization direction for the additional digital signature candidates.

On the planning side, keep FIPS 204 and FIPS 205 separate from the IR 8610 candidates in your notes. That one distinction prevents a lot of confusion: approved standards can shape current migration work, while additional candidates may shape the future signature portfolio.