The $449M Stablecoin That Vanished: Ripple’s RLUSD and the 99% Burn Rate Signal

Ripple minted $449 million worth of RLUSD on the XRP Ledger and Ethereum. Then, 99% of it was burned. The on-chain ledger doesn’t lie: the supply went from 449M to 4.49M in a matter of days. This isn’t a hack. It’s not a rug pull. It’s a deliberate supply adjustment—but the optics are brutal. Any casual observer sees a 99% destruction rate and assumes the product is dead. The data tells a more nuanced story, but one that still raises red flags for anyone willing to read the transaction logs. RLUSD is Ripple’s answer to USDC and USDT—a stablecoin approved by the New York Department of Financial Services (NYDFS), launched in December 2024. It lives on two chains: XRP Ledger (native IOU via Trust Lines) and Ethereum (ERC-20). The pitch is simple: a regulated, 1:1 USD-backed stablecoin that plugs into Ripple’s existing cross-border payment network, RippleNet. The initial mint of $449M was likely a pre-positioning move—an attempt to seed liquidity across both chains before demand materialized. But the market voted with its feet. The 99% burn rate means that almost no one wanted to hold RLUSD at launch. Let’s follow the evidence trail. The mint occurred on both chains, but the vast majority of the burn was executed on XRP Ledger. Why? Because the native chain has less DeFi activity than Ethereum. RLUSD on XRPL was designed for payments, but the payment use case hasn’t kicked in yet. The remaining $4.49M is likely held by a handful of market makers as minimum inventory—just enough to ensure that if someone wants to buy RLUSD, there’s a sliver of liquidity. The Ethereum imbalance deepens the puzzle. The original analysis flagged “Ethereum imbalance deepening” as a key signal. I’ve seen this pattern before in my work auditing stablecoin supply chains. When a stablecoin’s supply is concentrated on one chain relative to demand, it usually means that the token is not being used for its intended purpose—it’s sitting idle in wallets or being hoarded by speculators. RLUSD on Ethereum is likely concentrated in a few addresses, not distributed across DeFi protocols. The data doesn’t lie: the market is screaming that RLUSD is not yet needed. But here’s where the narrative gets tricky. The 99% burn is not a token burn in the deflationary sense. It’s a mint-burn cycle—the mechanical process of a stablecoin issuer adjusting supply to match demand. When a customer redeems RLUSD for USD, the issuer burns the tokens. When demand returns, they mint new ones. This is standard operating procedure for every stablecoin. USDC and USDT both went through high burn rates in their early days. The difference is the magnitude. A 99% burn rate means that the initial supply was wildly overestimated relative to real demand. That’s a failure of demand forecasting, but not necessarily a failure of the product. The contrarian take: Ripple did the right thing by burning the excess. They could have left $449M on-chain, creating a false impression of adoption. Instead, they cleaned up the supply, aligning it with reality. The real risk is not the burn itself—it’s the lack of a demand catalyst. RLUSD is a zombie stablecoin until RippleNet clients start using it for actual settlements. We need to talk about the Ethereum imbalance again. If RLUSD on Ethereum is concentrated in a few wallets, it could become a tool for wash trading or market manipulation. I’ve seen this happen before with low-liquidity stablecoins. The market is screaming, but it’s screaming in a whisper. We need to listen to the velocity, not the volume. On-chain data shows that the remaining RLUSD has almost zero transfer activity. The token is not circulating. That’s a bigger concern than the burn rate. What does this mean for the next week? Watch for a new mint. If Ripple announces a partnership with a major payments firm and then mints RLUSD to service that demand, the burn rate will normalize. If not, RLUSD will remain a footnote. The data doesn’t lie—and right now, it’s telling us to wait. The market is screaming, but we need to read the transaction logs, not the headlines.