by Jake ClaverThe XRP Ledger added AMMClawback, a feature that lets an issuer reclaim tokens they issued, even when those tokens are sitting inside an automated market maker pool. Paired with how Ripple has configured RLUSD’s issuer settings, it’s worth understanding what this actually enables and, just as importantly, what it doesn’t.
What AMMClawback does
Clawback isn’t new to XRPL. The ledger has long supported a clawback flag that lets an issuer reclaim tokens they created, provided they enabled that setting when the token was issued (see the XRPL clawback docs for the general mechanism). AMMClawback extends that same capability specifically into automated market maker pools, per the XRPL technical reference, closing a gap where tokens sitting in a liquidity pool were previously outside the issuer’s reach. You can track when this and related features went live on XRPL’s known amendments page.
Why RLUSD needs this
Ripple’s RLUSD implementation settings, documented in its public GitHub repository, show clawback enabled as part of the stablecoin’s compliance configuration. This is standard practice for regulated stablecoins, not unique to Ripple. Stablecoin issuers are generally required to be able to freeze or reclaim tokens in specific circumstances: responding to law enforcement requests, correcting an operational error, or handling sanctioned addresses. Without that capability, a stablecoin issuer can’t meet the compliance obligations regulators expect for fiat-backed tokens, and the issuer’s own bank relationships likely depend on being able to demonstrate that control exists.
What this doesn’t mean
Here’s where it’s worth being precise, because this feature gets misread often. Clawback and AMMClawback apply only to tokens the issuer created and explicitly enabled clawback for at issuance. It has no bearing on XRP itself. XRP is not an issued currency on XRPL, it’s the ledger’s native asset, and no clawback mechanism can reach XRP held in any account or pool. Conflating a compliance tool built for a specific stablecoin with some claim about centralized control over XRP is a common error, and it’s not supported by how the feature actually works.
The bigger picture
Features like this are why regulated stablecoin issuers can operate on XRPL in the first place. A stablecoin without a compliance backstop isn’t going to get approved by the banking partners or regulators an issuer like Ripple needs onside. AMMClawback closing the AMM-pool gap in that compliance toolkit is a small technical update with a straightforward, defensible purpose: keeping RLUSD viable as a regulated product, not extending issuer control over the ledger’s native asset.
Educational only, not tax, legal, or investment advice. Check primary sources and speak with a qualified professional before making financial decisions.
