XRP Burn Rate Explained: Can XRP Become Deflationary?
XRP is already deflationary under a narrow supply definition because validated transaction fees are destroyed and no replacement XRP is issued by the protocol. The effect is real but small: a July 13, 2026 ledger snapshot implies that about 14.36 million XRP, only 0.01436% of the original 100 billion, had been destroyed. Even at 1,000 transactions every second and the 10 drop reference cost, burning another 1% of original supply would take about 3,171 years.
What happens to an XRP transaction fee?
The XRP Ledger uses a transaction cost to discourage spam. According to the official transaction cost documentation, a standard reference transaction currently requires a minimum of 10 drops. One XRP contains one million drops, so 10 drops equals 0.00001 XRP.
The fee does not go to a validator, miner, company, or treasury. It is irrevocably destroyed. The sender signs a Fee value, and that exact XRP amount disappears when the transaction is included in a validated ledger. Network load can make the required cost rise, a sender can specify more than the minimum, and certain transaction types cost more. For example, the official table lists 200,000 drops for AMMCreate and AccountDelete before load scaling.
A validated failure with a tec result can still destroy its fee because it reached the shared ledger. A transaction rejected before validation does not change a balance and does not burn XRP. The documentation also describes a narrow zero cost key reset exception. Therefore, transaction count multiplied by 10 drops is a useful baseline, not an exact measurement of every ledger.
A dated snapshot of XRP already destroyed
The official XRP Ledger learning portal states that XRP supply is capped at 100 billion XRP. The official ledger API exposes total_coins, the total drops owned by accounts after transaction costs have been removed. It is a protocol supply field, not the same thing as liquid or actively traded supply, because inaccessible accounts and locked balances can still be included.
At 10:20:51 UTC on July 13, 2026, validated ledger 105,567,998 reported 99,985,637,420.970109 XRP in total_coins. Subtracting that value from the original 100 billion produces a cumulative destroyed amount of 14,362,579.029891 XRP. That equals about 0.014362579% of original supply, leaving 99.985637421% in the ledger total.
Snapshot method: original supply of 100,000,000,000 XRP less ledger total_coins of 99,985,637,420.970109 XRP. The difference is cumulative protocol destruction, not an estimate of coins lost through forgotten keys.
How burn scales with transaction volume
The baseline equation is simple: transactions each second multiplied by 31,536,000 seconds in a 365 day year, multiplied by XRP destroyed per transaction. At the 10 drop reference cost, one sustained transaction each second destroys 315.36 XRP per year. Every tenfold increase in transaction rate creates a tenfold increase in baseline burn.
The scenarios below are explicit sensitivity tests, not forecasts of network usage. One, 10, and 100 transactions each second represent progressively busier sustained activity. The 1,000 transaction scenario is a deliberately demanding upper case for the burn calculation. It does not assert that this level is current traffic or promise that it will occur continuously.
| Transactions each second | Transactions per year | XRP burned per year at 10 drops | Years to burn 1 million XRP | Years to burn 1 billion XRP |
|---|---|---|---|---|
| 1 | 31.536 million | 315.36 | 3,170.98 | 3,170,979 |
| 10 | 315.36 million | 3,153.60 | 317.10 | 317,098 |
| 100 | 3.1536 billion | 31,536 | 31.71 | 31,710 |
| 1,000 | 31.536 billion | 315,360 | 3.17 | 3,171 |
The meaningful supply test
Calling an asset deflationary can be technically correct while hiding scale. A useful threshold is 1% of original supply, equal to 1 billion XRP. At 100 transactions each second and 10 drops each, reaching that threshold takes about 31,710 years. At 1,000 transactions each second, it still takes about 3,171 years.
Reverse the equation to see what a ten year target demands. Burning 1 billion XRP over ten years at the reference cost would require an average of about 317,098 validated transactions every second, continuously. If activity instead averaged 100 transactions each second, the average destroyed fee would need to be about 0.031710 XRP per transaction, or 31,710 drops. That is roughly 3,171 times the present 10 drop reference cost.
Higher fees can change the result, but assumptions matter
The 10 drop reference cost is not a permanent economic constant. XRPL fee voting allows trusted validator preferences to influence the network setting, while load scaling can raise the cost needed for timely inclusion. Special transactions and multiple signatures can also destroy more than 10 drops.
At 100 transactions each second, an average fee of 100 drops would destroy 315,360 XRP per year. An average of 1,000 drops, equal to 0.001 XRP, would destroy 3,153,600 XRP per year. Even the latter would require about 317 years to remove 1 billion XRP if activity, fees, and the number of seconds per year stayed constant.
Fee increases are not designed as a price support tool. Their stated purpose is protecting the network against spam and excess load. A large fee also imposes a real cost on users, so modeling higher destruction without modeling reduced demand is incomplete. Volume and fee level can influence one another.
So, can XRP become deflationary?
In protocol supply terms, XRP does not need to become deflationary. It already has a declining total_coins field because fees are destroyed and consensus does not mint replacements. Each validated fee makes the ledger total slightly lower than it was before.
That statement should not be stretched into a price prediction. Deflation in protocol units is different from lower liquid supply, lower exchange balances, rising purchasing power, or positive investment returns. Demand can fall faster than supply. Regulation, utility, market liquidity, custody failures, macro conditions, and holder behavior can outweigh a burn measured in tiny fractions of original supply.
The best interpretation is precise: XRP has a permanent destruction mechanism, and its cumulative effect is publicly auditable. At the present reference cost, ordinary transaction growth alone would have to be enormous and sustained for the burn to remove a material percentage within a human investment horizon.
Burn is not yield
Fee destruction changes the network wide supply. It does not credit XRP to an individual holder. Leaving 10,000 XRP in a wallet or exchange account does not create more units merely because other users pay fees. A holder looking for account growth must separately examine the source, custody, access, and risk of any yield product.
For that comparison, use the XRP yield calculator, read how to earn yield on XRP, and review the platform's security model. XORA describes its headline as up to 22% APY value, 15% native XRP yield, treasury subsidised during a disclosed bootstrap, plus estimated XORA reward value. The estimated reward component is not native XRP, rates can change, and no return is guaranteed.
Assumptions and risk disclosure
- Scenario years use 365 days and 31,536,000 seconds.
- Base cases assume every counted transaction is validated and destroys exactly 10 drops.
- Real fees vary with transaction type, signatures, load, user settings, and future validator decisions.
- Transaction rates are continuous scenario averages, not forecasts or claims about present usage.
- The supply snapshot uses
total_coins. It is not circulating supply and does not estimate inaccessible XRP. - Crypto assets are volatile. Fee destruction does not guarantee price appreciation, income, liquidity, or protection from loss.
FAQ
Does the XRP Ledger burn XRP on every transaction?
A transaction included in a validated ledger normally destroys the XRP specified in its Fee field. This includes successful transactions and validated failures with tec result codes. A rejected transaction that never reaches a validated ledger does not destroy a fee, and a narrow key reset exception can use a zero fee.
How much XRP had been burned by July 13, 2026?
Validated ledger 105,567,998 reported 99,985,637,420.970109 XRP in total_coins at 10:20:51 UTC on July 13, 2026. Compared with the original 100 billion XRP, the cumulative difference was 14,362,579.029891 XRP, or about 0.01436% of original supply.
Is XRP deflationary?
Under a narrow protocol supply definition, yes. XRP transaction costs are destroyed and the consensus protocol does not issue replacement XRP, so total_coins trends downward. The decline is small relative to the original 100 billion XRP and does not guarantee price appreciation.
How long would it take to burn 1 billion XRP at 1,000 transactions per second?
At a constant 1,000 transactions per second and exactly 10 drops per transaction, annual destruction would be 315,360 XRP. Burning 1 billion XRP, equal to 1% of original supply, would take about 3,171 years if every assumption stayed constant.
Does burning XRP make its price rise?
Not automatically. Fee destruction reduces protocol supply, but XRP price also depends on demand, liquidity, regulation, market conditions, custody risk, and investor behavior. The burn is a supply mechanism, not a return promise.
Sources checked
Put XRP to work while understanding the burn
The XRP burn is real, permanent, and transparent, but the base cost math shows why it should not be confused with near term income. Supply declines a little with every validated fee, while your personal XRP balance does not grow from that mechanism.
With xora.finance, readers can put XRP to work for up to 22% APY value, never guaranteed, rather than leave it idle on an exchange. That means 15% native XRP yield, treasury subsidised during a disclosed bootstrap, plus estimated XORA reward value. Rates, reward value, custody conditions, and access can change, so review the terms and risks before depositing.