The XRP Ledger's fee mechanism is elegantly designed to balance accessibility with network protection. Rather than using a simple fixed fee, XRPL employs a dynamic system that adjusts costs in real time based on network demand.

The Three Fee Thresholds

Every transaction on the XRPL goes through a two-stage evaluation by each rippled server node:

• Load-based threshold: If the transaction fee is below this level, the server ignores and drops the transaction completely.
• Open ledger cost: If the fee meets the open ledger threshold, the transaction is included in the current ledger being built.
• Queue: Transactions between the two thresholds are queued for inclusion in a future ledger.

Base Fee and Load Factor

The formula governing XRP transaction cost is: fee (drops) = base_fee × load_factor ÷ load_base. The base_fee is 10 drops under standard conditions. The load_base is 256. The load_factor is a dynamic multiplier that each node adjusts independently based on observed transaction volume.

When a server's load_factor equals its load_base (both 256), the effective fee equals the base_fee minimum of 10 drops. As network activity increases, each node raises its local load_factor. Transactions submitted with fees that fall below a node's current threshold are rejected by that node.

Open Ledger Cost and Exponential Escalation

The open ledger cost is a separate, escalating fee level that rises sharply as each ledger fills up. The algorithm uses an exponential curve — meaning small increases in demand above the 200 TPS threshold can cause disproportionately large fee increases. This is intentional: the system prioritizes stability over transaction volume.

Ripple CTO David Schwartz explained in March 2026 that if even one more transaction per second arrives than the network can comfortably process, fees rise to whatever level is needed to bring volume back within capacity. Theoretically, fees have no upper ceiling during extreme congestion.

Validator Role in Fee Determination

Validators on the XRPL independently estimate how many transactions fit in each ledger based on recent history. They collectively determine the fee curve through consensus — no single entity, including Ripple Labs, sets the fee. Validators require at least 80% agreement to confirm transaction sets, balancing the speeds of the fastest and slowest nodes in the network.

Transaction Queue Mechanics

When a transaction's fee falls between the load threshold and the open ledger cost, it enters a queue. Queued transactions are sorted by fee level first, then by arrival time for equal-fee entries. As each new ledger opens, queued transactions are considered for inclusion in fee-descending order.

Every signed transaction must include the transaction cost in the Fee field. This field cannot be changed after signing, even if network conditions change before submission.