The XRP Ledger, an open-source blockchain best known for powering the digital asset XRP, has successfully implemented a major security update aimed at closing a longstanding vulnerability in its token management system. The fixCleanup3_4_0 amendment became active on November 4 at 14:52 UTC, following nearly two weeks of validator voting and procedural delay.
Token creation vulnerability addressed
This upgrade addresses a critical loophole within XRPL’s permission delegation system. Previously, accounts granted PaymentBurn privileges—which are intended for token destruction—could, under specific circumstances, also create new tokens. This flaw impacted not only traditional trust-line assets but also Multi-Purpose Tokens, raising concerns particularly among stablecoin issuers and other entities overseeing tokenized financial products.
An example of this problem involved stablecoin operators who had delegated redemption rights. While the intention was for trusted partners to destroy tokens upon redemption, the vulnerability meant those same partners could potentially mint new tokens without explicit authorization—jeopardizing the intended separation of roles.
The applied amendment now ensures that PaymentBurn transactions cannot move from a zero token balance to a positive one unless the account holds specific minting rights. This tighter control significantly reduces risk for institutions managing large-scale assets through the XRPL network.
Under the revised protocol, PaymentBurn rights alone do not suffice to create tokens. Separate and explicit minting authorization is required, bolstering trust and stability for issuers of stablecoins and similar assets.
The vulnerability did not affect XRP’s native currency supply, according to developers, and there have been no public reports of exploitation prior to the fix.
Mini dictionary: PaymentBurn permission, a specialized XRPL account authorization that allows the destruction of tokens on behalf of another party, commonly used by issuers to regulate token supply in cooperation with service partners. It does not normally allow token creation.
Validator voting and governance process
The amendment’s activation was delayed from its anticipated October 23 date due to a brief decline in validator support. On October 21, the number of approving validators dropped below the required majority, forcing a restart of the 14-day approval period despite consensus being quickly restored.
For governance changes like protocol amendments, XRPL depends on more than 80% validator approval sustained for two full weeks. Out of a tracked group of 35 validators, at least 29 needed to affirm the proposal before it could become part of network rules.
| Requirement | Number |
|---|---|
| Total validators | 35 |
| Approvals needed | 29 |
| Approval period | 2 weeks |
Additional upgrades and continued development
Beyond tightening token issuance permissions, the fixCleanup3_4_0 amendment includes improvements to automated market maker clawbacks, escrow reserves, transaction signing processes, and Single Asset Vault accounting. These measures aim to enhance security and reliability for all network participants.
The update does not activate XRPL’s proposed native lending protocol, which remains under separate consideration. At the latest check, only 19 of the required 29 validator votes had been secured for that feature, leaving it short of the approval threshold.
Ongoing development efforts are focused on further strengthening asset security, including new authorization checks for institutional use cases. Developers indicate that prospective amendments will continue to be subject to rigorous governance procedures to maintain trust across the XRPL ecosystem.
The latest protocol change underscores XRPL’s reliance on decentralized validator voting, reinforcing that significant upgrades require broad and sustained consensus rather than unilateral decisions from entities like Ripple.
