XRP Ledger Wants Quantum-Resistant Accounts by 2027. The Math Is the Easy Part.
The XRP Ledger Foundation's protocol roadmap now includes quantum-resistant account options, with ML-DSA-44 under study and a 2027 target window. It's a research direction, not a live feature, and the hard part is migration, not cryptography.
Can a quantum computer drain your XRP wallet? Not today, and almost certainly not in 2027. But the XRP Ledger Foundation has put quantum-resistant accounts on its protocol roadmap anyway, and that's more interesting than it sounds.
The roadmap lists work on quantum-resistant account options, with ML-DSA-44 named as the signature scheme under study. The target window circulating is 2027. To be clear about what this is: a proposal and a research direction. It's not a network-wide switch, and nobody at the foundation is claiming today's XRP accounts are already quantum-safe. They aren't.
The Numbers That Actually Matter
ML-DSA-44 is one of three parameter sets in the ML-DSA standard, which NIST finalized as FIPS 204 back in August 2024. It's the smallest and leanest of the three. Smallest still means a 1,312-byte public key and a 2,420-byte signature.
Now compare that to Ed25519, which the XRP Ledger already supports. Thirty-two byte public keys. Sixty-four byte signatures.
So you're looking at roughly 41x the key size and about 38x the signature size. Every account that adopts a post-quantum key carries that weight, and every validator on the network stores it, forever.
Why Size Is the Real Problem
Blockchain space isn't free, and the XRP Ledger is unusually explicit about that. Accounts pay a reserve. Objects take up room. If a post-quantum account costs meaningfully more bytes than a classic one, someone has to decide who absorbs that cost, and that answer shapes adoption far more than the cryptography does.
There's also the hardware question. Ledger and Trezor and the rest of the signing-device crowd would need firmware and secure-element support for ML-DSA. That's not an XRPL decision at all. It's a supply chain decision, and supply chains move slower than protocol roadmaps.
And then there's the uncomfortable truth about quantum risk itself. Adversaries can record signed traffic today and attack it later. The threat isn't a machine that exists now. It's a machine that might exist in a decade, aimed at data being archived this afternoon.
The Skeptics Have a Point
Color me skeptical, but a 2027 date attached to a research item is generous language for "we'd like to." XRPL amendments need 80% validator consensus held for two weeks before they activate. That's a real bar, and quantum-resistant accounts don't carry the same commercial urgency as, say, a fee fix.
Granted, the foundation has shipped protocol upgrades before. Admittedly, naming ML-DSA-44 publicly puts a marker down. But the migration problem is human, not cryptographic. Users don't rotate keys until something forces them to, and history suggests otherwise on voluntary security upgrades.
My read: the math is the easy part. Getting millions of accounts to move is where this gets hard, and the roadmap doesn't say much about that.
What to Watch
Watch for an XLS specification number. That's the moment a roadmap line item becomes something developers can argue about in public. Then watch for devnet support, hardware wallet vendor statements, and whether the amendment ever shows up in validator voting.
The question worth asking: if a quantum-resistant account costs three times the reserve of a normal one, who signs up first? Probably institutions. Probably quietly.
Time will tell, though. Keep an eye on 2027.
Related Articles
Explore More
Key Terms Explained
A distributed database where transactions are grouped into blocks and linked together cryptographically.
A development network used for early-stage testing of blockchain protocols and smart contracts.
A physical device that stores cryptocurrency private keys offline.
A record of transactions.