A different basis for signatures

FIPS 205 specifies SLH-DSA, derived from SPHINCS+. It is a digital signature scheme built from hash-based constructions. This gives protocol designers a standardized signature option with a different foundation from the lattice-based ML-DSA family.

The useful distinction is the security assumption and construction, rather than a claim that one algorithm makes every application safer. A deployment must still identify its selected parameters, implementation and threat model. No algorithm name establishes the quality of a wallet or the correctness of consensus code.

Sources:NIST FIPS 205

What “stateless” changes

Stateful schemes such as XMSS need to ensure that a one-time signing component is never reused. SLH-DSA does not require the signer to maintain that same persistent consumed-index state between signatures. This is an important operational distinction for backup, recovery and multiple signing devices.

Stateless does not mean that a wallet can ignore nonces, transaction ordering, balances or secret-key protection. Those are application responsibilities. It describes a property of the signature algorithm, not the absence of state throughout the surrounding system.

Sources:NIST FIPS 205RFC 8391: XMSS

Trees and parameter choices

The SPHINCS+ reference project describes a collection of hash-based components, including WOTS+, FORS and a tree structure. It offers variants that trade signature size against signing effort. That background helps explain why “hash-based signature” covers constructions with quite different operating requirements.

The final SLH-DSA standard specifies SHA2- and SHAKE-based families and parameter variants. When comparing an implementation, preserve the full name, including the hash family and the small-signature or faster-signing variant. A benchmark or size taken from a different variant is not a measurement of the chosen deployment.

Sources:SPHINCS+ reference repositoryNIST FIPS 205

Questions before putting signatures on-chain

For a public blockchain, signature data has consequences beyond its transmission by one wallet. Nodes may relay it, retain it and verify it repeatedly. Our recommended assessment therefore includes transaction size, block capacity, verification budgets and the behavior of light clients or constrained devices.

Test the complete transaction format with representative and adversarial inputs. A protocol can set limits on accepted data and verification work; those limits need to match the selected construction. Avoid a universal “fastest algorithm” claim assembled from measurements made on unrelated processors or libraries.

Sources:SPHINCS+ reference repository

Read the standard and the code separately

FIPS 205 is a final standard published in August 2024. The SPHINCS+ repository is a useful reference to its predecessor research and software. Its configurable reference parameters should not be treated as permission to invent an incompatible SLH-DSA mode under the same standardized name.

For a project claiming support, ask which code release is used, which FIPS parameter name is accepted and where compatibility tests are recorded. CoinTalk has not run implementation benchmarks or performed a security audit for this entry. The comparison offered here concerns roles, evidence and integration questions.

Sources:NIST FIPS 205SPHINCS+ reference repository