Guides

QRL vs Algorand: how their quantum resistance compares

Kevin Castro
Postquant Labs
·3 min read

QRL has signed every mainnet transaction with XMSS, a hash-based post-quantum signature scheme, since its network launched on June 26, 2018. Algorand accounts use Ed25519 by default, and holders opt into Falcon-1024 lattice signatures, through contract accounts since 2025 and through native accounts from August 2026.

The two chains side by side

QRL Algorand
Post-quantum scheme XMSS with W-OTS+ (QRL docs) Falcon-1024 (Algorand brief)
Math it rests on Hash functions Lattices
Default account signature XMSS on every address Ed25519, 64 bytes (roadmap)
Post-quantum signature size 2,500 bytes at the default tree height (computed below) 1,280 bytes (falcon-sign.info)
Signatures per key 1,024 at the default height, fixed at creation (QRL docs) No one-time limit
State the holder must track Every spent one-time key index None

Signature size per transaction

The 2,500-byte figure comes from the XMSS formula in RFC 8391, section 4.1.8. An XMSS signature holds a 4-byte index, an n-byte random value, and (len + h) hash values of n bytes each, with h as the tree height. The RFC's 32-byte parameter sets use n = 32 and len = 67. At QRL's default height of 10:

4 + 32 + (67 + 10) × 32 = 2,500 bytes

Each extra level of tree height doubles the signatures an address can make and adds 32 bytes to every signature. Height 8 gives 256 signatures at 2,436 bytes each. Height 16 gives 65,536 signatures at 2,692 bytes, and height 18 gives 262,144 signatures at 2,756 bytes.

A default QRL signature comes to about 39 times the size of a 64-byte Ed25519 signature. A Falcon-1024 signature on Algorand comes to 20 times. The QRL repository describes its transactions as about 3 KB each, which fits the computed signature plus transaction fields.

Key management

An XMSS key holds a fixed supply of one-time keys. The QRL docs list these rules for QRL addresses:

  • Each one-time key index signs once. Nodes reject a transaction using an index a second time.
  • An address created at height 10 can send 1,024 transactions. Its height cannot change afterward.
  • Incoming transfers spend no indexes.
  • If an index is ever exposed twice, QRL advises treating the address as compromised and moving the funds.
  • Funds left in an address with every index spent are lost, so the holder moves them to a fresh address first.

Falcon keys carry no one-time limit. An Algorand Falcon account signs with the same key across every transaction, the way an Ed25519 account does, and the holder keeps no record of past signatures.

Coverage beyond accounts

Algorand has used Falcon keys inside its state proofs since 2022, with participants signing a state proof every 256 rounds. Its roadmap lists further steps:

  • Hybrid accounts will merge existing Ed25519 accounts with lattice-based Falcon ones.
  • Native Falcon-512 support is planned for the end of 2026.
  • Consensus will likely run on Ed25519 and Falcon together for a period, with research still under way.

Algorand targets broad quantum resilience by the end of 2027.

QRL's mainnet has run on XMSS since launch, so QRL holders have no signature migration ahead of them. Its next network, QRL 2.0, runs proof of stake with an EVM-friendly layer on a testnet, and QRL has given no mainnet date for it.

Hybrid signatures on existing chains

Algorand's planned hybrid accounts will combine Ed25519 with Falcon. Quip Accounts already apply a hybrid construction on EVM chains: the account contract accepts an owner operation only with both the owner's ECDSA signature and a SHRINCS signature, so an attacker has to break both to move funds. SHRINCS is the hash-based scheme in Quip signatures, and Quip's open-source pqhybridsign library pairs it with ed25519 or sr25519 in the same hybrid construction.

The everyday SHRINCS signing path uses an XMSS-style Merkle tree, with RFC 8391 as its baseline. Each everyday signature spends a slot, much as a QRL signature spends a one-time key index, and routine key rotation runs on that path too. For recovery, the account holder signs on a separate break-glass path, and that path needs no record of used slots. The Quip clients track slots for account holders.

For the chain-by-chain picture beyond these two, read Which blockchains are quantum resistant?

Next step

Read the Quip Accounts documentation for how slot tracking and recovery work before adding post-quantum signing to a wallet or contract.

Share
Filed underGuides
Newsletter

Don't miss an update

Get new posts and project updates delivered to your inbox. No spam, unsubscribe anytime.