An XRP Ledger amendment called fixCleanup3_4_0 is on course to activate on or about 4 November 2026, closing a loophole in the network’s new delegation feature that could let one account mint tokens it was never meant to create. Live ledger data on livenet.xrpl.org shows the change carrying the support of 33 trusted validators, about 94.29% of the tracked set, comfortably above the 80% supermajority the XRP Ledger requires. Under the network’s rules an amendment that holds a supermajority for two weeks becomes enabled automatically, with no company flipping a switch.
In brief
- fixCleanup3_4_0 bundles dozens of fixes across vaults, lending, automated market makers, trust lines, NFTs, escrow and transaction signing.
- Its most consequential change stops an account holding only the burn permission from minting new fungible tokens.
- On-chain voting put support near 94%, above the 80% threshold, with activation projected around 4 November 2026.
What fixCleanup3_4_0 actually changes
The amendment is housekeeping rather than a new feature. The XRP Ledger documentation describes it as “a collection of fixes for Single Asset Vaults, the Lending Protocol, Automated Market Makers, the permissioned DEX, trust lines, NFTs, MPTs, Escrow, Sponsorship, transaction signing, and permission delegation”. In practice that is more than two dozen distinct changes rolled into one vote, each tightening an edge case that current code handles loosely.
Several are small but telling. Creating a trust line that already exists will return a “tecDUPLICATE” result as a no-op, rather than doing unexpected work. The “asfDisallowIncomingTrustline” flag, which lets an account refuse unwanted trust lines, is extended to also block incoming offers. Vault deposits, withdrawals and clawbacks are made to round more precisely “so vault assets can’t over- or under-deliver”. And transaction signing gains distinct prefixes for sponsor and counterparty signatures, so a signature “can no longer be moved from one role to another” — a quiet but real hardening for the ledger’s sponsorship feature.
The minting loophole in permission delegation
The headline change concerns delegation. The XRP Ledger’s permission-delegation feature, which went live last month alongside a Solana upgrade, lets an account hand specific, granular permissions to another account. One of those permissions, “PaymentBurn”, is meant only to let a delegate burn tokens.
The documentation is blunt about the gap. Until this fix is enabled, it says, “a delegate with the PaymentBurn granular permission can also mint new fungible tokens (trust line tokens or MPTs) in certain circumstances”, and it recommends not delegating that permission in the meantime. fixCleanup3_4_0 “changes PaymentBurn-only delegated payments to reject an amount that would cross a zero balance into a mint, unless the delegate also holds PaymentMint”. In plain terms, a burn-only delegate will no longer be able to tip a balance past zero and quietly conjure new units of a token. There is no suggestion in the docs that the flaw was ever exploited on the live network; the guidance has been precautionary.
How close the XRP Ledger amendment is to going live
On the XRP Ledger, protocol changes are not pushed by a central operator. They are voted on by validators, and an amendment that keeps at least 80% support for two straight weeks activates on its own. The on-chain voting page lists fixCleanup3_4_0 at 94.29% consensus, with 33 of the tracked validators in favour against a 28-of-35 threshold, and it is not yet enabled. The projected activation date shown on-chain is 4 November 2026. Because support sits well clear of the line, the main risk to that timetable would be validators dropping their backing before the window closes.
Why a tidy-up amendment matters more than it sounds
It is tempting to wave away a “cleanup” release, but the XRP Ledger amendment lands on a chain that increasingly carries real money. Institutions have begun parking regulated products on it — a tokenised sterling fund put £50m onto the XRP Ledger earlier this year — and wallet and payments firms have built directly on it for consumer and AI-agent use. On a network like that, a path that lets a delegate mint tokens it should only be able to burn is exactly the sort of quiet accounting flaw that erodes trust in a token’s supply, even if nobody has abused it.
The episode also shows the XRP Ledger’s pattern: ship a feature, then harden it. Permission delegation itself arrived only after an earlier version was disabled over a bug, and this amendment now cleans up the replacement. That iterative, validator-governed model is slower than a company issuing a patch, but it means no single party can force a change — or, in this case, quietly leave a hole open. The honest caveat is that this is a projection, not a done deal: the fix is not enabled until the two-week clock runs out and validators hold the line.
For now, the thing to watch is simple: whether fixCleanup3_4_0 keeps its supermajority through the activation window, and whether anyone delegating the burn permission heeds the documentation’s advice until it does.
Sources
Related stories
- Two Blockchain Upgrades: XRP Ledger Delegation and Solana’s 200ms Blocks Go Live
- Aviva Investors Puts £50m Into Tokenised Sterling Fund on XRP Ledger
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X
