Daily news

XRP Ledger maps out quantum-resistant accounts with no extra fees: what the ML-DSA-44 plan means

The XRP Ledger Foundation's 2027 protocol roadmap, updated November 4, includes a costed plan for a "Quantum" amendment that would let XRPL accounts, validators and list publishers sign with NIST's ML-DSA-44. Base fees would not change, but quantum-signed payments would be about three times larger. A migration study is due in the first half of 2027, and Ripple targets a full transition by 2028.

MyTraderBot DeskPublished: 12 min readخواندن به فارسی
Share
IBM Quantum System One cryostat with gold-plated stages, with MyTraderBot branding
IBM Quantum System One. OJB Quantum / Wikimedia Commons, CC BY 4.0.
Table of Contents

Key takeaways

  • The XRP Ledger Foundation has published a costed plan for quantum-resistant signatures on the XRP Ledger (XRPL), as part of its 2027 protocol roadmap. The roadmap and the quantum study page were both marked updated on November 4, 2026.

  • The proposed Quantum amendment would add ML-DSA-44, the post-quantum signature standard NIST approved in 2024, for accounts, validators and validator list publishers. Existing accounts would not be migrated automatically.

  • The base transaction fee would not change. A quantum-signed payment would take about 5,331 bytes of storage, compared with 1,704 bytes for an ordinary payment, and node operators would carry that extra load.

  • Nothing is live. A migration study is planned for the first half of 2027, followed by development and audits in late 2027 or 2028. Ripple is aiming for a full transition no later than 2028.

What the XRP Ledger Foundation published

The XRP Ledger Foundation, the non-profit that supports the network's open-source development, keeps a public "2027 protocol roadmap". It lists the 24 amendments the Foundation wants to fund next year. Each entry gives its current state, the next step, an estimate of build and review hours, the cost, and a "market fit" score out of 12. The roadmap first appeared on the Foundation's pages site on September 9, 2026. The current version is stamped "Updated 2026-11-04", and so is its quantum research page, "Quantum: market and feasibility".

That research page is the new material behind this week's coverage. CoinDesk reported it on November 10, followed by crypto.news and Bitcoin.com News. It covers who needs post-quantum protection, what rival blockchains are doing, the storage and dollar costs, and the problems still open in the draft specification. The Foundation is careful about status: "Nothing here is promised. An amendment activates only if the validators vote it in."

The underlying technical spec is not new. It is a draft XRPL Standards proposal, "Post-Quantum Signatures (ML-DSA-44)", which Ripple engineer Denis Angell opened as discussion #295 in the XRPLF/XRPL-Standards GitHub repository on July 8, 2025. It was last updated on May 20, 2026 and is still marked Draft, with no XLS number yet. What changed in November is that the Foundation put the work on its funded roadmap with a price, a schedule and a list of risks.

Why quantum computers threaten XRP accounts

Today every XRPL account signs with one of two elliptic-curve schemes, secp256k1 or Ed25519. Both could be broken by Shor's algorithm running on a large enough fault-tolerant quantum computer. No such machine exists yet. The Foundation's concern is the public data that is already on the ledger.

Ripple put the problem plainly in its April 20, 2026 post "Post-Quantum Readiness on the XRP Ledger": "Every time an account signs a transaction, its public key becomes visible onchain." An attacker could record those keys now and try to work back to the private keys later, once the hardware exists. Researchers call this "harvest now, decrypt later." Any account that has sent a transaction, including every exchange hot wallet, has already exposed its key.

The study also cites research suggesting the attack is getting cheaper. In March 2026, Google Quantum AI and co-authors from the Ethereum Foundation and Stanford published circuits that would solve the 256-bit elliptic-curve problem behind secp256k1 with fewer than 1,200 logical qubits. Regulators are setting deadlines too. The study cites NIST's transition report (NIST IR 8547), which says quantum-vulnerable public-key cryptography will be deprecated after 2030 and disallowed under NIST standards after 2035.

The Foundation expects three groups to want the feature first:

  • Holders of large balances: exchanges, custodians and token issuers.

  • Validators and validator list publishers: they use long-lived keys that sign consensus messages and the lists that tell nodes which validators to trust.

  • Regulated institutions: they face formal post-quantum migration deadlines.

How the proposed Quantum amendment works

The draft adds a third key type, called dilithium in the code, next to secp256k1 and ed25519. It uses ML-DSA-44, the smallest parameter set of NIST's FIPS 204 standard, published on August 13, 2024. The spec makes it available on every surface that produces a signature: account transactions, multi-signing, Batch transactions, payment-channel claims, validator manifests, validations, consensus proposals, validator lists and peer-to-peer handshakes.

