Key Highlights:
- The XRP Ledger is scheduled to activate the fixCleanup3_4_0 amendment on Wednesday to patch a token creation permission vulnerability.
- The loophole allowed accounts granted only token-burning rights to improperly mint issued assets, including stablecoins, under certain circumstances.
- The patch has secured backing from 33 of 35 trusted validators, surpassing the mandatory 80% consensus threshold required over a two-week period.
The XRP Ledger is poised to activate a critical protocol correction on Wednesday, resolving a permission loophole that under specific conditions permitted accounts authorized strictly to destroy issued tokens to mint new ones instead. The upcoming deployment follows a temporary drop in validator consensus that previously delayed the fix’s activation schedule by nearly two weeks.
Understanding the fixCleanup3_4_0 Amendment
The technical issue centers on asset permission configurations managed by token issuers on the XRP Ledger. Under the existing framework, an account granted authorization exclusively to burn tokens could bypass intended boundaries and generate unauthorized supply. For instance, a stablecoin issuer might grant a partner payments firm permission to burn tokens when end users redeem them for fiat currency. While that entity should logically require independent, explicitly granted authorization to mint new tokens, the existing logic flaw failed to enforce that operational boundary.
The upcoming network correction, designated as fixCleanup3_4_0, establishes strict enforcement of these asset permissions. Network documentation had previously advised developers and asset issuers against utilizing the token-burning authorization feature until the patch could formally take effect across the network. The vulnerability applies strictly to third-party tokens and stablecoins issued on the ledger; the native supply of XRP itself remains completely unaffected by the bug.
Consensus Thresholds and Network Activation
On the XRP Ledger, protocol amendments require rigorous testing and consensus from independent validators—the distributed node operators responsible for validating transaction integrity and maintaining network state. In order for an amendment to pass and become permanently active on-chain, it must sustain an agreement threshold exceeding 80% among trusted validators for an unbroken duration of two consecutive weeks.
Ripple’s RLUSD Surpasses PayPal’s PYUSD to Become the Seventh-Largest Stablecoin
Data tracked by the XRPL Dashboard indicates that 33 of the 35 tracked trusted validators currently back the fixCleanup3_4_0 upgrade. Meeting the 80% supermajority required at least 29 of the 35 tracked validators to consistently signal their approval. Having maintained this required consensus after recovering from an earlier, brief dip in validator support, the network is set to execute the rule change on Wednesday.
Why This Matters
Tokenization and stablecoin issuance represent significant utility sectors on the XRP Ledger. Institutional issuers, payments providers, and financial applications depend on immutable, distinct controls between minting and burning mechanisms to maintain total supply integrity and regulatory compliance. By resolving this permission discrepancy, the XRP Ledger eliminates an operational risk factor for stablecoin operators, strengthening smart permission logic and reinforcing developer trust in the ledger’s issued asset infrastructure.
Frequently Asked Questions
Does this loophole impact the total supply or security of native XRP?
No. The vulnerability is entirely restricted to custom issued assets on the ledger, such as stablecoins and third-party tokens. The native supply, security, and mechanics of XRP are completely unaffected.
What does the fixCleanup3_4_0 update change for token issuers?
The amendment strictly enforces the operational boundary between burning and minting permissions. Once activated, any secondary entity or partner authorized only to destroy tokens during redemptions will be technically prevented from minting new supply without distinct, authorized permissions.
Why was the activation of the fix previously delayed?
Network rule amendments on the XRP Ledger require uninterrupted support from over 80% of trusted validators for a continuous two-week window. A temporary drop in validator support previously interrupted that countdown, requiring the consensus clock to reset and extending the timeline by nearly two weeks.
