TL;DR
XRP Ledger is approaching activation of fixCleanup3_4_0, which closes a flaw allowing PaymentBurn delegates to mint issued tokens without PaymentMint authority.
Validator support briefly fell below the threshold on October 21, resetting the 14-day countdown. The amendment now has 33 of 35 votes and is projected for November 4.
The issue affects issued fungible tokens, including stablecoins, but does not affect XRP’s supply or enable arbitrary accounts to mint assets.
XRP Ledger is approaching activation of a fix that closes a token-permission flaw affecting issued assets, including stablecoins , after validator support recovered from a reset in October. The official amendment documentation warns that delegated PaymentBurn permission can, under certain conditions, also allow new fungible tokens to be minted. The fix sits inside fixCleanup3_4_0 and strengthens the XRP Ledger ecosystem without changing XRP’s own supply. The problem affects delegated fungible-token operations rather than the ledger’s native asset.
Validator Reset Delays Fix for Delegated Token Minting
The issue concerns delegated permissions, not unrestricted token creation by arbitrary accounts . A stablecoin issuer could, for example, authorize a partner to burn tokens when customers redeem them for fiat. That partner should require a separate PaymentMint permission to create replacement tokens, but the current flaw can allow a PaymentBurn delegate to cross a zero balance and mint under specific circumstances. fixCleanup3_4_0 rejects that behavior unless the delegate also holds minting authority. This matters because PermissionDelegationV1_1 is already active on Mainnet.
Validator governance delayed the correction. fixCleanup3_4_0 lost its required supermajority on October 21 when support fell to 26 of 35 trusted validators , resetting the mandatory 14-day approval period. The XRPL Dashboard now shows 33 of 35 validators supporting the amendment, above the 29 votes required. The network currently projects activation for November 4 around 14:46 UTC if support remains uninterrupted, following the earlier validator-support reset . Another fall to 80% or less would restart the clock again.
The package extends beyond the minting-permission flaw. fixCleanup3_4_0 groups corrections for tokens, AMMs, permissioned trading, vaults, lending and escrow , including calculation and authorization fixes. Some of that code concerns features whose own amendments are not yet active. The distinction mirrors the network’s earlier preparation of bug fixes ahead of the lending launch : activating maintenance code does not automatically launch every feature it touches. That governance distinction remains operationally important today.
For stablecoin and token issuers, the immediate significance is tighter separation between authority to destroy tokens and authority to create them . Official documentation continues to recommend against delegating PaymentBurn until fixCleanup3_4_0 activates. The issue does not affect XRP issuance, and the amendment itself remains conditional until the voting window completes. The episode also reinforces why XRPL operators must track amendment readiness, a process highlighted during earlier node-upgrade warnings when approaching consensus could leave outdated servers amendment-blocked.
