See more like this on Google
Share article
Share article
The RLUSD printer has a reverse gear, and Ripple is using it. Earlier today, roughly 40 million RLUSD was sent to burn addresses on Ethereum$1,768.88 in under an hour, right as the market was asking an awkward but fair question: why so much supply management, and why so little explanation? [1]
Enjoy articles without ads?
Register for free and get unlimited access to all articles.
Ripple retires nearly 40 million RLUSD
Blockchain tracking flagged a total burn of 39,998,800 Ripple USD$1.00 on Thursday, April 2, split across three Ethereum transactions. The biggest leg removed 20 million RLUSD, followed by two smaller burns of 9,999,000 and 9,999,800. [2]
Those tokens were sent to null addresses, which means they are effectively gone for good. One wrinkle caught traders' attention: the first burn was followed almost immediately by a small mint. That does not automatically signal stress, but it does reinforce the view that Ripple is actively tuning Ripple USD$1.00 supply rather than letting issuance sit static. [3]
This matters because stablecoin flows are usually read as a signal, not just an accounting event. When a stablecoin issuer mints, traders often assume demand is incoming. When it burns, the market starts asking whether redemptions are rising, liquidity is being rebalanced, or inventory was simply overissued and is now being cleaned up.
Why the burn is drawing scrutiny
The timing is doing most of the work here. Hours before the latest burn, a developer on X publicly urged Ripple CEO Brad Garlinghouse to clarify the purpose of recurring RLUSD burns. The argument was straightforward: if Ripple says nothing, the rumour mill will do the talking instead.
That criticism has found an audience because this was not a one-off oddity. RLUSD has seen repeated burn activity in recent weeks, including prior removals on Ethereum and larger supply adjustments reported across Ripple-linked channels. Research circulating today also points to previous episodes involving tens of millions, and in some cases far more, being retired in short order. [4] [5]
None of that proves demand is falling. It could just as easily reflect treasury operations, cross-chain balancing, or institutional settlement flows being netted out after issuance. But absent a detailed issuer breakdown, the market is left inferring intent from wallet movements, which is never the cleanest way to price risk. [6]
What the chain data suggests, and what it does not
The confirmed facts are limited but useful. The burns happened on Ethereum, not as an abstract ledger note. They were executed in quick succession, which suggests planned treasury management rather than a random retail-driven redemption wave. The near-immediate mint after the first burn also hints at operational reshuffling instead of a simple one-way contraction.
What is missing is the part traders actually want: wallet attribution beyond the obvious issuer linkage, redemption context, and whether the burned RLUSD corresponded to client outflows, internal reserve handling, or a venue-specific liquidity adjustment. Without that, it is hard to map the event onto broader demand for RLUSD with much precision.
That is the bit worth underlining. A burn is not inherently bearish for a stablecoin. It can mean redemptions are working as designed. It can also mean supply is being tightened to keep circulation aligned with reserves. The problem is not the mechanism. The problem is opacity.
What to watch next
- Whether Ripple or Brad Garlinghouse gives a direct explanation for recurring RLUSD burns
- Fresh mint activity on Ethereum or XRPL that would suggest routine rebalancing
- Exchange and custodian wallet flows tied to RLUSD issuance and redemption
- Any change in burn frequency, especially if large batches continue without comment
- Secondary market liquidity for RLUSD, because thin liquidity turns treasury moves into narrative fuel fast
