The XRP Ledger is designed to keep fees near-zero under normal conditions, but during periods of unusually high demand, fees escalate automatically to protect network integrity. Understanding how this mechanism works helps developers and users plan accordingly.
The Open Ledger Cost
Every XRP Ledger validator maintains two fee thresholds. The first is the local load cost — the minimum fee for a transaction to be relayed by that server. The second is the open ledger cost — the minimum fee for a transaction to be included in the current open ledger, rather than queued for a later one.
Escalation Mechanics
When a ledger fills beyond a certain threshold (approximately 200+ transactions), the open ledger cost escalates according to a proportional curve. This prevents the ledger from being overwhelmed with low-value traffic. Importantly, the escalation is proportional to the transaction type's base cost — not a flat increase.
On March 23, 2026, XRPL recorded 190 transactions per ledger — a one-year high — resulting in aggregate fees temporarily surging above 1,400 XRP for that period.
David Schwartz on Fee Spikes
Ripple's former CTO David Schwartz provided a detailed explanation of fee spike behavior in March 2026. He confirmed that there is no fixed fee on XRPL — the fee adjusts in real time based on demand. He identified two key drivers: overall transaction volume approaching ledger capacity, and specific transaction types (such as multi-signed or complex operations) consuming disproportionate resources.
Transaction Queue
Transactions that meet the local load cost but fall below the open ledger cost are placed in a transaction queue rather than being discarded. The server estimates whether the queued transaction is likely to be included in a future ledger and relays it accordingly. This means there is a graceful pathway for lower-fee transactions during busy periods — they simply wait for the next available ledger slot.
Validator Fee Management
Validators on the XRP Ledger vote on the base fee through the amendment system. Fee changes require sustained supermajority support (approximately 80% of trusted validators) over an extended period. This governance mechanism ensures that fee adjustments reflect broad network consensus rather than individual operator preferences.
How to Handle Congestion in Applications
- Monitor the current fee via the
feeRPC method before submission - Set fee_mult_max appropriately to allow for temporary escalation
- For non-urgent transactions, allow queuing rather than forcing immediate inclusion
- For time-sensitive transactions, set fees above the open ledger cost with margin
Despite occasional congestion events, XRPL's fee management system is designed to be self-correcting. After high-load periods normalize, fees return quickly to the base level, maintaining the network's reputation for predictable, near-zero transaction costs.
Consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum.
Vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis.
Lorem ipsum dolor sit amet.
Consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum.