What to Know
- A proposed XRP Ledger upgrade would let account owners add quantum-resistant signing keys and disable their original keys.
- The design is intended to reduce future risk from quantum computers that could potentially derive private secrets from exposed public keys.
- The new signing approach uses ML-DSA-44, a signature scheme approved by NIST in 2024 for quantum-resistant security.
- The key and signature together take 3,732 bytes, compared with 105 bytes for a regular payment.
- Including history and database overhead, protected payments are estimated at 5,331 bytes versus a 1,704-byte baseline.
- The proposal keeps the base transaction fee unchanged, meaning users would not pay extra base fees for the larger signatures.
- Network operators would absorb the added storage burden because XRP Ledger fees are destroyed.
- Technical work remains incomplete, including fixes to a key-generation mismatch across implementations and network testing with validators using the new signatures.
- A migration study is scheduled for the first half of 2027, with development and auditing expected to follow in late 2027 or 2028.
- Ripple is targeting a full quantum transition by 2028.
XRP Ledger Prepares for a Post-Quantum Security Shift
The XRP Ledger is moving deeper into long-range security planning as developers outline a proposed account upgrade designed to protect users from the potential threat of future quantum computers. The core idea is straightforward but consequential: account owners would be able to add a quantum-resistant signing key to an existing account, then switch off the original key that may already have been exposed through previous transactions.
For blockchain networks, the quantum debate is not only theoretical. Public blockchains rely on cryptographic signatures to prove that an account owner has authorized a transaction. When an XRP Ledger account signs a transaction, the process reveals a public key that the network uses to verify that approval. Under today’s assumptions, the corresponding secret remains secure. However, a sufficiently powerful quantum computer could, in theory, work backward from a public key and uncover the private secret that controls the account.
That risk is especially important because exposure can already exist onchain. Any account that has ever sent a transaction has revealed its public key. That includes individual wallets, exchange wallets and other high-activity accounts. The proposed upgrade is meant to give those accounts a migration path before quantum computing capabilities become a practical threat to current signature systems.
How the Proposed Account Upgrade Would Work
The design would allow an account owner to attach a quantum-resistant signing key to the account. Once that new key is in place, the owner could disable the old key. That step matters because simply adding a new signing method would not fully remove risk if the previous key remained active. Turning off the older key would close the attack route that a future quantum-capable adversary might otherwise attempt to exploit.
Market participants watching the development of major blockchain networks see this kind of account-level migration as a practical challenge as much as a cryptographic one. Blockchains must preserve continuity while improving security. Users need enough time and clear tools to move safely. Exchanges and custodians need operational procedures that avoid service disruptions. Validators and node operators need software that can handle new transaction formats reliably.
The proposed XRP Ledger approach aims to make the shift possible without forcing users into a separate account structure or requiring a fee increase at the base transaction level. That distinction may be important for adoption, because security upgrades can lose momentum if users face added friction or direct cost increases during migration.
ML-DSA-44 Brings Larger Keys and Signatures
The new key design uses ML-DSA-44, a signature scheme approved by the U.S. standards body NIST in 2024 for resistance to quantum attacks. Quantum-resistant cryptography often comes with a trade-off: the signatures and keys can be larger than those used in existing blockchain systems. That is also the case in the XRP Ledger proposal.
The key and signature together would take 3,732 bytes, compared with 105 bytes for a regular payment. That means each protected transaction would carry about 3.6 KB of additional data. When accounting for history and database overhead, the storage figure rises to 5,331 bytes per protected payment, compared with a 1,704-byte baseline.
Those numbers highlight the engineering challenge facing networks that plan for post-quantum security. The cryptography can strengthen account protection, but the ledger must store and propagate more data. Over time, if many accounts adopt quantum-resistant signing, the cumulative storage and bandwidth implications could become material for infrastructure operators.
No Extra Base Fees for Users Under the Proposal
One of the most notable elements of the design is that users would not face extra base transaction fees for using quantum-resistant signatures. The proposal keeps the base fee unchanged, even though protected transactions require more storage than standard transactions.
That choice shifts the burden to network operators. XRP Ledger fees are destroyed rather than paid to validators, so the larger storage footprint would be absorbed by the parties running network infrastructure. In practical terms, this means account owners would receive a path toward stronger cryptographic protection without paying a higher base fee directly for each protected transaction.
For users, that could simplify the decision to migrate. If the cost of safer signing were visibly higher at the transaction level, some account holders might delay action, especially those with low balances or infrequent activity. By keeping base fees unchanged, the design gives wallets, exchanges and other service providers a cleaner route to encourage adoption when the upgrade becomes available.
Technical Work Still Needs to Be Completed
The roadmap does not suggest that the transition is finished. Several technical issues remain unresolved before the XRP Ledger can move to a full quantum-resistant account model. Developers are still addressing a mismatch in which the Python prototype and the server and JavaScript versions can generate different keys from one starting seed.
That kind of mismatch must be fixed before production deployment because deterministic key generation needs to be consistent across supported implementations. If different tools produce different keys from the same starting material, users and developers could face serious reliability and recovery problems. For a financial ledger, those issues are not cosmetic; they go directly to account access and transaction authorization.
Testing also remains a major requirement. Developers have yet to publish tests showing how the network performs when all validators use the new signatures. Validators are the computers that agree on the ledger’s history, and their ability to process, validate and maintain consensus under a new signature scheme is central to any major cryptographic change.
Budget and Roadmap Point to a Multi-Year Transition
The quantum-resistant account proposal forms part of a broader protocol roadmap that includes multiple amendments. The roadmap sets aside $215,000 to $255,000 for review and auditing of this amendment, along with 640 hours of development. Across all 24 amendments on the roadmap, the total budget runs from about $5 million to nearly $6 million.
The timeline also reflects the scale of the work. A migration study is scheduled for the first half of 2027. Development and auditing are expected to follow in late 2027 or 2028. Ripple is targeting a full quantum transition by 2028, suggesting that the network’s quantum-security plan is being treated as a staged process rather than a single switch.
That staged approach is common in major protocol changes. Before a network can transition, developers must define the cryptographic method, test software implementations, measure performance, audit security assumptions and prepare users for migration. Wallet providers, exchanges, custodians and infrastructure operators then need time to update systems and operational procedures.
Why Quantum Planning Matters for XRP Holders
For XRP holders, the immediate takeaway is not that current accounts are being actively exploited by quantum computers. Rather, the concern is forward-looking. Accounts that have already sent transactions have public keys visible onchain, and those exposed keys could become a risk if quantum computers become powerful enough to break current cryptographic assumptions.
The proposed account design gives users a way to reduce that future exposure. By adding a quantum-resistant signing key and disabling the original key, an account owner would be able to move away from reliance on a key that has already been revealed through past activity. This is particularly relevant for accounts that hold meaningful balances or perform regular transactions.
Some chart watchers and technical traders tend to focus on price action, liquidity and market sentiment, but protocol security can also influence long-term confidence in a blockchain ecosystem. A credible migration path toward quantum-resistant accounts may help reassure infrastructure providers and institutions that the network is planning for future cryptographic risks before they become urgent.
Broader Implications for Blockchain Infrastructure
The XRP Ledger’s quantum roadmap reflects a wider issue facing digital asset networks. Many blockchains were designed around cryptographic assumptions that remain robust today, but the industry must still plan for the possibility that quantum computing changes the security landscape. Preparing early can reduce the chance of rushed upgrades later.
At the same time, quantum-resistant cryptography introduces practical trade-offs. Larger signatures mean more data. More data means higher infrastructure demands. If users are not charged extra base fees, node operators may shoulder more of the operational cost. Networks must balance user experience, decentralization, storage requirements and security.
For the XRP Ledger, the proposed design attempts to strike that balance by preserving fee simplicity for users while placing the technical burden on infrastructure that can be upgraded and optimized over time. Whether that model proves sufficient will depend on testing, audits, validator performance and the eventual migration experience for wallets and exchanges.
Frequently Asked Questions (FAQs)
What is the XRP Ledger quantum-resistant account proposal?
It is a proposed upgrade that would let XRP Ledger account owners add a quantum-resistant signing key to an account and disable the original key. The goal is to protect accounts from future quantum-computing risks tied to exposed public keys.
Why would old XRP Ledger keys need to be disabled?
When an account signs a transaction, it reveals a public key onchain. A powerful enough quantum computer could potentially use that public key to derive the secret controlling the account, so disabling the old key after adding a new one would reduce that future attack path.
Will users pay higher base transaction fees for quantum-resistant signatures?
Under the proposal, the base transaction fee would remain unchanged. Users would not pay extra base fees for the larger quantum-resistant key and signature, even though the protected transaction requires more storage.
Who absorbs the added storage cost?
Network operators would absorb the additional storage burden. XRP Ledger transaction fees are destroyed, so the larger data footprint does not create a direct fee payment to validators.
What signature scheme is being proposed?
The proposed design uses ML-DSA-44, a signature scheme approved by NIST in 2024 for quantum-resistant security. It is larger than the signature structure used for regular payments today.
How much larger are the new keys and signatures?
The key and signature together take 3,732 bytes, compared with 105 bytes for a regular payment. Including history and database overhead, protected payments are estimated at 5,331 bytes versus a 1,704-byte baseline.
Is the upgrade ready for deployment?
No. Technical work remains unfinished. Developers are addressing a mismatch across implementations and still need to publish tests showing how the network performs when all validators use the new signatures.
What is the timeline for the XRP Ledger quantum transition?
A migration study is scheduled for the first half of 2027, with development and auditing expected to follow in late 2027 or 2028. Ripple is targeting a full quantum transition by 2028.
Why does this matter for exchanges and custodians?
Exchange and custodian wallets often sign many transactions, which means their public keys may already be exposed onchain. A clear migration path would help these operators move accounts to quantum-resistant signing while reducing disruption for users.