Server racks representing XRP Ledger validator infrastructure

XRP Ledger’s Token-Permission Fix Nears Activation With Validator Support Restored

• November 2, 2026 3:06 pm • Comments

The XRP Ledger is approaching an important cleanup upgrade that would close a token-permission loophole before the network’s stablecoin and lending ambitions expand any further.

The change is part of an amendment package called fixCleanup3_4_0. If validator support holds, the package is expected to become eligible for activation on November 4.

That timetable matters because one of the fixes separates two powers that should never have been treated as interchangeable: permission to destroy an issued token and permission to create more of it.

What the XRP Ledger fix actually changes

CoinDesk found that an account authorized to burn an issuer’s tokens could, under certain conditions, also create new units without receiving separate minting authority.

The issue concerns fungible tokens issued on the XRP Ledger, including stablecoins and other tokenized assets. XRP’s fixed ledger supply is outside this particular permission path.

A stablecoin issuer might allow a payment partner to burn tokens when customers redeem them for dollars. Separate minting authority should still be required before that partner can issue replacement units.

The amendment enforces that boundary. CoinDesk also found no public report that the loophole had been exploited, and the network’s current developer guidance warns against granting the affected burn permission until the correction takes effect.

The timing remains conditional. Validator support must stay above the network threshold through the full voting window, and the actual switch follows a consensus checkpoint rather than a calendar promise.

The network’s official amendment documentation describes a broader cleanup package. It tightens calculations involving automated market makers, vault deposits and withdrawals, clawbacks, and lending-related accounting.

The package also corrects edge cases in token balances, escrow behavior, transaction signing, and permissioned trading. One lending fix prevents a loan from being marked late or in default before its contractual due date.

Those corrections will not launch XRP Ledger lending by themselves. The separate lending and single-asset vault amendments still need enough validator support to begin their own uninterrupted voting periods.

That sequencing is useful. Cleanup rules can be activated before the products that depend on them, giving validators and builders a tighter accounting foundation before more capital moves through native vaults and credit markets.

Validator support is back above the line

At the time of the latest report, 33 of 35 validators tracked by the XRP Ledger dashboard supported the amendment. The network requires more than 80% support for two uninterrupted weeks before a rules change can activate.

Support briefly fell to 26 validators on October 21. It recovered roughly two hours later, but the interruption restarted the clock and pushed the expected activation window back from October 23 to November 4.

XRPL contributor Vet documented the reset and the added validator votes that restored the margin:

The two-week rule can look slow when a fix is ready and nearly every tracked validator supports it. The delay is also the point of amendment governance.

New consensus rules do not go live after a momentary vote. The support has to remain durable.

Separate the cleanup amendment from the earlier slowdown

The amendment vote has unfolded alongside a separate operational issue that caused occasional slower ledger closes. Those events are related only by timing, not by cause.

XRP Ledger Operations said the slower closes stopped after operators applied a recommended configuration change. The team also said it was continuing work on a software release to address the behavior:

The cleanup amendment is a planned rules package. The slower-close incident was an operational problem mitigated through configuration while a separate software correction was prepared.

Why XRP holders should care

XRP’s supply was not at risk in this permission issue. The larger point is that token issuance rules have to be exact if the ledger is going to support more stablecoins, tokenized assets, vaults, and native lending products.

Small permission mistakes become large financial risks once real issuers and payment companies depend on them. Closing the burn-versus-mint loophole before those products scale is the right order of operations.

The next checkpoint is straightforward: validator support must stay above the required threshold through the activation window. If it does, the XRP Ledger will add a useful layer of separation between token destruction and token creation—and remove one more avoidable risk from its expanding financial stack.

Join the conversation!

We have no tolerance for comments containing violence, racism, profanity, vulgarity, doxing, or discourteous behavior. If a comment is spam, instead of replying to it please click the icon below and to the right of that comment. Thank you for partnering with us to maintain fruitful conversation.