XRP Ledger developers have proposed account signatures to address future quantum computing threats without raising base transaction fees. The upgrade would let wallet owners replace existing signing keys and disable older credentials through a migration process. Meanwhile, the proposal remains under development, and the roadmap schedules migration research for the first half of 2027.
Xrp Ledger Account Upgrade Targets Exposed Signing Keys
Cryptocurrency wallets use digital signatures to authorize transfers, while public keys allow the network to check those instructions. However, XRP Ledger accounts reveal their public keys during transaction signing, creating a record on the blockchain. A sufficiently powerful quantum computer could use that information to compromise current signing methods and gain unauthorized account access.
The proposed design introduces quantum-resistant keys, and account holders would register them through the ledgerโs existing account controls. Users would retain their accounts and assets, but they would change the credentials for approving payments and other actions. This approach focuses on transaction authorization, so the migration would avoid requiring users to move assets into replacement accounts.
Account owners would also need to disable vulnerable signing routes, including their classical master keys, for the intended protection. Merely adding a quantum-resistant regular key would leave an account exposed through an active master key under current rules. Therefore, the migration process must address both new credentials and existing access permissions across participating wallets and account systems.
Xrp Ledger Signature Design Keeps Base Fees Unchanged
Developers selected ML-DSA-44 for the proposal, and the National Institute of Standards and Technology standardized ML-DSA in 2024. The scheme uses larger cryptographic components than current XRP Ledger signatures, increasing the amount of data for each payment. Together, its public key and signature require 3,732 bytes, expanding the information for network transmission, verification, and historical storage.
The Foundation estimates storage at 5,331 bytes per protected payment, compared with 1,704 bytes for an ordinary payment. That estimate represents roughly 3.13 times the current baseline, and it includes the additional key and signature data. However, the draft leaves the base fee schedule unchanged, placing the additional storage burden on operators across the network.
The unchanged schedule addresses base charges, but the larger payload still creates technical demands for servers handling transaction traffic. Consequently, developers must assess bandwidth use, signature verification, and consensus performance alongside the storage estimates in the roadmap. These requirements extend beyond wallet software because validators and other network tools also rely on signatures for operations.
Xrp Ledger Roadmap Sets Research and Audit Priorities
The Foundation schedules migration research for early 2027, followed by development, review, and auditing in late 2027 or 2028. Its estimate allocates $215,000 to $255,000 for reviews, an external audit, reference implementation work, and wallet support. Separately, the roadmap assigns 640 development hours, so the stated cash budget excludes that engineering time from its total.
Developers must resolve key-generation differences between Python tooling, JavaScript software, and server implementations. Those differences prevent matching seeds from consistently producing matching keys across the implementations. Shared test vectors would help confirm consistent results and support integration checks.
Meanwhile, the Foundation has not published complete validator performance measurements for the proposed signatures. Ripple separately targets a broader post-quantum transition by 2028, and testing will inform implementation decisions. The account upgrade still requires further technical work before network deployment.
