Every transaction on the XRP Ledger destroys a small amount of XRP as its transaction fee, a design documented directly in XRPL’s transaction-cost and fees pages, and reflected in how the xrpl-py library models transactions. It is worth understanding on its own terms rather than through the shorthand “XRP is deflationary,” which oversimplifies what is actually happening.
Why Burn Instead of Pay-to-Validator
Most blockchains route transaction fees to miners or validators as an incentive to process transactions. XRPL does something different: the fee is destroyed outright, removed from circulating supply permanently, rather than paid to anyone. The reasoning is anti-spam design, not monetary policy. A network with near-zero transaction costs is vulnerable to being flooded with junk transactions, since there is no meaningful cost to sending garbage. Burning even a tiny fee, currently a fraction of a cent per transaction, makes spam expensive at scale while staying negligible for a legitimate user sending one payment.
The Fee Isn’t Fixed
XRPL’s transaction cost can scale up dynamically when the network is under load, specifically to price out spam during periods of high transaction volume, then drop back down under normal conditions. This is documented in the transaction-cost and fees references directly. It is a load-based anti-spam throttle, not a static tax.
Don’t Overstate the Supply Effect
It is tempting to connect “XRP gets burned on every transaction” to “XRP’s supply is meaningfully shrinking,” but that leap needs actual numbers behind it, not just the mechanism. The per-transaction burn is small by design, and whether cumulative burn across all XRPL activity adds up to a supply effect worth talking about is a separate quantitative question that this documentation does not answer on its own. Treat the burn mechanism as a spam deterrent first, and only make supply claims if you have actually done that math.
Where the Details Live
For the mechanics themselves, XRPL’s transaction-cost documentation and fees documentation are the primary references. Developers working directly with transactions can see how the fee field is modeled in the xrpl-py transaction model docs.
Educational only, not tax, legal, or investment advice. Check primary sources and speak with a qualified professional before making financial decisions.
