HostHostDeFi › Library › Is RLUSD safe on Ethereum?
Is RLUSD safe on Ethereum? The 52-day-old institutional stablecoin
Ripple's RLUSD on Ethereum grades B (80): upgradeable proxy, unassessed controls — and ~$37.6M of daily volume on a token that's barely two months old. Young, regulated, and moving fast.
RLUSD — Ripple's US-dollar stablecoin — reached ~$2.42B in market cap in its first ~52 days on-chain: ~$42.1M of tracked Ethereum liquidity, ~12,580 holders, and ~$37.6M of 24-hour volume on our September 21, 2026 read. It grades B, score 80 on the now-familiar regulated-coin pair: an upgradeable proxy plus contract-level controls not assessed in this snapshot.
RLUSD is this series' youngest institutional token — a deployment that's already moving institutional-scale volume while its contract is still in the "not yet fully read" window.
What 52 days of $2.4B looks like
Most tokens spend their first quarter proving they deserve liquidity. RLUSD went the other way: the liquidity and the holders arrived before the deployment earned history. ~$42M of on-chain depth and $37.6M of daily volume on a two-month-old contract is the institutional distribution model — Ripple's payment rails seeded adoption, so the chain shows a mature market riding a young contract.
That inversion is exactly why the proxy warn and the unassessed-controls warn matter more than usual: the market is behaving like the contract is proven while the checklist is still marking the parts it hasn't finished reading. The B isn't a judgment on Ripple — it's the honest status of a read in progress on a contract that's already holding billions.
The proxy flag on a payments company
RLUSD's upgradeable proxy is the same design every regulated stablecoin carries — USDC's deployments flag identically, and the reasons are the same: legal process requires a controllable contract, and controllability in code means an upgrade lever. On Ripple's deployment the power set is predictable: minter, pauser, freezer for sanctioned addresses — the regulated-coin toolkit.
What's distinctive isn't the flag — it's the tempo. A 52-day-old proxy contract holding $2.4B means the operator's upgrade key became systemically important before the deployment had time to accumulate adversarial history. The checklist can't score trust earned over time into a contract that hasn't had time; it records what's visible (proxy live, source verified, pool real) and marks what isn't (controls surface, unenumerated).
Verify it live: RLUSD's flags and numbers recompute at hostdefi.com/token/ethereum/rlusd/ — worth a fresh look since this snapshot dates to September 21, 2026 and the deployment is still in its first quarter. /check-token reads the admin surface directly.
The holder count that hasn't caught up
~12,580 holders against a $2.42B cap is the inverted version of USDM's anomaly (175 holders on $6.5B): there it's concentrated; here it's simply young — the distribution hasn't spread through the wallet graph yet because retail RLUSD mostly lives where Ripple's rails deliver it, and on-chain wallets accumulate later. Both shapes flag "small holder base" variants for different reasons — concentration vs youth — and both pages exist to date that difference.
For a holder, the practical read: the holder count will climb, the contract will age, and the two warns it carries today are the two that resolve with time — assessed controls eventually get enumerated; proxies settle or get timelocked.
Where RLUSD sits among the stablecoin B's
This series now covers four regulated stablecoins at B: USDC-Arbitrum (proxy + unassessed, $79.5M pool), PYUSD (proxy + unassessed, $71M pool), RLUSD (proxy + unassessed, $42M pool, 52 days), and USDG (proxy + thin + young + unassessed, 11 days). The pattern is consistent enough to name: the regulated dollar ships as a proxy, and the checklist's B is the standing price of holding one — not a mark of failure but the honest label for operator-trust at scale.
Within that cohort, RLUSD's distinguishing feature is velocity: it's the only one whose volume-to-holder ratio is institutional-first — $37.6M daily against 12.5K wallets means the market is running ahead of the wallet graph.
The trust object, specifically
Who runs RLUSD's contract matters for reading the flags: the issuer is Ripple's stablecoin entity (issued under a NYDFS-regulated trust charter — the license is the reason the token exists in the United States at all). The proxy and the unassessed-controls surface sit on a contract operated by a company whose entire legal posture is built around custody and redemption obligations. That doesn't lower the flag's importance — a regulated operator with an upgrade key is still an operator with an upgrade key — it sharpens what the trust object is: not code-immutability, but a licensed entity's obligation stack.
The checklist's job on a token like this is to keep the two registers separate: the contract says proxy-live (a fact about architecture) and the issuer is chartered (a fact about institutions). The B grades the first; the second is the context you bring to it.
Reading the growth curve honestly
A stablecoin that reaches $2.4B in 52 days didn't get there on organic demand — it got there because the issuer and its partners minted against committed distribution. That's not a criticism; it's what "institutional stablecoin" means in practice. What it changes for a reader is the shape of the numbers: high cap + low holder count + high volume is the ledger of a token whose circulation is wholesale-first. Retail on-chain wallets are the trailing edge of the distribution, not the leading edge — which is why the holder count will look anomalous until the wallet graph catches up.
Every number on this page is the profile of a market that was provisioned rather than grown — and the checklist's warns are exactly the right shape for it: young contract, thin-for-cap pool, unassessed controls, all of which resolve on a schedule the issuer can't shortcut. The page's value for a holder isn't alarm — it's calibration: you know the deployment is young because the grade can't hide it, and you know the market is real because the volume can't fake it.
Holding it, honestly
If you hold RLUSD on Ethereum you hold Ripple's regulated dollar — a proxy contract two months into its on-chain life, with real depth, real volume, and a control surface this snapshot hasn't enumerated. The B is the interim grade of a deployment still earning its history: nothing is flagged broken; what's flagged is what's young. Date it, check it live, size it against the pool rather than the brand, and re-read it after the contract's first adversarial quarter — the snapshot on this page is the baseline it will be measured against — a date, a flag set, and a number, all publicly checkable — which is the whole point of a reserve page.
Frequently asked
Is RLUSD safe on Ethereum?
B (80) on our September 21, 2026 read — upgradeable proxy + controls not assessed, zero bad flags. ~$42M tracked liquidity, ~12,580 holders, ~52 days old, ~$37.6M daily volume. An institutional-market token on a still-young contract.
Why does RLUSD have a proxy contract?
Ripple's stablecoin carries the same design as every regulated dollar: the operator must be able to respond to legal process, so the contract ships with an upgrade lever. USDC and PYUSD flag the same way.
Is RLUSD too new to trust?
The checklist's read: real liquidity and real volume on a deployment that hasn't accumulated adversarial history. The B isn't a verdict on Ripple — it's the honest status of a read still in progress.
How many people hold RLUSD on Ethereum?
~12,580 wallets against a ~$2.42B cap — concentrated because the deployment is ~52 days old and most RLUSD lives inside Ripple's distribution rails rather than retail wallets yet.
Will RLUSD's grade improve?
Mechanically yes if nothing goes wrong: the young-token factor ages away, snapshots enumerate the admin surface, the pool deepens. The proxy flag stays — that's the regulated-dollar ceiling unless the key is burned.