How XRP Burn Rate Works and Why XRP Gets Destroyed Forever Every time someone sends a payment on the XRP Ledger, a tiny sliver of XRP disappears forever. That is XRP burn, and it has been run
Every time someone sends a payment on the XRP Ledger, a tiny sliver of XRP disappears forever. That is XRP burn, and it has been running quietly in the background since the network launched back in 2012. This guide breaks down what actually gets destroyed, how the mechanism works under the hood, what gets burned on each transaction, and whether all of this really makes XRP deflationary.
This refers to the small amount of $XRP permanently destroyed every time a transfer gets processed on the XRP Ledger. This destroyed amount is called the transaction cost, and its entire purpose is protecting the network from spam and denial-of-service attacks, not generating revenue for anyone.
That last part matters more than people often realize. The fees documentation states plainly that these are "neutral fees that protect the ledger against abuse" and that they "are not paid to anyone." No validator collects a cut. No company pockets the difference. The $XRP just stops existing.
The system is built around a unit called a drop, the smallest possible division of $XRP. One drop equals 0.000001 XRP.
PerXRPL.org's transaction, the standard minimum cost for most transactions is 10 drops, or 0.00001 $XRP. That number is not fixed forever, though. It rises automatically when network load increases through a system XRPL.org calls "fee escalation." Each server tracks its own load and raises the required cost when the network gets busy, which makes it expensive to flood the ledger with junk transactions while keeping normal use nearly free.
A few technical points worth knowing:
The cost is deducted only once a transfer actually lands in a validated ledger, whether that transfer succeeds or fails
Fee changes require validator consensus through a formal fee voting process, not a unilateral decision by any single party
Because every signed transaction locks in its exact Fee value, the network always burns precisely what was specified, even if that is more than the current minimum
Not every transfer burns the same amount. Certain actions cost noticeably more because they place a heavier load on the network. Based on the cost table, here is how it breaks down:
Transaction Type
Cost Before Load Scaling
Standard transaction (most payments)
10 drops (0.00001 $XRP)
Multi-signed transaction
10 drops × (1 + number of signatures)
Escrow finish with fulfillment
10 drops × (33 + fulfillment size in bytes ÷ 16)
AccountDelete transaction
200,000 drops (0.2 $XRP)
AMMCreate transaction
200,000 drops (0.2 $XRP)
Key Reset (SetRegularKey under specific conditions)
0 drops
A regular payment, the kind most people send, burns a fraction of a cent. Deleting an account or creating an automated market maker pool burns considerably more, since those actions do more work on the ledger. During periods of high congestion, even the 10-drop baseline can climb well above normal through the load-based scaling XRPL.org describes.
Since XRPL.org itself does not publish a running total, tracking cumulative destruction means turning to blockchain explorers built on top of the ledger's public data. According to XRPScan, the most widely cited tracker for this figure, the cumulative total reached roughly 14 million by mid-2025 and has since climbed to approximately 14.4 million as of July 2026.
Put that in context against the numbers:
It's total supply was fixed at 100 billion units at genesis, all created at once with no ongoing mining or inflation
That 14.4 million figure represents a tiny fraction of the total supply, somewhere around 0.0144 percent
Recent estimates put the annual burn pace at somewhere close to 1 million $XRP per year during active network usage, though this scales up or down with actual transaction volume
The pace is genuinely slow. This was never designed as a scarcity mechanism the way some other projects use scheduled or event-driven burns. It is a byproduct of network security, and the ledger's architects built it that way on purpose.
Technically, yes, though with an important asterisk. Since burned $XRP is destroyed permanently and can never be reissued, and there is no mining or staking reward creating new supply, the total amount of $XRP in existence can only ever go down from its original 100 billion. That satisfies the basic definition of deflationary supply.
That said, it is worth clearing up a common mix-up. Ripple's escrow releases, where large batches of $XRP are unlocked on a schedule from accounts Ripple controls, are not burns. Escrowed XRP moves back into circulation; it does not get destroyed. Only the transaction cost mechanism actually removes XRP from existence. Confusing the two overstates how aggressive the deflation really is.
In practical terms, the burn rate is far too small to meaningfully affect $XRP's price or scarcity on its own. What it does provide is a built-in, incorruptible spam deterrent that scales with network activity.
XRP burn is a small but permanent side effect of how the $XRP Ledger keeps itself clean. Every transaction destroys a tiny transaction cost, ranging from a fraction of a cent for standard payments up to 0.2 $XRP for heavier operations like account deletion, and none of that ever goes to a validator or company. Cumulative destruction has crossed roughly 14.4 million $XRP since 2012, a genuinely deflationary trend, just a remarkably slow one against a 100 billion token supply. The mechanism was never meant to move markets. It was built to keep spam off a network that now settles millions of transactions a year.
This article is for educational and informational purposes only and should not be considered financial or investment advice. Always do your own research before making decisions related to any crypto asset.
