Algorithm

XMSS

Family: hash-based.

XMSS signs messages with one-time keys that are organized under a single Merkle tree root, so one short public key covers many signatures. Each one-time key may be used once only, so the signer must record how many it has used. Signatures are small for a hash-based scheme. RFC 8391 specifies it, and NIST approves it for stateful use.

Safety: High

Security rests only on the properties of the hash function. The scheme is stateful: signing twice with the same one-time key reveals enough of that key's secrets for an attacker to forge signatures. A restored backup, a cloned device, or a crash before state is saved can cause this, so safe use needs strict state management.

https://www.rfc-editor.org/info/rfc8391

Spotted an error or a missing entry? Edit this registry on GitHub to open a pull request, or suggest a change in an issue.

Edit on GitHub Suggest a change