XRPL validator Vet said he won't vote for another reduction in account reserves, arguing that security must come first. The stance puts him at odds with community members who see lower reserves as a path to broader adoption.
Why Vet changed his stance
Vet backed earlier reserve reductions but now opposes further cuts. He says reserves protect network resources — storage and memory — by making it expensive to create many accounts for spam or DDoS attacks. He also confirmed he wouldn't vote for higher transaction fees as compensation for lower reserves.
The adoption argument
Community member Daniel Keller argued lower reserves could help onboard users outside crypto and that spam concerns are overstated. Chris Thompson warned lower reserves could increase disposable wallets, raising exploitation risks. The split reflects a familiar tension: lower barriers vs. stronger protections.
A history of cuts
In 2012, activating an XRPL account required 1,000 XRP. That was later reduced to 200 XRP by Jed McCaleb. Current reserves sit at 1 XRP base reserve to activate an account, plus 0.2 XRP owner reserve per token or per up to 32 NFTs. Hussein Zangana, XRPL Foundation's director of community, posted on July 20 that reserves have fallen significantly since 2012.
The upgrade gap
Recent XRPL update v3.2.0 reduced node memory usage by 30-40% and improved network operations. But only 43% of nodes have upgraded. That low adoption rate could complicate any future changes — including reserve adjustments. Vet's position suggests further cuts won't happen without a broader consensus. And that consensus is far from settled.
