Skip to content
Independent XRP reference
Our standards
← All XRP news

XRP Ledger

XRPL Quantum Plan Separates User Fees From Node Storage Costs

XRPL’s quantum plan adds data costs for nodes while the draft keeps fees as they are. A new model puts a signed payment at 5,331 bytes. This is a plan to test, with no approved date for public Mainnet use.

By
A pale-gold chain-mail sleeve partly encloses a flat cobalt silk packet on ivory stone, with the blue packet protruding from the open cuff.

What the XRPL Foundation’s new Quantum cost model shows

The XRP Ledger Foundation’s November roadmap estimates that a quantum-signed payment would require about three times its ordinary-payment storage baseline, while the draft leaves the fee schedule unchanged. That separates the sender’s charge from the operator’s workload. These are planning estimates for a proposed amendment, not measurements from a live rollout.

The official roadmap was updated November 4, 2026. ForkLog and Bitcoin.com News independently reported the proposal and its cost estimates on November 10. The fresh issue is how to account for the extra burden: a transaction can retain its existing fee treatment while becoming more expensive for infrastructure providers to process and retain.

Confirmed proposal status: the roadmap lists Quantum among amendments still requiring a decision. It schedules a migration study in the first half of 2027, followed by development, review and audit in late 2027 or 2028. That sequence gives integration teams a research agenda, not a production installation deadline.

For readers evaluating the plan, three separate questions matter. What does one protected payment add? What happens when an operator retains many such payments? What does it cost to build and review the change? Combining those questions into one claim that the upgrade is free, or expensive, conceals who would bear which cost.

Section sources[1][2][4][5]

The 5,331-byte estimate is a total, not an extra charge

The Foundation’s feasibility study adds 3,627 bytes of key-and-signature overhead to a 1,704-byte ordinary-payment baseline, producing 5,331 bytes per signed transaction. ForkLog and Bitcoin.com News reproduce that comparison. It describes a modeled storage footprint, including history-related overhead; it is not the number of XRP transferred or a fee quoted to a wallet.

Original calculation: dividing 5,331 by 1,704 gives approximately 3.13 times the baseline. The increase is approximately 213%, rather than a 313% increase. Those two descriptions share the same numerator but use different starting points. Keeping total and additional storage separate prevents a large error when multiplying the figures into a capacity plan.

A deliberately simple illustration makes the distinction concrete. For one million payments with the study’s assumed characteristics, the totals would be 5.331 GB and 1.704 GB respectively, using decimal gigabytes. The difference is 3.627 GB. This is arithmetic on published inputs, not an estimate of how many XRPL users will adopt the signature type.

The comparison also holds payment count constant. A business sending the same number of payments could create a larger historical dataset without moving more XRP. Conversely, extra bytes alone would not demonstrate more customers, more transaction value or greater demand for XRP. Capacity measurements and economic activity need separate denominators.

Illustrative storage for one million payments using the Foundation’s model
ScenarioBytes per paymentDecimal GB for one million
Ordinary-payment baseline1,7041.704
Quantum-signed modeled total5,3315.331
Additional modeled storage3,6273.627
AllAboutXRP calculations on November 10, 2026 from the XRPL Foundation feasibility study, an undated reference linked by its November 4 roadmap, and corroborated per-use figures in ForkLog and Bitcoin.com News on November 10. One GB equals one billion bytes. Not an adoption or hardware forecast.

Section sources[2][4][5]

Node operators need a retention model, not just a signature size

A useful operator budget starts by defining the service being offered. Is the requirement to support current signing, retrieve older transactions, or restore a historical dataset after an outage? Each question calls for a different acceptance measure. Buying enough disk for a modeled total would answer a capacity question, but would not establish whether the service can retrieve or restore that data quickly enough for its customers.

Operator implication: before estimating a bill, specify the data being retained, the retention period and the number of copies. A historical-data service and a signing gateway may have different operational needs. Applying a per-payment figure to every machine in an organization without describing each machine’s role would produce a misleading budget.

For example, a capacity worksheet can start with the protected payment count, apply the modeled additional bytes, then state any replication assumption separately. Backup space, transfer traffic and recovery time belong on separate lines. This makes it possible to change one assumption later without silently changing the meaning of the whole estimate.

