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 8/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.
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, but the scheme is not deployed on mainnet.
source
Placement in the band The top of the band rather than a 9: ML-DSA is a final standard and a committed selection, but it runs only on AlphaNet, a pre-Devnet network, and the 9 to 10 anchor needs the standardised scheme in use on mainnet.
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 4/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.
ML-DSA signing code for the XRP Ledger is public, in a fork used for AlphaNet, and has been deployed to that test network. Nobody outside its authors has reviewed it: the one upstream pull request was opened and closed within a minute, and Project Eleven is building the proof of concept with Ripple rather than reviewing it. We could not reach AlphaNet to confirm it is still running.
source
Placement in the band A 4 rather than a 5: the code was deployed, but to a network we could not confirm is persistent or reach to check. Not a 3, because the code is public and was actually deployed.