Some details matter for ordinary users:

  • Same address format. XRPL addresses are derived from a hash of the public key, so a quantum-resistant key still produces a normal r... address.

  • Opt-in migration. The spec does not move anyone automatically. An account owner would need to set a quantum-resistant regular key with SetRegularKey, or send funds to a new account derived from a quantum-resistant key.

  • The master key must be turned off. The Foundation's study flags a gap in the spec here. Setting a dilithium regular key "does not protect an account whose classical master key is still enabled; the master key must also be disabled." The XRPL already supports disabling the master key pair, so the old key can no longer sign.

  • Off by default. The amendment is coded as DefaultNo. Validators must vote it in actively. Until it activates, the network must reject any dilithium-signed transaction.

On the XRP Ledger, an amendment passes only if it keeps more than 80% support from trusted validators for two weeks, according to the xrpl.org documentation.

Bigger keys and signatures, same fee

Post-quantum signatures are much larger than the ones the ledger uses today. Using the spec's figures, the Foundation's study puts an ML-DSA-44 public key at 1,312 bytes and a signature at up to 2,420 bytes, or 3,732 bytes together. An ordinary payment carries a 33-byte key and a 72-byte signature. Each quantum-signed transaction would therefore add about 3,627 bytes.

Including transaction history, the study puts a quantum-signed payment at 5,331 bytes, about 3.1 times the 1,704 bytes of an ordinary payment. One such transaction per ledger would add about 42 GB a year. A thousand per ledger would add about 42,029 GB a year.

Users would not pay more for this. The spec does not change the fee schedule. The minimum cost of a standard XRPL transaction is 10 drops of XRP, and that XRP is destroyed rather than paid to anyone. The heavier bandwidth and storage load would fall on the operators who run validators and full-history servers. The study lists fees and size as its first risk. Because a quantum-signed transaction carries about 3.7 KB more for the same base fee, that affects bandwidth, history storage and the cost of spam. It says the migration study "should decide whether size needs its own fee rule."

Cost, timeline and Ripple's 2028 goal

The Foundation gives the quantum work its highest size rating (XL) and its highest complexity score (3 out of 3), because it touches cryptography, consensus and every signature check in the node software. The costing is:

  • Build: 640 hours, about four engineer-months.

  • Ripple code review: 400 hours at $100 to $200 an hour, or $40,000 to $80,000.

  • External security audit: $100,000.

  • Reference implementation and client-library support: $50,000.

  • Ledger hardware wallet XRP app and community wallet updates: $25,000.

  • Total: $215,000 to $255,000, not counting the 640 build hours.

Across all 24 amendments, the roadmap estimates 6,240 build hours, 6,560 Ripple review hours and $5.08 million to $5.74 million in costs. Quantum scores a medium 7 out of 12 for market fit. It ranks near the bottom of the proposed items, behind lending and credit features such as Loan Collateral. The Foundation also says security work goes ahead of new features, and that once the 2027 budget is approved, its CTO and its Director, Community and Product will choose which funded items to build.

The schedule follows Ripple's plan. In April, Ripple published a four-phase roadmap:

  1. A "Q-Day" contingency plan, in case classical cryptography breaks suddenly.

  2. Experimentation in the first half of 2026.

  3. Testing of post-quantum primitives on Devnet in the second half of 2026.

  4. A new amendment and a full transition for post-quantum signatures, targeting no later than 2028.

Ripple named Project Eleven as a partner. Project Eleven is building a proof-of-concept hybrid signing implementation and a post-quantum custody wallet prototype. The Foundation's roadmap entry describes the next step as "a post-quantum migration study in the first half of 2027", with development, review and audit "in late 2027 or 2028". Ripple's blog post also says the company is designing for "cryptographic agility", meaning support for more than one NIST-standardized algorithm rather than a single scheme.

What still has to be fixed

An implementation exists on the xrplf/quantum branch of the XRPL server code and has run on AlphaNet, a developer test network. The Foundation and the spec itself list several open problems:

  • Mismatched keys. The Python validator list publisher tool derives keys from 48 bytes of a hash where the server and xrpl.js use 32, so the same seed produces different keys. The spec says this must be fixed before it is final.

  • No shared test vectors. The cross-implementation test file the spec requires does not exist yet.

  • Admin commands. The admin commands sign and wallet_propose still reject dilithium keys.

  • How the scheme is identified. The spec identifies the scheme by key length. A public comment on October 15 argued for an explicit algorithm identifier so that schemes such as SLH-DSA can be added later without another format change.

  • Signature length. FIPS 204 fixes ML-DSA-44 signatures at exactly 2,420 bytes, but the draft accepts shorter ones in some places. A November 2 comment on the GitHub thread also asked for checks against NIST's own test vectors.

  • Network load. Nobody has publicly measured consensus speed with all of the roughly 150 validators signing with dilithium. The spec already raises peer socket buffers to 1 MiB after it saw connection errors under bursts of large signatures.

  • Design choices. It is not settled whether to use pure ML-DSA-44 or a hybrid that pairs a classical signature with a post-quantum one, which Ripple's partner is building. Validators and custodians would also need hardware security modules that support the new keys.

