Source finding: three precise specifications

NIST announced approval of FIPS 203, 204 and 205 on August 13, 2024. ML-KEM, derived from CRYSTALS-Kyber, supplies key encapsulation. ML-DSA, derived from CRYSTALS-Dilithium, and SLH-DSA, derived from SPHINCS+, supply digital signatures. These are different cryptographic functions within the same PQC standards milestone.

The announcement made precise standardized primitives available. It did not announce a universal blockchain transaction format, wallet recovery model or consensus upgrade. Reading the milestone accurately starts by retaining the distinction between key establishment and signing, then asking where each function is needed.

Sources:NIST: Approval of three PQC FIPSNIST FIPS 203: ML-KEMNIST FIPS 204: ML-DSANIST FIPS 205: SLH-DSA

CoinTalk analysis: names are version information

The relationship to a competition submission is useful history, but a predecessor name is not enough to identify the standardized behavior. For an implementation claim, ask which specification and parameter set the software follows. Record any project-specific changes instead of silently treating them as equivalent.

This matters when comparing chain profiles. A network describing a custom lattice-based signature may be pursuing a different construction from ML-DSA. A library implementing an earlier submission may also need changes. The standard publication records, including errata, are better anchors for implementation review than a shared family label.

Sources:NIST FIPS 203: ML-KEMNIST FIPS 204: ML-DSANIST FIPS 205: SLH-DSA

CoinTalk analysis: signatures need protocol rules

For on-chain signing, a protocol still needs to specify message contents, encoding, verification behavior, resource limits and activation rules. Wallets must produce valid transactions and handle key creation and recovery. Node operators need software that applies the same rules consistently.

Different signature choices can shift storage and computation costs among participants. A useful evaluation identifies the parameter set and test environment, then measures the actual integration. A standalone library benchmark does not establish network throughput, and a standard's availability does not show that a chain has accepted a new transaction type.

Sources:NCCoE migration project: discovery and interoperabilityBitcoin BIP 3: Updated BIP process

CoinTalk analysis: keep assurance claims scoped

Implementation review must consider the code and environment that use the primitive. Protecting secret keys, handling malformed inputs and checking correct outputs remain necessary. A finalized algorithm specification supplies a reference for this work; it does not perform that work on behalf of a project.

Likewise, NIST module validation is a separate process for an identified cryptographic module. An asset should not inherit a certification claim simply because its documents mention a FIPS algorithm. For readers, the useful result is a clear chain of evidence: standard, implementation, protocol integration and deployment, with unresolved steps stated explicitly.

Sources:NIST Cryptographic Module Validation ProgramNIST FIPS 204: ML-DSA