Why XRPL has a transaction cost
The transaction cost is an anti-abuse mechanism. A server must verify, relay, and process candidate transactions, so unlimited free submissions could consume network resources. Requiring each distributed transaction to risk a small amount of XRP makes sustained spam progressively expensive.
This mechanism is different from a payment to a block producer. No validator receives the cost. When a transaction is included in a validated ledger, the XRP specified in its Fee field is irrevocably destroyed.
The current reference cost
As reviewed on August 22, 2026, official XRPL documentation lists 10 drops, equal to 0.00001 XRP, as the minimum cost for a standard reference transaction before load scaling. One XRP contains one million drops.
This value is not a permanent promise. Fee voting can change the reference cost, and real-time load can increase what a server requires. Applications should query current conditions and place sensible maximums on automatically selected fees.
Load scaling and the transaction queue
Servers maintain load-based and open-ledger thresholds. A transaction below a server's load threshold can be ignored. A transaction that clears that threshold but not the current open-ledger requirement may wait in a queue for a later ledger.
The open-ledger requirement rises as an in-progress ledger fills beyond its soft limit. This prioritizes transactions offering higher costs during bursts of activity while allowing normal requirements to fall again when load subsides.
Open the related live demo or evidence lab →Failed transactions and special cases
Some failed transactions are still included in validated ledgers with a tec result and therefore destroy their specified cost. That prevents invalid or unsuccessful attempts from becoming a free way to consume network resources. Failures rejected before ledger inclusion do not change balances.
Some transaction types have higher unscaled costs because they require additional work. Multi-signed transactions scale with signature count, while specific operations such as account deletion or AMM creation have distinct base costs. Always check the current protocol documentation before treating a number as fixed.