XRPL Fee Voting: How the Network Sets Transaction Costs
XRPL fee voting is the decentralized process by which the XRP Ledger's validator network collectively determines the base transaction cost and reserve requirements. Rather than having these values fixed in code, they can evolve as the network grows and the value of XRP changes over time.
How Fee Voting Works
Validator operators can set their preferred fee settings in the [voting] stanza of the rippled.cfg configuration file. The network then follows this process:
- Each validator periodically expresses its fee preferences to the network, approximately once every 15 minutes
- In the ledger immediately before a "flag ledger," each validator whose preferences differ from current settings distributes a "vote" message alongside its ledger validation
- In the flag ledger, validators tally the votes from other validators they trust (their UNL)
- Each validator computes the median vote for each setting
- If the median differs from current settings, validators insert a SetFee pseudo-transaction into their proposed ledger
- New settings take effect starting with the ledger after the flag ledger, if a SetFee pseudo-transaction achieves consensus
Why Fee Voting Exists
The purpose of fee voting is to allow long-term adjustments to XRP's value and network capabilities without requiring a hard fork. As XRP's price increases, the USD equivalent of the base fee (currently ~$0.0000152) would become even more negligible, potentially weakening its spam-prevention effectiveness. Fee voting allows validators to respond to these changes.
The XRPL documentation notes: "Changes must be made periodically to adjust to long-term changes in the value of XRP and the costs and capabilities of network nodes."
Safety Considerations for Validators
Fee preferences must be set carefully. If the reference transaction cost is too low and adopted by more than 50% of trusted validators, malicious users could overload the network with spam transactions, consuming CPU and bandwidth. Similarly, reserve settings that are too low could allow excessive ledger state growth.
Conversely, fees set too high would reduce accessibility and utility. The fee voting mechanism requires validators to weigh these competing concerns to find a balance that serves the network's long-term health.
Historical Fee Changes
The XRPFees amendment, which enabled more flexible fee voting, expanded the maximum possible fee values. Before this amendment, values were limited by the internal data type of the legacy FeeSettings ledger entry format. The current base fee of 10 drops has remained remarkably stable for years, reflecting the fact that XRP's price appreciation has kept the USD equivalent low enough to remain effective as a spam deterrent.
