1 Signature scheme 5/10, weighted 30%
Band 4 to 6: A post-quantum signature is available on mainnet only as an opt-in, application-level or experimental primitive.
Quantumroot verifies Leighton-Micali One-Time Signatures inside Bitcoin Script, so the post-quantum primitive protecting a vault is real and runs on mainnet. It is an application-level contract rather than a protocol signature scheme: Bitcoin Cash itself still signs transactions with ECDSA and Schnorr on secp256k1, and no post-quantum account type exists.
source
Placement in the band Above the 4 given to a comparable application-level vault elsewhere in this index, because the enabling consensus changes shipped in a mainnet upgrade and production wallets carry it, rather than it being a single experimental program. Not a 6, because no share of supply behind Quantumroot has been measured and the author states the template is unreviewed.
2 Deployment stage 8/10, weighted 25%
Band 8: Tier 2: Shipping.
Tier 2: Shipping. A post-quantum signing primitive is live on mainnet and reachable by holders through supported wallets. As with the other contract-level cases in this index, this is a generous reading and the caveat below sets out why a reader might score it lower.
source
3 NIST alignment 7/10, weighted 15%
Band 6 to 8: The scheme is NIST-selected but the standard is not yet final, or a NIST-approved scheme is named but not yet deployed.
Quantumroot names its scheme precisely: LM-OTS as specified in RFC 8554, which NIST SP 800-208 recommends. The construction rests only on SHA-256 rather than on lattice assumptions. What runs is the one-time signature on its own, not the stateful LMS or HSS scheme that SP 800-208 actually approves.
source
Placement in the band A 7 rather than an 8 because the approved artefact in SP 800-208 is LMS, and Quantumroot deploys its LM-OTS component standalone. Above a 6 because the scheme is named to the RFC and the parameter choice, and it is deployed rather than merely referenced.
4 Migration path 8/10, weighted 15%
Band 6 to 8: A credible published plan exists with a mechanism identified, but key parts are unbuilt or undated.
The mechanism is not merely designed but built, live and carried by wallets: a holder can move coins into a Quantumroot vault today, and sweeps out of quantum-ready addresses are cheaper than the equivalent P2PKH spend. Nothing at the protocol level accompanies it. No plan, dated or otherwise, has been published for Bitcoin Cash's own ECDSA and Schnorr signatures.
source
Placement in the band At the top of the band rather than a 6 or a 7, because a working, wallet-supported route beats the identified-but-unbuilt mechanism this band describes at its floor. It cannot reach the band above, which is for chains migrating the accounts themselves: moving coins into a vault contract protects the coins moved and leaves the signature scheme exactly where it was.
5 Exposure 2/10, weighted 10%
Band 0 to 2: Public keys are exposed for effectively all accounts, or a large, measured share of total supply sits in exposed addresses.
Under v1.8's inheritance rule, the published measurements of the history Bitcoin Cash shares with Bitcoin apply to it until one specific to Bitcoin Cash exists. That history, to August 2017, includes the original pay-to-public-key outputs, about 2 million coins by Deloitte's count, around a tenth of supply with the public key already on-chain. Those coins have not moved and sit exposed on this chain exactly as on Bitcoin.
source
Placement in the band The top of the band rather than a 1: only the pre-fork pay-to-public-key share is inherited with certainty, while Bitcoin's larger address-reuse figures were measured on its history after the split and do not transfer. Not a 3, because a measured tenth of supply with keys on-chain is a large share.
6 Verification 5/10, weighted 5%
Band 3 to 5: A post-quantum component exists, on mainnet, on a persistent testnet or as a merged implementation, but is unreviewed.
The Quantumroot vault template is open source and has run on Chipnet, Bitcoin Cash's persistent public testnet, since November 2025, and the May 2026 upgrade made it usable on mainnet. It is still unreviewed: its author's own post says it has not been reviewed by anyone else, and he has called a mainnet vault unwise without an audited wallet.
source
Placement in the band The top of the band rather than a 4: it runs on a persistent public testnet and is usable on mainnet, but there is no outside review to lift it to 6.