BTC/USD $68,420 +2.8%
ETH/USD $3,540 +1.4%
SOL/USD $142.80 -0.6%
BNB/USD $605.20 +0.9%
XRP/USD $0.62 -1.2%
DOGE/USD $0.18 +5.4%
BTC/USD $68,420 +2.8%
ETH/USD $3,540 +1.4%
SOL/USD $142.80 -0.6%
BNB/USD $605.20 +0.9%
XRP/USD $0.62 -1.2%
DOGE/USD $0.18 +5.4%
Altcoins

RLUSD crossed a billion dollars on the XRP Ledger. The share everyone is quoting is wrong.

Ripple USD passed a billion dollars of supply on the XRP Ledger this week. Read both chains at the same moment and the split is 43.5% XRPL, 56.5% Ethereum, which is not the "roughly half" tha

AnonymousCryptoCompass newsroom
August 31, 2026
5 min read
NEWS
RLUSD crossed a billion dollars on the XRP Ledger. The share everyone is quoting is wrong.
CryptoCompass editorial visual for altcoins coverage.

Ripple USD passed a billion dollars of supply on the XRP Ledger this week. Read both chains at the same moment and the split is 43.5% XRPL, 56.5% Ethereum, which is not the "roughly half" that has been circulating since August 26.

What the ledger reports

The XRPL figure is 1,039,586,343.75 RLUSD, read at validated ledger 106,670,866 on August 31. It comes from the gateway_balances call on the issuing account, rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De, which returns what the protocol calls that account's obligations.

The Ethereum figure comes from totalSupply() on the ERC-20 contract: 1,350,048,389.52. Add them and RLUSD is a $2.39 billion asset, of which the XRP Ledger holds a little under 44%.

That matters for a small reason and a larger one. The small reason is accuracy: several write-ups this week put XRPL at or near half of all RLUSD, and it is not there. The larger reason is that the two figures are produced by different machinery, so adding them and taking a percentage hides what the XRPL number is actually counting.

A trust line is a decision

On Ethereum, RLUSD is a contract balance. Anyone can receive it. The recipient takes no prior action, signs nothing, and pays nothing to hold it.

On the XRP Ledger, RLUSD is an issued currency. It has no contract. It exists as balances on trust lines, each one a ledger object that a holder created, pointing at Ripple's issuing account and naming a limit. The protocol reports the sum of those balances as the issuer's obligations, which is the correct word: what the issuer owes to holders.

Creating that line is not free. Each trust line raises the holder's XRP owner reserve by 0.2 XRP, locked for as long as the line stays open. So every account holding RLUSD on XRPL performed a deliberate act, paid a standing cost, and named Ripple as the counterparty it is willing to be exposed to.

Three flags on the issuing account fill in what that exposure looks like. I checked each one on the account itself:

  • lsfNoFreeze is not set. Ripple did not permanently give up the ability to freeze an individual RLUSD trust line. It can still do it.
  • lsfRequireAuth is not set. Ripple does not gate who may hold RLUSD in the first place. Anyone can open the line without asking.
  • Trust line clawback is not enabled, and the master key on the issuing account is disabled.

Read together, that is a specific posture: open access on the way in, freeze authority retained afterward, no clawback, and operational signing separated from the master key. A holder taking on RLUSD on XRPL is agreeing to all four.

None of that is a criticism. Every regulated dollar stablecoin worth using has a freeze function somewhere, and the XRP Ledger puts the setting in a protocol flag anyone can read, where an ERC-20 keeps it in contract code. The point is that the billion on XRPL and the $1.35 billion on Ethereum are not interchangeable quantities. One of them is a billion dollars of counterparty exposure that people signed up for one account at a time.

The rails that would use it are not switched on

A billion dollars of on-ledger stablecoin is only useful once something on the ledger can put it to work as collateral, and the two amendments that would do that are still short of activation.

I pulled the vote board in the same run. XLS-65 Single Asset Vault stands at 13 of the 28 validations it needs. XLS-66 Lending Protocol stands at 12. Both counts have been flat since August 25. The validation set is 35 and the threshold is 28, and a passing amendment then has to hold that support for two continuous weeks before it activates.

Those are the two amendments underneath the credit market that Ripple, Clearpool and Cicada Partners announced on August 20. Loans in that design are denominated in RLUSD. So the collateral asset reached a billion dollars on the ledger before validators enabled the primitives that would lend against it.

Feature amendments in rippled ship default-no, which means each of those counts moves only when an operator makes a deliberate config change. Nobody is drifting into it on an upgrade. Twelve and thirteen are choices.

What I would watch

Three checkable things, none of them a price call.

Whether the XRPL share keeps climbing. At 43.5% it is gaining but behind. If it passes Ethereum's share before year end, the issuance mix has genuinely moved to the XRP Ledger. If it stalls in the low forties, this week was a milestone with no trend behind it.

Whether the vault and lending counts move now. They have been flat for six days and near half for over a month. A billion dollars of RLUSD sitting on the ledger is the strongest argument yet for switching them on. If the counts are still at 13 and 12 in mid-September, then validator appetite for on-ledger credit is the binding constraint, and stablecoin availability never was.

Whether the supply spreads. An obligations figure counts what was issued and held. It says nothing about how many hands it passed through, or whether most of it is parked in a handful of treasury accounts. Distribution is the number that would turn this from issuance into usage, and it is not the number anyone quoted this week.

That last one is the honest limit on the whole story. A billion dollars minted and held is a real milestone and a weak proxy for adoption. Turning the first into the second runs through what custody and structure look like for holdings this size, and none of that work shows up in an obligations figure.