XRPL Reserve Debate Splits Community Over Adoption vs Security

Vet argues that reserve requirements serve as an important defense against spam attacks and excessive network resource usage.

An XRPL validator has said that he will not vote for another reduction in its account reserves, sparking a community debate over whether lower costs would help adoption or weaken network protections.

The dispute has split community members between those who see lower reserves as necessary for easier onboarding and those who argue that it could strip out a security buffer that the network still needs.

XRPL Reserve Debate Revisits Network Costs and Spam Protection

In a July 20 post on X, Hussein Zangana, the XRP Ledger Foundation’s director of community, told his nearly 57,000 followers that the network’s account reserves have already fallen significantly since the network launched.

In 2012, activating an account required 1,000 XRP in base reserves, with Jed McCaleb later reducing the requirement to 200 XRP. From there, reserves came down gradually through validator votes rather than formal amendments, landing at today’s figures: a 1 XRP base reserve to activate an account, plus a 0.2 XRP owner reserve for each token held, including RLUSD or USDC, or for each of up to 32 NFTs.

He said that he’d backed earlier reductions himself, and at the time, the cuts had made sense given XRP’s rising price and XRPL’s beefier server capacity. However, as things stand, he’s drawing a different line.

“We have to be very careful in arbitrarily lowering reserves,” Vet wrote. “There’s a clear reason for its existence and security comes first. The debate should start there.”

According to him, reserves were designed to protect network resources, including storage and memory, by making it more expensive to create a large number of accounts that could be used for spam or DDoS attacks.

The dUNL validator added that he would only vote to lower reserves if the lower requirements could provide the same level of protection the current one does. He further confirmed that he would definitely not vote for higher transaction fees, which he claimed many community members had been using “as an argument to compensate for lower reserves.”

You may also like:

Where the Rest of the Community Landed

Vet did face some pushback, especially from community member Daniel Keller, who argued that lower reserves could help the project attract more users who are unfamiliar with crypto.

According to him, the focus should be on onboarding people outside the existing crypto audience, where sponsors might want to activate accounts on their behalf while keeping down acquisition costs.

Keller also questioned whether Vet’s concerns about spam were overstated and pointed out that the ledger had handled periods of high activity in the past without lower reserves causing any issues.

Meanwhile, another community member, Chris Thompson, raised a different worry: that lowering reserves could make it easier to create more easily disposable wallets, which could increase the surface area for possible exploitation.

Recent XRPL updates have also seen uneven adoption, with only 43% of nodes moving to its v3.2.0 upgrade. The update introduced changes such as reduced memory usage for nodes of between 30% and 40%, as well as improvements tied to network operations.