Many one-time signatures, one tree root
XMSS uses a Merkle tree to connect many one-time signing components to a compact public root. A signature includes the information needed to verify a message and authenticate its place under that root. RFC 8391 specifies WOTS+ as a building block, the single-tree XMSS construction and the multi-tree XMSS variant.
The structure lets one public root support a planned number of signatures. Tree height is therefore part of the signing design. It should not be confused with an unlimited ability to reuse each underlying one-time signing component.
Sources:RFC 8391: XMSS
The index is part of the secret-key workflow
The important operational rule is to consume a one-time signing index only once. Restoring an old wallet backup can restore an old view of which indexes have already been used. Two signing devices can also disagree about the next available index unless their operation is coordinated.
Our engineering interpretation is that recovery and concurrency belong in an XMSS deployment review alongside the primitive itself. A system should explain how it reserves an index, persists its use and handles interrupted signing. An offline signer needs a defined state-management procedure rather than an assumption that observing confirmed transactions is always sufficient.
Sources:RFC 8391: XMSSNIST SP 800-208
A concrete example: QRL
QRL documents XMSS and one-time-signature indexes as part of its transaction model. Its documentation distinguishes outgoing signing activity from receiving funds and explains how tree height determines the initial index capacity. This is a practical example of an algorithm property becoming a wallet responsibility.
Use the documentation for the relevant QRL network and wallet version before taking action. CoinTalk is not providing a recovery procedure or reporting a live wallet test here. The lesson for a reader comparing projects is to ask how each implementation exposes, tracks and protects its signing state.
What the specifications establish
RFC 8391 is an informational IRTF publication describing XMSS. NIST SP 800-208 recommends specified stateful hash-based schemes and parameter sets, including XMSS and LMS families, with requirements for their use. Their publication status and scope should be reported precisely.
Neither publication certifies a named cryptocurrency. A project may select parameters or an operating model that needs its own assessment. Our recommended evidence record includes the parameter identifier, hash function, key-generation implementation, state-protection design and source version. These details make the claim reviewable.
Sources:NIST SP 800-208RFC 8391: XMSS
Stateful versus stateless is an operating choice
SLH-DSA offers a standardized hash-based design without the same persistent one-time-index requirement. That does not make the two schemes interchangeable. Their structures, message overhead and operational assumptions differ, so a migration requires more than changing an algorithm label.
For a custodial service or personal wallet, model ordinary failure cases: a stale backup, a second device, a failed broadcast and a crash during signing. The resulting operational design is part of the deployment evidence. CoinTalk has not tested these scenarios for the projects discussed in this library.
Sources:NIST SP 800-208