110 Bot Wallets Dominate RLUSD Payments on the XRP Ledger, and the Bigger Number Is Being Ignored

Bitquery spent thirty days counting RLUSD payments on the XRP Ledger and found that 110 automated wallets did most of the tapping. That's the headline. The quieter detail is the one worth carrying around.

The 30-day window

The study window is precise. September 19 to October 18. One month of activity for Ripple's dollar stablecoin, which went live in December 2024 on both the XRP Ledger and Ethereum, pulled apart and sorted into two piles. Pile one is automated traffic. Pile two is everything else, and everything else includes billions of dollars in larger transfers.

Some of those billions are issuer flows. That part deserves a pause, because issuer flows aren't demand.

When the company behind a stablecoin shuffles supply between its own addresses, mints new tokens, burns old ones, or stages liquidity ahead of a market maker, the ledger records a transfer. A big one, usually. It just isn't a person doing anything. There's no user on the other end deciding to hold, spend, or send. It's bookkeeping with a block explorer attached.

Now add the bot wallets. One hundred and ten of them, running whatever loops they run, each payment indistinguishable from a real one at the counting layer. The raw tally climbs. The story the tally tells gets worse with every increment.

Here's why the plumbing matters. Most public dashboards don't separate these categories. They query the ledger, count the transfers, and publish a number. Automated and organic, issuer and user, all in one bucket. The chart goes up. Nobody asks who's pushing.

What the split actually changes

So what does this study break, exactly? Not the stablecoin. RLUSD still works. Transfers still settle, finality on the XRP Ledger still arrives in seconds, and the smart contract side on Ethereum is untouched by any of this. The rails are fine.

What breaks is the metric.

Transaction count has been the laziest number in crypto for years, and stablecoins are where the laziness shows most. A payments product isn't healthy because a script pings it 40,000 times a month. It's healthy when someone with a payroll run, a remittance corridor, or a trading desk decides to move real money through it and comes back next month to do it again. Those are different questions, and only one of them shows up in a count.

Ask yourself this. Does anyone honestly believe the health of a dollar stablecoin can be measured by how often an automated wallet touches it? If the answer is no, then why is that number still the first one quoted in every market recap?

The second thing this changes is how we read the billions. Once you separate automation from size, you notice that the large transfers exist, they're substantial, and a meaningful share of them trace back to the issuer rather than to customers. That's not a scandal. It's what a young stablecoin looks like in its first year, when the company is still seeding liquidity and building out distribution before organic flow shows up. But reporting it as volume is dishonest by omission.

My take: the 110 figure isn't a scandal either. It's a labeling problem. Bots exist on every chain, on every stablecoin, and they always have. The failure here belongs to the data layer that never bothered to tag them, then sold the resulting number as adoption.

Winners in this? Analytics shops that do the unglamorous work of classifying addresses. Bitquery gets to own a niche now. Losers? Any team that built a growth narrative on raw transfer counts and now has to explain the composition. And honestly, every reporter who quoted RLUSD volume this fall without asking the obvious follow-up question. I'll include myself in that group.

What to watch next

Three things, and they're all measurable.

First, the bot share. Run the same study on the next 30-day window and see whether those 110 wallets still dominate. My guess is they'll, and the share stays stubbornly high for a while, because automated payments on a low-fee chain are cheap to keep running. The interesting signal is the ratio. If bot volume holds flat while organic transfers climb, that's a stablecoin finding product fit. If both freeze, the count was always noise.

Second, watch whether the tooling catches up. If the major dashboards start splitting automated from human, issuer from customer, by the end of the year, this study did its job. In simple terms, that's the whole test. Better labels force better questions. Better questions force teams to compete on the metric that actually means something.

Third, watch where RLUSD's supply goes, not how many times it moves. Supply growth plus real counterparties is a signal. Supply growth plus a handful of issuer addresses is a launch strategy. There's nothing wrong with either, as long as we stop confusing the two.

For everyday users, nothing changes overnight. Your transfer still settles. Your balance still reads the same. But for anyone reading dashboards to figure out which stablecoin is actually being used, the number you were watching just lost a lot of its meaning.

The change comes at a time when stablecoin supply is racing toward records and every issuer is publishing its own version of traction. A 110-wallet bot cluster on a one-year-old stablecoin is a small finding. The methodological hole it exposes isn't.