How XRPL compares with other blockchains

The Foundation's study says no major blockchain has yet shipped native post-quantum keys for ordinary accounts and validators on mainnet. Bitcoin's BIP 360 is a draft that reduces public-key exposure but leaves post-quantum signatures to a later soft fork. Ethereum is targeting its main quantum milestones around 2029. Algorand verifies Falcon signatures through a smart-signature program rather than a native account type. QRL runs ML-DSA-87 on testnet. If the amendment ships as planned, the XRP Ledger would be among the first major networks to offer the feature natively. The Foundation calls that "a reason for the hardest review."

What it means for XRP holders

You don't need to do anything now. No quantum-resistant key type is active on XRPL mainnet, and none is scheduled before the 2027 study. The spec warns that quantum keys used before activation would produce transactions "no peer accepts", and that holders should keep their current key as a fallback until activation is confirmed.

Watch for scams. Any website, direct message or "support agent" offering an urgent "quantum-safe XRP migration" in exchange for your secret key or seed is a scam. Never share your recovery phrase. Our guide to storing a seed phrase safely explains why. Recent incidents such as Keplr's Web3Auth key breach and the unauthorized transfers that halted Initia show that stolen or mishandled keys are a far more immediate risk than quantum computers.

Institutions are likely to move first. The study expects exchanges, custodians and issuers to rotate first, which ties in with banks building crypto custody, such as Deutsche Bank's digital asset custody launch. If you hold XRP on an exchange, its key migration will be the exchange's job. If you self-custody, check that your wallet supports the new key type before you move anything.

There is no direct price effect. This is a long-term security roadmap item, not a product launch.

What we still don't know

  • Whether the 2027 budget will be approved, and whether Quantum will be among the items chosen for funding.

  • Whether the migration study will keep pure ML-DSA-44, add a hybrid mode, or add a fee rule based on transaction size.

  • How Ripple's own planned amendment and the Foundation's draft will become a single spec.

  • When, or whether, validators will vote the amendment in.

FAQ

Is the XRP Ledger quantum-resistant today? No. Accounts and validators still use secp256k1 or Ed25519. The Quantum amendment is a draft that has been tested only on a developer network.

Will XRP transaction fees go up? Not under the current proposal. The spec keeps the base fee unchanged, and node operators would absorb the extra storage. The 2027 migration study may revisit fees based on transaction size.

Will I need a new XRP address? Not necessarily. You could keep your address, set a quantum-resistant regular key and disable the old master key. Moving funds to a new quantum-derived account is another option.

When could this go live? The Foundation plans a migration study in the first half of 2027, followed by development and audits in late 2027 or 2028. Ripple is targeting a full transition by 2028. Activation still needs more than 80% validator support for two weeks.

This article is news, not investment advice.

Sources

  • XRP Ledger Foundation, "2027 protocol roadmap" and "Quantum: market and feasibility" (updated Nov 4, 2026)

  • XRPLF/XRPL-Standards discussion #295, "Post-Quantum Signatures (ML-DSA-44)" (opened Jul 8, 2025; spec updated May 20, 2026)

  • Ripple, "Post-Quantum Readiness on the XRP Ledger" by Ayo Akinyele (Apr 20, 2026)

  • xrpl.org documentation: amendments, transaction cost, disabling the master key pair

  • NIST FIPS 204, Module-Lattice-Based Digital Signature Standard (Aug 13, 2024)

  • CoinDesk (Nov 10, 2026); Bitcoin.com News and crypto.news (Nov 10, 2026)

Photo: IBM Quantum System One at IBM's Thomas J. Watson Research Center, Yorktown Heights, New York (May 2024), by OJB Quantum. CC BY 4.0, via Wikimedia Commons. Illustrative; not connected to the XRP Ledger.

Coins mentioned
  • XRP
Share

See the signals and their results

Browse publicly logged signals and how they performed, or create a free account to follow them.

XRP Ledger Quantum-Resistant Accounts: ML-DSA-44 Plan