1 Signature scheme 0/10, weighted 30%
Band 0: Classical signatures only on mainnet, with nothing post-quantum protecting live funds. Short-lived devnets and one-off benchmarks sit here: they demonstrate research rather than something a user can hold keys on.
Mainnet transactions are signed with secp256k1 or Ed25519 and nothing post-quantum protects live XRP. ML-DSA has been deployed on AlphaNet, which is a pre-Devnet test network, so no post-quantum signature guards funds on the public ledger.
source
2 Deployment stage 5/10, weighted 25%
Band 5: Tier 3: Committed.
Tier 3: Committed. The roadmap is funded, staffed, phased and dated to 2028, and post-quantum work is running on test networks, but no post-quantum signature is live on mainnet.
source
3 NIST alignment 9/10, weighted 15%
Band 9 to 10: The scheme in use is covered by a final NIST standard (FIPS 204, FIPS 205, or SP 800-208).
The roadmap explicitly commits to NIST-standardised quantum-resistant algorithms and names ML-DSA, which is finalised as FIPS 204, as the scheme already running on AlphaNet. This is a committed selection of a final standard rather than a survey of candidates.
source
Placement in the band Not a 10: ML-DSA is a final standard and a committed selection, but it runs on AlphaNet, a pre-Devnet network. A 10 would need the standardised scheme in use somewhere it protects something.
4 Migration path 9/10, weighted 15%
Band 9 to 10: Holders can migrate today, or the published plan is dated, specific, and executable under the chain’s existing governance.
The strongest migration thinking in the index. Phase 1 defines a Q-Day response in which classical signatures stop being accepted and holders migrate using post-quantum zero-knowledge proofs of key ownership, so funds can be rescued without revealing a compromised key. Native key rotation already exists on the ledger, and the amendment process is a proven governance route for consensus changes.
source
Placement in the band Not a 10: holders cannot migrate today. The Q-Day mechanism is specific and executable under the existing amendment process, but it is a response awaiting an event rather than a route that is open now.
5 Exposure 3/10, weighted 10%
Band 3 to 5: Most active accounts have revealed a public key, or the chain has no live supply to assess.
XRP Ledger accounts are derived from a hash of the public key, but the key is published in the transaction that first sends from the account, so any account that has transacted is exposed. Native key rotation gives holders a mitigation that most account-model chains lack.
source
Placement in the band The floor of the band: the key is published on an account's first send, so any account that has ever transacted is exposed, which is close to all of them. It is not a 2 because native key rotation is a real mitigation and never-sent accounts do keep a hashed address.
6 Verification 8/10, weighted 5%
Band 6 to 8: Open source with public review or a named third-party audit of the relevant component.
rippled is open source, the roadmap is published with named phases, and the post-quantum work is being run with an external partner, Project Eleven, on validator-level testing, Devnet benchmarking and a post-quantum custody wallet prototype rather than in-house only.
source
Placement in the band The top of the band: Project Eleven is a named external partner running validator-level testing and Devnet benchmarking, which is closer to a third-party audit than open code alone. It stops short of 9 because the reviewed component sits on a test network rather than on the ledger.