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 6/10, weighted 10%
Band 6 to 8: Addresses are key hashes and exposure is limited to spent outputs, keeping a meaningful share of supply unexposed.
Bitcoin Cash uses the same pay-to-public-key-hash address model as Bitcoin, so a public key is revealed on spend rather than on receipt and a never-spent address exposes only a hash. Exposure therefore concentrates in reused addresses and in the pre-fork pay-to-public-key outputs that Bitcoin Cash inherited with the shared chain history to August 2017.
source
Placement in the band At the floor of the band rather than a 7 or an 8, because the inherited pre-fork outputs are exposed on this chain exactly as they are on Bitcoin, and because no Bitcoin Cash specific measurement of exposed supply has been published. This score reflects the address model, which is what the evidence supports, and the caveat below says what would change it.
6 Verification 5/10, weighted 5%
Band 3 to 5: Some independent verification exists, but the headline quantum-safety claim itself is not verified.
The consensus changes that made Quantumroot practical went through the Cash Improvement Proposal process in public and shipped in a node release. The vault template itself is open source but explicitly unreviewed: its author writes that it "has not yet been reviewed by anyone else" and that he is erring on the side of publishing too early.
source
Placement in the band At the top of the band rather than a 3 or a 4, because the enabling upgrade had genuine public scrutiny and a named node release behind it. It cannot enter the band above, because the component carrying the post-quantum claim is the one part of this that carries a self-declared absence of review.