XRP Ledger activates fix for token-minting permission flaw
XRPL activated fixCleanup3_4_0 on Nov. 4, closing a delegated burn-permission flaw that could mint issued tokens. XRP was unaffected, with no exploit confirmed.
The Splyt Genesis Desk

The XRP Ledger activated fixCleanup3_4_0 on Nov. 4 at ledger 108,112,129, closing a flaw that could let accounts authorized to burn tokens create new ones. CoinDesk reported the activation, and XRPL’s amendment documentation describes the permission risk.
The flaw involved PaymentBurn, a permission that lets an account destroy tokens for an issuer. The bug affected issued assets, including stablecoins, not XRP itself. CoinDesk reported no publicly confirmed cases of exploitation.
How could a burn permission create tokens?
XRPL lets an account delegate specific actions to another account. For example, a stablecoin issuer might let a payment processor destroy tokens when customers redeem them, without authorizing it to issue more.
Before the fix, a delegate with PaymentBurn permission could, in certain circumstances, cross a zero balance and mint fungible tokens. XRPL’s documentation says this could affect trust-line tokens or multi-purpose tokens. The new rule rejects a delegated PaymentBurn payment that would cross zero unless the delegate also has PaymentMint permission.
That closes the gap between the action an issuer intended to delegate and what the delegate could do. XRPL’s documentation had advised developers not to delegate PaymentBurn until the fix was enabled.
What changed when the fix went live?
The correction is part of fixCleanup3_4_0, a wider package of ledger changes. The amendment also covers vault and lending calculations, automated market makers, NFTs, escrow, transaction signing and other functions, according to the XRPL amendment page.
Activation followed the XRP Ledger’s validator voting process. CoinDesk reported that the amendment needed support from more than 80% of trusted validators for 14 consecutive days. A drop in support during an earlier attempt restarted that clock; the fix eventually went live Wednesday, Nov. 4.
The bug concerned issued tokens, not the ledger’s native XRP supply. No public exploitation has been confirmed, so the disclosure does not establish that anyone created tokens through the flaw.
What should issuers watch next?
Issuers and developers should check that delegated permissions match the intended task, especially where a service can burn tokens. The next signal to watch is whether XRPL or affected issuers report any evidence that the flaw was exploited; so far, none has been publicly confirmed.
Source material
- amendment documentation — xrpl.org