A practical acceptance test would compare two otherwise similar workloads on the same equipment, changing the signing scheme while keeping payment contents and retention settings fixed. Record the resulting database growth and processing time independently. Then repeat with a mixed workload. That would help distinguish a cost caused by the new signatures from a cost caused by an unrelated change in traffic. It is a proposed test design, not a test result reported here.

Uncertainty: the Foundation’s feasibility analysis says consensus latency with an entirely ML-DSA validator set has not been publicly measured, and ForkLog reports the same testing gap. A storage multiplier therefore cannot establish how many payments a server will sustain. A useful benchmark would disclose hardware, traffic composition, retention settings, verification work and observed ledger timing together.

Section sources[2][4][6]

An unchanged XRP fee schedule does not remove infrastructure cost

The draft’s fee treatment is distinct from its larger signing material. The primary proposal and the Foundation’s research leave the schedule unchanged; ForkLog reports that operators would absorb the extra data burden. The feasibility study identifies a possible size-related fee rule as a question for the migration study, not a settled policy.

Interpretation: this is an allocation question. If a sender faces the same fee for a heavier transaction, the sender’s visible price does not describe the resources used elsewhere. But the reverse claim would also overreach: the model does not establish that fees must rise, how much they would rise, or whether a future rule would apply to every transaction.

A useful review should compare the resources required by valid ordinary traffic with those required by deliberately burdensome traffic. Average transaction size alone cannot answer whether the system can manage a burst. The decision should be tied to measured constraints and explicit rules, rather than a promise that the stronger signature will have no operational tradeoffs.

For wallet users, the actionable distinction is between a proposed protocol schedule and a provider’s eventual service terms. The current materials are not a quote for a future exchange withdrawal or custody service. Product teams should identify which charge they are describing before advertising a migration as costless.

Section sources[2][3][4]

The development budget is separate from the network’s running costs

The November 4 roadmap estimates 640 build hours and 400 hours of Ripple engineering review for Quantum. Its separate $215,000 to $255,000 range covers review, an audit, a reference implementation and wallet work, excluding the build effort. Bitcoin.com News corroborates both the hours and the exclusion. These are planning figures, not reported expenditure.

Budget implication: review hours are already priced inside that dollar range. Counting the range and then charging the same review hours again would double-count them. The unpriced build effort needs its own assumption before anyone can calculate a complete project budget. Continuing operation of upgraded infrastructure is another category altogether.

NIST’s FIPS 204 standard establishes the ML-DSA signature family; it does not certify a particular XRPL implementation or its operational readiness. The Foundation’s draft and independent coverage still describe integration work. For a custodian, successful standardization is a reason to assess compatible signing systems, not evidence that its own backup and recovery procedures already work.

The next evidence should connect these budgets to deliverables: a migration-study decision, revised specification, interoperable software, published load tests and completed audit findings. A report that shows faster verification but omits retained-history growth answers only part of the question. Until those results exist, readers can evaluate the cost model while keeping deployment timing and final fee policy explicitly unresolved.

Section sources[1][3][5][7]

What to watch next

  • • First-half 2027 migration study: does it retain the existing fee schedule or propose a rule tied to transaction size?
  • • Revised specification: which signature parameters and signing paths are included in the final storage estimates?
  • • Published benchmarks: hardware, transaction mix, retained history, bandwidth and ledger latency under ML-DSA validator traffic.
  • • Budget disclosures: separate build labor, already-priced review, audit and wallet deliverables from ongoing operator costs.
  • • Release and amendment records: reviewed code, audit status and an actual activation decision, rather than an assumed 2028 launch.

Sources and verification

We prioritize primary records and label supporting coverage. Dates reflect each source’s publication record.

  1. [1]XRP Ledger Foundation: 2027 protocol roadmap, updated November 4primary
  2. [2]XRP Ledger Foundation: Quantum market and feasibility studyprimaryUndated reference
  3. [3]XRPL Standards discussion 295: Post-Quantum Signatures, opened July 8, 2025primary
  4. [4]ForkLog: XRPL quantum proposal, fee schedule and operator costssupporting
  5. [5]Bitcoin.com News: XRPL quantum upgrade risks and costssupporting
  6. [6]XRP Ledger Foundation: Quantum impact study, computed October 31primary
  7. [7]NIST: FIPS 204, Module-Lattice-Based Digital Signature Standardprimary