0x05dc08ae05dc…05dc08b1
XRP Ledger Plans Quantum-Resistant Accounts With No Extra User Fees
XRP Ledger Foundation's Nov. 4 roadmap adds ML-DSA-44 quantum-resistant keys, burning no extra fees, with a $215K-$255K audit budget and 2028 migration target.

Outputs
Design uses NIST-approved ML-DSA-44, adding 3,732 bytes per transaction vs 105 bytes today
Base fees stay unchanged; XRP fees are burned, so validators absorb extra storage
Roadmap budgets $215,000-$255,000 plus 640 dev hours for this amendment
Migration study set for H1 2027; Ripple targets full quantum transition by 2028
24 amendments on the 2027 roadmap carry a $5M-$6M total budget
The XRP Ledger Foundation has published a design that would let account owners attach a quantum-resistant signing key and disable their original key, with no increase in base transaction fees for users. The update landed Nov. 4 as part of the Foundation's 2027 protocol roadmap.
The threat the design addresses already exists on-chain. Every signed transaction exposes the public key the network uses to verify the owner's approval. A sufficiently powerful quantum computer could work backward from that key to the private secret controlling the account. Any account that has ever sent a payment — including every exchange wallet — has already exposed its key.
Under the proposal, owners would install the new key first, then switch off the old one, closing the attack route an adversary could otherwise exploit.
Which standard does the new key use?
The design adopts ML-DSA-44, a signature scheme the U.S. National Institute of Standards and Technology approved in 2024 specifically to withstand quantum attacks. The scheme carries a heavier footprint than the ledger's current cryptography.
The key and signature together consume 3,732 bytes, against 105 bytes for a regular payment — roughly 3.6 KB of extra data per protected transaction. Counting history and database overhead, the Foundation estimates 5,331 bytes of storage per protected payment, compared with a 1,704-byte baseline.
Users would not pay for that difference. The proposal keeps the base fee unchanged, and because XRP Ledger fees are burned rather than collected, the operators running the network absorb the extra storage cost. The burden shifts to validators, not account holders.
What work remains before deployment?
Two engineering gaps still block the amendment. Developers are fixing a mismatch in which the Python prototype and the server and JavaScript implementations can generate different keys from the same starting seed. They have also not yet published tests of network behavior when all validators — the computers that agree on the ledger's history — run the new signatures.
The roadmap allocates $215,000 to $255,000 for review and auditing of this single amendment, plus 640 hours of development. Across all 24 amendments on the 2027 roadmap, the budget ranges from roughly $5 million to nearly $6 million.
When would migration happen?
The timeline spans three years. The Foundation has scheduled its migration study for the first half of 2027, with development and auditing to follow in late 2027 or 2028. Ripple, which maintains much of the ledger's core software, is targeting a full quantum transition by 2028.
For exchanges and custody providers holding exposed keys, the window matters: accounts that delay migration would keep a public key on-chain that a future quantum machine could target, while early movers face unfinished cross-implementation tooling.
via cryptonews.net (Source)
More from Tom Whitfield
Show full bio
News editor covering technology and product news in crypto and web3 industry at Mempool Brief.
728 articles