Ripple Burns 1,363,614 RLUSD on XRP (XRP) Ledger, Remints on Ethereum

1.36M RLUSD Shifts Chains

Ripple executed a significant cross-chain adjustment of its dollar-backed stablecoin over the weekend, with on-chain data showing 1,363,614.85 RLUSD permanently removed from the XRP Ledger on September 6. The burn transaction routed the tokens to an irretrievable address, and just seconds later an identical 1,363,614.85 RLUSD was minted on Ethereum — a near-simultaneous pairing that points to issuer-side coordination rather than any organic change in circulating supply. The on-chain transaction trail confirms the burn-and-mint sequence, and the timing gap of only a few seconds strongly suggests both legs were executed by Ripple itself rather than by an independent holder. Critically, the total RLUSD supply was left untouched: what changed is not how many tokens exist, but which network holds them. This is a relocation of existing liquidity, not an issuance event. The mechanics matter here — because Ripple controls the issuer account, it can retire tokens on one chain and recreate them on another without routing value through a third-party bridge protocol, eliminating the custody and exploit risk that wrapped-asset bridges carry. It is also a clean demonstration of why the XRP Ledger remains a practical issuance rail, with the kind of 3–5 second finality that the BIS trialed for statistics verification, even when the destination liquidity ends up on Ethereum.

on-chain transaction trailhttps://x.com/bankxrp/status/2096824805639238056?s=46

Issuer-Side Rebalancing, Not New Supply

The second stage of the movement is where the signal gets more interesting. After the RLUSD was minted on Ethereum, the newly created tokens were transferred onward to an external wallet address, a step that takes the operation beyond routine internal bookkeeping. In our reading, that hand-off suggests the tokens are being positioned for active deployment — market-making desks, trading venues, or decentralized finance applications — rather than simply parked in a treasury account. Roughly $1.36 million worth of stablecoin is a modest figure in absolute terms, but the direction is what counts: Ripple is actively managing the balance between the two supported chains, and the flow in this instance ran from the XRP Ledger toward Ethereum. For context, demand for XRP-market liquidity has been building on centralized venues too — Binance XRP spot volume hit $7.28B in August, its highest since February — and a growing XRP ecosystem gives Ripple more places to position RLUSD where it will actually be used. Unlike algorithmic stablecoins, whose pegs depend on coded incentives, RLUSD's cross-chain shifts are purely administrative: fiat-backed reserves stay in place while token representation moves to wherever DeFi and trading demand is strongest. Readers tracking the market in real time can follow live spot and futures prices on Bitget.

What the On-Chain Record Signals

COINOTAG's take: the load-bearing evidence here is the on-chain record itself — two transactions, identical amounts, seconds apart, one a burn to an inaccessible address and one a fresh mint. That structure admits only one sensible interpretation: an issuer-managed rebalancing of RLUSD liquidity between the XRP Ledger and Ethereum, with total supply preserved at every step. The open question is not what happened but why now, and Ripple has not published a statement disclosing the intended use of the Ethereum-side tokens. Until it does, each further supply shift between the two chains should be read as a live indicator of where RLUSD's next phase of adoption is being targeted — a signal worth monitoring as XRP holds its post-breakout structure and stablecoin rails become an increasingly competitive battleground.