Post-Quantum Cryptography and Encryption Field Guide
Is XRP Safe From Quantum Computers?
- THREAT TODAY
- No break at scale
- none demonstrated yet
- XRP SIGNS WITH
- Ed25519 or ECDSA (secp256k1)
- both quantum-vulnerable
- THE EDGE
- Native key rotation
- replace the signing key, keep the address
- ROADMAP
- 2028 target
- ML-DSA-44 proposed, not approved
No publicly demonstrated quantum computer has broken the signature schemes the XRP Ledger uses at the scale required. XRP isn't inherently safer than other coins: it signs with Ed25519 or ECDSA over secp256k1, and both fall to Shor's algorithm once a capable machine exists. What XRPL has that most chains don't is a native way to change the key that authorizes an account without changing the account's address, and there is a proposed post-quantum amendment with a 2028 transition target.
Part of the Post-Quantum Cryptography and Encryption guide seriesWhat XRP signs with
There’s still no machine that can break XRP today, but XRP is not inherently safer than other coins. Its advantage is a cleaner path to fix the problem later. New to the threat? Start with What Is Q-Day? and Post-Quantum Cryptography, in Plain English.
The XRP Ledger supports two signing schemes: Ed25519 and ECDSA over secp256k1 (the same curve Bitcoin uses). Many client libraries, including xrpl.js, default to Ed25519, but defaults vary by tool. Both face the same class of quantum attack, where Shor’s algorithm breaks them once the hardware exists, so switching between the two schemes doesn’t make an account quantum-resistant. The fix is a post-quantum scheme, not a different curve.
The XRP Ledger supports Ed25519 and ECDSA over secp256k1. They differ in format and performance, but both are broken by Shor’s algorithm once a capable quantum computer exists, so switching between the two doesn’t make an account quantum-resistant. The fix is a post-quantum scheme, not a different curve.
When your public key gets exposed
An XRP address is a hash of your master public key, so receiving XRP doesn’t publish the key. The key is recorded on-ledger when a transaction you sign is validated, because the signing public key travels with the transaction. The nuance that matters is this: your first transaction uses the master key, but later transactions can use a regular key or a signer list instead, and a master key that’s been disabled no longer authorizes spending, even though its public key stays in history. So to assess exposure, look at which keys are public and still able to authorize transactions.
| Account state | What it means for exposure |
|---|---|
| Funded, no outgoing transaction | Receiving XRP doesn’t reveal the master key (though it could be disclosed elsewhere). |
| Master key public and still enabled | The exposed key still authorizes spending, even if you normally sign with a regular key. |
| Master key disabled | Its public key stays in history, but exposure now depends on whichever keys remain enabled. |
| Signer list (multisig) | Each signer’s key shows as it signs; an attacker would need enough signing weight to meet the quorum. A single enabled key can still authorize on its own. |
In an April 2026 snapshot, XRPL validator Vet classified about 5.69 million of 7.81 million accounts as exposed under the study’s model. Those accounts were associated with 76.82 billion XRP, including funds in escrow and payment channels, whereas about 23.16 billion XRP sat in accounts the model classified as unexposed. The figures depend on the study’s assumptions and don’t show how much an attacker could immediately spend.
How XRPL rotates a signing key without moving funds
This is XRPL’s concrete structural advantage. The ledger lets you change the key that authorizes an account without changing the account itself:
Add a regular key
A SetRegularKey transaction gives the account a second key pair that can sign for it, separate from the master key the address came from.
Sign with it
Your address, balances, trust lines, and history all stay the same.
Disable the master key (optional)
Once you have a working regular key or signer list, use the master key itself to sign an AccountSet transaction that sets asfDisableMaster. The master key then stops authorizing transactions unless it is re-enabled.
Today, you can only rotate to another classical key, which is still quantum-vulnerable. Rotation becomes a real quantum fix only once the ledger supports a post-quantum scheme to rotate into. And before disabling the master key, test and back up an alternative signing method: once it’s disabled, a working regular key or a multisignature meeting the account’s quorum is what re-enables it, so backing up the disabled master key doesn’t give you a way back in.
This mechanism is native to XRPL at the protocol level. Bitcoin has no equivalent, and on Ethereum ordinary accounts don’t either, though smart-contract accounts can define their own authorization rules. It’s a real advantage for in-place migration, but it’s only one piece; it doesn’t by itself make the entire transition simple.
Ripple’s plan, and where it stands
Ripple published a four-phase post-quantum roadmap on April 20, 2026. It designs for “crypto-agility” (supporting multiple NIST schemes rather than committing to one) and runs new cryptography alongside the existing signatures instead of replacing them overnight. The dates below are the plan’s own milestones, not confirmation that each has shipped.
| Phase | What Ripple outlined | Timing (as planned) |
|---|---|---|
| 1. Post-quantum recovery | A Q-Day contingency: if classical signatures break, force a shift to post-quantum accounts. Ripple is exploring whether post-quantum zero-knowledge proofs could let holders prove ownership and migrate without exposing keys | Contingency planning |
| 2. Planning and experimentation | Assess the impact on performance and storage; test NIST schemes (ML-DSA prototyped on AlphaNet by Denis Angell) | 1st half of 2026 |
| 3. Exploration of primitives | Run candidate post-quantum signatures alongside the current ones, starting on Devnet | 2nd half of 2026 |
| 4. Full transition | Propose a native post-quantum amendment and migrate at scale | targeting 2028 |
Ripple’s April roadmap targets a post-quantum transition by 2028, and a separate draft proposes ML-DSA-44 (the “Quantum” amendment). The XRP Ledger Foundation’s November roadmap lists a post-quantum migration study for the first half of 2027, with development, review, and audit to follow in late 2027 or 2028. That amendment is still proposed, not approved, and mainnet activation requires more than 80% support from trusted validators for two weeks. How holders migrate will depend on the rules that ultimately activate. Ripple has been clear that none of this means XRP is at risk today.
2028 is a target for the ledger to support post-quantum signatures, not a prediction of when quantum computers arrive. Any amendment still has to be built, audited, proposed, and voted in by validators, and the scheme (ML-DSA-44) is a prototype, not a finalized choice. Existing accounts would not switch automatically.
What to do if you hold XRP
Bottom line
XRPL’s advantage is that holders can change an account’s regular signing key without moving its funds or changing its address, something Bitcoin and ordinary Ethereum accounts don’t offer natively. Its current signatures remain vulnerable to a sufficiently capable quantum computer. Ripple is targeting a post-quantum transition by 2028, but the scheme is still a proposal, and holders will need to follow whatever migration rules ultimately activate.
XRP’s advantage isn’t the math, it’s the migration. The cryptography is as quantum-vulnerable as anyone’s, but an account can change its signing key without moving funds, and a post-quantum scheme is on the roadmap.
// FAQ
Is XRP safe from quantum computers right now?
Yes, in that no publicly demonstrated quantum computer has broken its signatures at the required scale yet. It isn’t inherently safer than other coins; it signs with Ed25519 or ECDSA over secp256k1, both of which Shor’s algorithm breaks once the hardware exists.
Does XRP use quantum-resistant cryptography?
Not yet. It uses classical elliptic-curve signatures today. A post-quantum amendment (ML-DSA-44) is proposed, with a transition targeted by 2028, pending development, audit, and a validator vote.
Is my XRP public key exposed?
If a key that can still authorize your account is already recorded on-ledger, yes. Receiving XRP doesn’t reveal the master public key, though the key may have been disclosed elsewhere, and a disabled master key’s old disclosure no longer controls the account.
Will I have to move my XRP to stay safe?
XRPL can replace an account’s regular key without moving funds or changing the address, so in-place rotation is one route. Some holders may move funds to a new account instead, and which path applies will depend on the rules that activate. Either way, assigning a post-quantum key won’t help if a classical key is still enabled to authorize on its own.
Is XRP safer than Bitcoin against quantum?
Not in the cryptography; both are vulnerable. XRP’s edge is operational: native in-place key rotation gives it a concrete migration tool that Bitcoin and ordinary Ethereum accounts lack.
Keep going
New to the threat? Start with What Is Q-Day? plus Is Bitcoin Safe, Is Ethereum Safe, and Which Cryptocurrencies Are Quantum-Resistant.
Disclaimer: This article is educational and does not constitute security or investment advice.
// Sources
- Ripple, Post-Quantum Readiness on the XRP Ledger (April 20, 2026) https://ripple.com/insights/post-quantum-readiness-on-the-xrp-ledger/ XRP Ledger Foundation, 2027 Protocol Roadmap — the "Quantum" (ML-DSA-44) amendment (updated Nov 4, 2026) https://pages.xrpl.foundation/protocol-roadmap/ Vet, XRPL quantum-exposure dataset (April 2026) https://github.com/xVet/xrpl-quantum-exposure-dataset XRP Ledger, Cryptographic Keys https://xrpl.org/docs/concepts/accounts/cryptographic-keys XRP Ledger, Assign a Regular Key Pair https://xrpl.org/docs/tutorials/best-practices/key-management/assign-a-regular-key-pair XRP Ledger, Disable Master Key Pair https://xrpl.org/docs/tutorials/how-tos/manage-account-settings/disable-master-key-pair NIST FIPS 204, Module-Lattice Digital Signature Standard (ML-DSA) https://csrc.nist.gov/pubs/fips/204/final