RLUSD and the $13 Trillion Number: A Forensic Read of Ripple's Enterprise Treasury Strategy
Last month, a stablecoin carrying roughly $2.4 billion in circulating supply processed an estimated $750 million in daily transaction volume. That implies a turnover ratio near 31% per day. For a settlement asset, that is an unusual number, and it deserves more scrutiny than the growth rate attached to it.
The headline figure in Ripple's recent messaging is $13 trillion. That number now circulates as though it were a forecast. It is not. It is a total addressable market benchmark, and a TAM benchmark has never once been reconciled into a revenue line. The distance between a TAM figure and a booking is where most crypto narratives quietly do their work.
I want to be explicit about the evidentiary base before going further. Nearly every quantitative claim in this analysis originates from Jack McDonald, Ripple's senior vice president for its stablecoin business. No third-party attestation appears in the record. No independent on-chain reconciliation appears in the record. Follow the metadata, not the mood.
RLUSD is Ripple's fiat-backed stablecoin, redeemable one-to-one against dollar reserves. It issues on two networks: the XRP Ledger and Ethereum. Circulation sits near $2.4 billion. The reported growth rate is over 50% for the month, which sounds substantial until you divide it by the base.
The commercial architecture is the more interesting object. Ripple acquired GTreasury, an enterprise treasury management firm, for approximately $1 billion. GTreasury brings roughly 1,200 corporate treasury clients, people who already move money across subsidiaries, manage liquidity, and settle cross-border obligations. Ripple's stablecoin leadership frames these clients as the distribution surface for RLUSD. Named partners include Franklin Templeton, on tokenized money-market funds, and DBS, on lending and settlement rails.
The product positioning is compliance-native. RLUSD is marketed as a settlement asset for enterprise treasuries rather than a retail trading coin. That framing matters, because enterprise treasuries are the most compliance-sensitive pool of capital in finance. They do not care about a validator set. They care about custody, audit, and the ability to move a nine-figure balance without a counterparty surprise. In a sideways market, that is a genuinely different buyer than the one chasing yield.
Here is where the record is thin. The source material does not disclose the reserve composition, the custodian, or the audit frequency. For a fiat-backed stablecoin, those three items are the entire product. Everything else, chain choice, marketing, partnership logos, is secondary. Data doesn't care about your timeline, and it does not care about a partnership announcement either.
Now the forensics.
The supply distribution is the first anomaly. RLUSD issues on two chains, and on paper the XRP Ledger is home. In practice, Ethereum carries roughly $1.4 billion against the XRP Ledger's $1 billion. The chain that shares Ripple's name holds the minority of the float.
I have seen this pattern before. In 2021, while tracing wallet clusters around the Bored Ape collection, the metadata told a story the floor price refused to tell. Here the metadata says the same kind of thing: institutions are choosing the network with the deepest liquidity and the widest DeFi composability, not the network with the brand alignment. Ethereum wins on network effect. The XRP-native stablecoin narrative is weakened by Ripple's own issuance data, not by a competitor's spin.
The turnover ratio is the second anomaly. $750 million in daily volume against $2.4 billion in circulation implies roughly 31% turnover per day. USDC and USDT turn over at fractions of that rate on a relative basis. Two readings are possible, and I will not pretend the data settles which one is correct.
Reading one: RLUSD has found a genuinely high-velocity settlement use case. Subsidiaries sweep balances, treasuries fund and defund intraday, cross-border legs clear quickly. High turnover is the signature of a working settlement layer.
Reading two: the volume is inflated by circular transfers. In an enterprise treasury context, the same dollars can move between subsidiaries repeatedly and register as volume on each hop. Corporate cash pooling is precisely this, the same liquidity circulated across entities to optimize interest and funding. If RLUSD is running cash-pooling on-chain, the transaction count is real but the incremental economic activity is small.
The source material gives no metric definition for the $750 million. Without knowing whether intercompany transfers are netted or gross, the number cannot be classified as demand or as plumbing. The unaudited variable is the one that decides the outcome, and here the variable is unlabeled.
Next, the reserve economics, the question the source material never asks. RLUSD is backed by dollar reserves, typically cash and short-dated Treasuries. In the current rate environment those reserves generate yield. The interview does not say where that yield goes. This is not a footnote. It is potentially the core of the business model.
If the reserve yield accrues entirely to Ripple, then RLUSD is functionally an on-chain money-market fund wrapped in a settlement interface. The revenue is the spread between reserve yield and operating cost, plus transaction fees. That is a legitimate business, and it is the same structure that makes Circle profitable. But it is a spread business, and its economics are governed by interest rates, not by token adoption curves.
If some reserve yield flows back to holders, the enterprise value proposition changes substantially. Treasuries would have a reason to park idle balances in RLUSD beyond settlement convenience. The source material is silent on this, and silence on a money question is itself information. When a stablecoin operator declines to discuss reserve yield, the default assumption should be that the yield is retained.
Now the TAM gap. The $13 trillion figure is the aggregate transaction volume flowing through GTreasury's client base. It is not RLUSD's addressable float, and it is not a revenue projection. It is the gross throughput of 1,200 enterprise treasuries. Mapping that throughput onto stablecoin float requires assumptions about capture rate, retention, and the share of treasury flows that will ever touch a chain. None of those assumptions are provided.
Do the arithmetic that is available. Ripple paid roughly $1 billion for GTreasury. Divided across 1,200 named clients, that is approximately $833,000 per client. That per-client figure is the price Ripple placed on access to the channel. It implies a very high expected lifetime value per relationship, which in turn implies Ripple expects meaningful balance capture, not just transaction routing. A channel that only routes small settlement legs does not return $833,000 per client.
That is the strategic bet. It is a channel purchase, not a technology purchase. Stablecoins are not technically differentiated at this stage. Issuance, redemption, and multi-chain deployment are solved problems. The moat, if one exists, is distribution plus compliance, and Ripple bought the distribution.
Against that sits the size reality. RLUSD at $2.4 billion is a rounding error next to USDT's reported $120 billion-plus and USDC's reported $40 billion-plus. That is a gap of one to two orders of magnitude. The stablecoin market exhibits strong network effects: liquidity attracts liquidity, and integration attracts integration. A $2.4 billion coin does not threaten a $120 billion coin. It can only occupy a niche the incumbents have not prioritized, and enterprise treasury settlement is exactly such a niche, which is why the channel logic holds even while the market-share logic does not.
The compliance position deserves its own paragraph. Enterprise treasuries cannot hold USDT at scale for US regulatory reasons. That is the wedge. RLUSD's bet is that compliance-native issuance is worth a liquidity discount to corporate treasurers who cannot touch the alternatives. That is a coherent thesis. It is also fragile, because it depends entirely on trust in the issuer's reserves, and trust in reserves depends on disclosure. The source material discloses none.
Based on my audit experience, I weight transparency failures heavily. In 2022, I reconstructed the Terra liquidity drain transaction by transaction, and the lesson was not that an asset can fail. It was that opacity and fragility were not separate problems. Opacity was the mechanism by which fragility stayed hidden until it was terminal. RLUSD is not Terra. It is fiat-backed and structurally different. But the disclosure discipline carries over. A stablecoin that does not publish a monthly attestation from a named, reputable firm is asking the market to take its word. Enterprise treasuries do not take words.
The XRP transmission channel is where the narrative stretches again. RLUSD is not an investment asset; it does not appreciate. Its value to XRP holders is indirect. RLUSD activity generates XRPL fees and draws users onto the network, which could lift demand for XRP over time. But the Ethereum float is the larger slice. Value capture is leaking to the chain the product is nominally not built around. If RLUSD succeeds on Ethereum, the XRP Ledger benefits least.
The institutional partnerships, Franklin Templeton on tokenized money-market funds and DBS on lending, are credible logos. They are also early-stage. A partnership announcement and a funded, exclusive, revenue-generating integration are different states. The source material provides the logos, not the flows. In my ETF pipeline work, I found institutional accumulation consistently preceding retail rallies by roughly forty-eight hours, but that signal was measurable only because the flow data was public and daily. RLUSD offers no equivalent public flow ledger. The partnerships are therefore unverifiable at the resolution that would actually matter.
Here is the counter-thesis, and I will state it as a correlation problem rather than a forecast.
The bear reading of RLUSD is straightforward: small float, unverified data, one-to-two-order-of-magnitude gap to incumbents. That reading is correct but incomplete. The more interesting error is the assumption that the enterprise-treasury-on-chain trend, if it is real, benefits Ripple specifically.
Consider the causal chain the narrative requires. Enterprise treasuries move on-chain. Therefore they adopt RLUSD. Therefore Ripple captures the float and the reserve yield. Each arrow is an assumption. The first arrow is plausible; corporate treasuries do have real reasons to settle on-chain, and a compliant, audited stablecoin is a prerequisite for that. The second arrow is not established. Treasuries may adopt USDC, or PYUSD, or a bank-issued stablecoin, or tokenized deposits from their existing banking relationships. Ripple's channel, 1,200 GTreasury clients, is an advantage, but a channel is a starting position, not a finish line.
There is a second blind spot. High turnover is being read as a strength. In treasury operations, high gross turnover with low net balances is normal and unimpressive. If RLUSD's $750 million daily volume is largely intercompany circulation, then the metric measures plumbing activity, not adoption. The data cannot distinguish the two, which means the celebratory reading is being chosen for narrative reasons, not analytical ones. Follow the metadata, not the mood.
The forward signal is not the growth rate. It is three disclosures that have not yet appeared.
First, a reserve attestation, with a named auditor, a monthly cadence, and a published composition. Second, a GTreasury conversion metric, how many of the 1,200 treasury clients actually hold RLUSD balances rather than merely touch it. Third, the XRP Ledger to Ethereum issuance ratio. If the Ethereum share keeps climbing, the XRP-native stablecoin thesis erodes further, and with it the indirect case for XRP demand.
Watch those three numbers. If none of them surface within two quarters, the $13 trillion figure remains what it started as: a memorable number attached to an unverified business. Data doesn't care about your timeline.