Disclaimer: The opinions expressed by our writers are their own and do not represent the views of U.Today. The financial and market information provided on U.Today is intended for informational purposes only. U.Today is not liable for any financial losses incurred while trading cryptocurrencies. Conduct your own research by contacting financial experts before making any investment decisions. We believe that all content is accurate as of the date of publication, but certain offers mentioned may no longer be available.
The XRP Ledger eyes crucial fixes and improvements over the next few days. According to XRPScan data, fixCleanup3_4_0 began its two-week activation window on October 5, 2026, with the earliest activation date being 9:34 AM UTC on October 23, 2026.
Validator support for the fixCleanup3_4_0 amendment must stay above 80% for it to launch. If it slips to 80% or lower even once, the amendment is rejected and the 14-day timer starts over.
This fixCleanup3_4_0 amendment is a collection of fixes for Single Asset Vaults, the Lending Protocol, Automated Market Makers, the permissioned DEX, trust lines, NFTs, MPTs, Escrow, Sponsorship, transaction signing, and permission delegation.
HOT Stories
You Might Also Like
FixCleanup3_4_0, which bundles amendment-gated fixes, was shipped in Version 3.4.0 of xrpld, the reference server implementation of the XRP Ledger protocol, and entered voting on September 17, 2026. The amendment has 81.25% consensus, with 26 out of 32 validators having voted for it.
The Permission Delegation and Batch amendments went live as a key milestone in the past week. The fixCleanup3_4_0 amendment is essential for Permission Delegation, as until it is enabled, users would not be able to delegate the PaymentBurn granular permission. Before the fix, a delegate with the PaymentBurn granular permission could also mint new fungible tokens (trust line tokens or MPTs) in certain circumstances. Other granular permissions are unaffected.
Wide-ranging protocol fixes anticipated
This fixCleanup3_4_0 amendment is a collection of fixes: it excludes deleted domain offers from the Permissioned DEX invariant, so replacing an offer in one domain with an offer in another no longer triggers a violation.
You Might Also Like
The fix prevents 'AMMClawback' from silently recovering zero when integer MPT rounding floors the amount, instead of burning the holder's LP tokens for nothing, and allows AMMClawback to bypass the owner-reserve check when it must auto-create the paired asset holding, so a compliance clawback is not blocked or vetoed by reserve requirements.
The fix rejects fake-XRP NFT offer amounts, exempts an IOU issuer from their own global freeze when creating an NFToken offer denominated in their own currency, and tightens permissioned DEX domain checks. It also recycles the escrow owner reserve in EscrowCancel and EscrowFinish, so returning IOUs to an owner at the reserve boundary no longer fails. It adds precision and rounding fixes across VaultDeposit, VaultWithdraw, and VaultClawback, so a vault's tracked total assets, available assets, and share supply stay consistent.
The fix refines freeze, authorization, credential, and destination handling for Single Asset Vaults and the Lending Protocol; for example, exempting loan defaults from asset freeze, refusing pseudo-accounts where they cannot participate, and validating permissioned-domain withdrawal destinations and rejecting 'PaymentBurn' payments that cross a zero balance.