Identify the network before identifying the algorithm

QRL is useful as a case study because post-quantum signing is part of the documented transaction system, rather than only a future migration objective. Its existing user documentation describes XMSS wallets and the handling of one-time signature indexes. That is a narrower, more inspectable claim than saying every component of a cryptocurrency is quantum-proof.

The project also develops a successor stack. Its documentation links to a Zond test environment, while the newer cryptographic library discusses both legacy address compatibility and newer signing types. This profile therefore keeps the existing XMSS network separate from successor development. A feature present in a new library does not establish activation on the existing chain.

Sources:QRL documentationQRL go-qrllib implementation notes

A reusable address is built from one-time signing keys

XMSS combines one-time signatures with a Merkle-tree authentication structure. The public commitment can authenticate many individual signing keys, but each underlying one-time key has a strict usage condition. This explains how an address can be used repeatedly without making the individual one-time key reusable. The signature authenticates a message and its position in that structure.

For the chain documented by QRL, outgoing transactions consume signing indexes. Receiving a payment does not consume an index at the receiving address. The available capacity depends on the tree selected when the wallet is created. Capacity and key-state management belong in any comparison with stateless signatures, alongside transaction size and verification cost.

Sources:RFC 8391: XMSSQRL one-time signature keys

Backups and concurrent signers must preserve signing history

The practical requirement is to avoid signing different messages with the same one-time index. QRL warns that index reuse should be treated as compromise. Restoring an old wallet copy or allowing two devices to sign independently can create an operational problem even when neither device loses its seed. A private-key backup and accurate signing state serve different purposes.

A useful wallet review consequently examines recovery, failed broadcasts, offline signing, and coordination between devices. Operators need to know which indexes have already been exposed, including signatures that may have left the device without reaching a confirmed block. These are review questions arising from the stateful design, rather than a claim that this article has tested a particular wallet release.

Sources:QRL one-time signature keysRFC 8391: XMSS

Standard names and deployed compatibility are different evidence

NIST SP 800-208 recommends specified stateful hash-based schemes, including XMSS. It is not a FIPS certificate for the QRL network. More importantly, the current go-qrllib provenance notes explicitly distinguish its legacy XMSS implementation from a general RFC-compatible implementation and from later SP 800-208 refinements.

The library explains that some legacy choices are retained to avoid changing keys derived from existing seeds. Compatibility can be necessary for an operating network, but it makes precise parameter and version identification essential. The defensible description is that QRL documents a particular XMSS-based system; compliance with a later specification requires a separate, implementation-specific assessment.

Sources:NIST SP 800-208QRL go-qrllib implementation notes

What a deeper deployment review would add

This review reads official documentation and implementation notes. It does not run a QRL node, replay the chain, verify a wallet binary, or establish the current activation state of a successor network. The reviewed date records when the sources were checked, not the date of an independent security audit.

The next evidence to collect would be a named network and release, accepted transaction formats, wallet recovery behavior, and audits scoped to that exact implementation. Separately inspect exchange custody, bridges, update signing, and administrative access. An XMSS transaction signature answers who authorized a transaction under the scheme; it does not answer every question about software delivery, consensus, or custody.

Sources:QRL documentationQRL go-qrllib implementation notes