XRP Ledger Prepares Token-Permission Fix After Validator Delay

The XRP Ledger is approaching a security-related protocol change designed to close an unusual gap between two powers that token issuers normally keep separate: the ability to destroy issued tokens and the authority to create them. As of November 2, an amendment known as fixCleanup3_4_0 was expected to become eligible for activation on November 4, subject to continued validator support and the network's approval process.

The distinction matters because the XRP Ledger supports assets issued by businesses and other organizations, including stablecoins. An issuer might authorize a payment processor to remove tokens from circulation after users redeem them for conventional money. That limited operational role should not automatically grant the processor permission to increase the outstanding supply.

According to CoinDesk's reporting and the network's technical guidance, a flaw could allow an account holding a token-destruction permission to create issued tokens under certain conditions. The planned change is intended to enforce the separation between those functions. It does not imply that someone has exploited the loophole, and it does not enable the creation of new native XRP.

Why minting and burning need separate authorization

Issued tokens are claims or digital representations whose properties depend on the entity responsible for them. For a stablecoin, the issuing organization may promise redemption under specified terms. A token's on-chain supply therefore needs to align with the issuer's authorized creation and redemption processes.

Burning typically removes units from circulation. Minting increases units in circulation. Allowing the same account to perform both operations may be appropriate in a tightly controlled system, but granting only the narrower permission is a common way to limit operational risk. A processor handling redemptions may need to destroy redeemed units without gaining a broad right to issue fresh units.

That does not mean all tokens issued on XRPL are automatically compromised. The exposure depends on how permissions were configured and which accounts were entrusted with particular functions. Issuers and infrastructure providers need to assess those configurations rather than assume the flaw affected every asset equally.

Network governance explains the delay

Protocol changes on XRPL are not activated simply because a development team announces them. Amendments need sustained backing from validators, the independent participants that help agree on the network's transaction history. The threshold is more than 80% support for two uninterrupted weeks.

CoinDesk reported support from 33 of 35 tracked trusted validators on November 2. With that denominator, at least 29 must continue backing the amendment for the clock to complete. A temporary decline to 26 validators on October 21 interrupted the previous approval period, delaying the expected activation from October 23 to early November. Support later recovered, but the required continuous approval period had to begin again.

The earliest reported activation window was around 14:46 UTC on November 4, provided support remained above the threshold and the network completed its activation checkpoint. That is a projected window, not confirmation the change has gone live. Coverage published before that moment should describe the fix as expected or pending.

Other changes are included in the amendment

The same package addresses calculations involving trading pools, vault deposits and withdrawals, and loan-related records. Some of these systems are components of broader lending functionality that has not yet received the validator support needed for its own launch. A correction in a software package should not be mistaken for activation of every associated financial product.

For stablecoin issuers, the near-term practical question is whether permission configurations should be changed before or after the protocol update. Users who simply hold XRP do not need to infer from this story that the native token's supply mechanism has changed. XRP's issuance structure is separate from the permissions used for assets created by third parties on its ledger.