BTC $77,095 
ETH $2,283 
MGLOEURO $111,813 
USDT $0.9987 
BNB $695.44 
XRP $1.28 
USDC $0.9994 
SOL $93.09 
TRX $0.3223 
FIGR_HELOC $1.04 Altcoins · Explained
XRP Ledger sets Nov. 4 target for token-minting fix
The fixCleanup3_4_0 amendment is set to close a PaymentBurn permission flaw, provided validator support holds through the waiting period.
Key takeaways
- Burn-only loophole. A delegate with PaymentBurn permission can sometimes mint trust line tokens or MPTs until fixCleanup3_4_0 is active.
- Conditional date. The amendment is projected for Nov. 4 at about 14:46 UTC, with 33 of 35 trusted validators backing it and support required to stay above 80%.
- Issuer guidance. Issuers are advised not to delegate PaymentBurn until activation; existing permissions can be updated or revoked.
What happened
The XRP Ledger is moving toward activation of fixCleanup3_4_0, an amendment expected to take effect around 14:46 UTC on Nov. 4 and close a flaw in a recently added permission system. The issue involves PaymentBurn, a delegated permission meant to let one account destroy fungible tokens for an issuer.
XRPL documentation cited by Crypto.news and Bitcoin.com News says a delegate holding PaymentBurn can sometimes create trust line tokens or Multi-Purpose Tokens (MPTs) before the amendment is enabled. The warning covers issued assets, including stablecoins, and does not affect XRP's native supply. Other granular permissions are unaffected.
Until activation, developers recommend that issuers avoid delegating PaymentBurn. The correction ships in xrpld version 3.4.0, but inclusion in server software does not by itself activate an amendment. Validator backing stands at 33 of 35 tracked trusted validators, according to the reports.
First $1.52Latest $1.29-15.1% over the period
Points are daily observations, not closing prices.
Why it matters
Permission delegation lets an issuer give another account limited powers without sharing full control. If a burn-only delegate can sometimes mint tokens, the line between destroying and creating assets becomes less reliable for issuers that rely on delegated roles. Issuers, exchanges and businesses that delegate permissions are the relevant audience; ordinary XRP holders are not affected because the flaw concerns issued tokens.
The guidance is temporary. Bitcoin.com News reported that PaymentBurn should be safe to delegate again once fixCleanup3_4_0 activates. Neither the warning nor the release notes identified an issuer whose tokens were fraudulently created.
What the data shows
The XRPLWin tracker cited by Crypto.news recorded 33 of 35 trusted validators backing fixCleanup3_4_0, or 94.29%. Crypto.news said 29 supporting votes were needed to clear the threshold, while Bitcoin.com News put the requirement at 28; both reported the same 33-of-35 support level. Amendments need at least 80% support from trusted validators for two consecutive weeks, and a drop to 80% or lower resets the countdown.
The timetable has slipped before. Crypto.news reported an initial majority from Oct. 9 to Oct. 21, when the amendment lost the backing needed to continue its countdown, followed by a new majority that began on Oct. 21. Bitcoin.com News noted that an earlier target of Oct. 23 at about 09:34 UTC came and went. The tracker lists Nov. 4 as a conditional activation time, not a completed upgrade.
Background
Permission delegation went live on Oct. 8 through the PermissionDelegationV1_1 amendment, Bitcoin.com News reported. XRPL lists PaymentMint and PaymentBurn as separate functions: PaymentMint authorizes payments that create fungible tokens, while PaymentBurn is meant to authorize destruction without letting a payment cross a zero balance. The Sep. 16 release notes for xrpld 3.4.0 say payments using PaymentBurn will be rejected if they cross that boundary.
Accounts grant delegated powers through a DelegateSet transaction and can later change or revoke them with another transaction of the same type, according to XRPL's delegation guide. A delegate can receive up to 10 permissions, and certain powers, particularly those involving cryptographic keys or granting further permissions, cannot be delegated. The guide also says granular permissions are predefined and cannot be customized for selected currencies.
The package also repairs vault rounding, trading-pool clawbacks that round to zero, and loan checks that require the due date to have strictly passed, Bitcoin.com News reported; it tightens escrow reserves and signature handling as well.
What is still unclear
The reports do not name any issuer whose tokens were fraudulently created, and they do not state whether the PaymentBurn permission was misused before the fix. The warning is framed as a precaution for accounts that received the affected delegated permission.
What to watch
The key variable is validator support. If backing stays above 80% through the waiting period, fixCleanup3_4_0 is projected to activate on Nov. 4 at about 14:46 UTC; a decline to 80% or lower would interrupt the countdown again. Issuers that already delegated PaymentBurn can update or revoke the permission through DelegateSet.
Other lending amendments remain below the support line, with Bitcoin.com News reporting LendingProtocolV1_1 and LendingProtocol at 19 votes each and SingleAssetVault at 21, below the 28-vote threshold cited in that report. None had a countdown running.
Questions readers ask
What does fixCleanup3_4_0 change?
It closes a PaymentBurn permission flaw that can let a delegate sometimes mint trust line tokens or MPTs, and it bundles other repairs to vaults, trading pools and loan checks.
Does the flaw affect XRP itself?
No. The reports say it concerns issued tokens such as trust line tokens and MPTs, not XRP's native supply.
What should issuers do before activation?
XRPL guidance recommends not delegating PaymentBurn until the amendment is active. Existing delegates can be changed or revoked through DelegateSet.
