The XRP Ledger is moving toward significant protocol improvements, as the fixCleanup3_4_0 amendment advances through its approval process. Data from XRPScan indicates that the amendment’s two
The XRP Ledger is moving toward significant protocol improvements, as the fixCleanup3_4_0 amendment advances through its approval process. Data from XRPScan indicates that the amendment’s two-week activation window started on October 5, 2026. The earliest possible activation is scheduled for 9:34 AM UTC on October 23, 2026, provided it maintains the required validator support.
For the fixCleanup3_4_0 amendment to become active, validator support must stay above 80% continuously during the voting period. If support falls to 80% or below at any point, the proposed changes are rejected, triggering a fresh 14-day voting cycle. As of now, consensus stands at 81.25%, with 26 out of 32 validators in favor, according to the latest figures.
The fixCleanup3_4_0 package includes multiple protocol enhancements and has been distributed as part of Version 3.4.0 of xrpld, the reference server implementation for the XRP Ledger. Voting for this amendment began on September 17, 2026.
Mini dictionary: xrpld, a reference implementation of the XRP Ledger protocol, serves as the backbone for nodes participating in the XRP Ledger, supporting transaction processing and amendment deployment.
The update brings targeted fixes across several XRP Ledger features, such as Single Asset Vaults, the Lending Protocol, Automated Market Makers (AMMs), the permissioned decentralized exchange (DEX), trust lines, non-fungible tokens (NFTs), MPTs, escrow, and permission handling for transactions and sponsorships.
Recent milestones include the activation of both the Permission Delegation and Batch amendments. Permission Delegation enables one account to delegate specific transaction permissions to another, enhancing access control mechanisms. However, full functional deployment relies on fixCleanup3_4_0 becoming active. Until then, users are unable to delegate the PaymentBurn granular permission. There have been cases where, without this fix, delegates with PaymentBurn permission could mint new fungible tokens under specific circumstances, which this update aims to correct.
In its current form, fixCleanup3_4_0 ensures a delegate with PaymentBurn permission cannot mint new tokens in scenarios where this was previously possible, maintaining proper separation of permissions and enhancing system security.
Among its technical corrections, fixCleanup3_4_0 removes deleted domain offers from the Permissioned DEX invariant, enabling seamless replacements across domains without triggering violations. The amendment also prevents the ‘AMMClawback’ functionality from returning zero when integer rounding reduces an MPT amount to nothing, and permits this function to bypass the owner-reserve check when creating a paired asset holding, facilitating compliance-sensitive clawbacks.
Feature Previous Behavior Post-Amendment Behavior Permissioned DEX domain offers Replacing offers between domains could cause violations Offer replacement does not trigger invariant violation AMMClawback with zero value Possible silent return with LP token burn No tokens burned when result is zero PaymentBurn permission Delegates could mint tokens under certain conditions Strict separation, token mint blockedThe amendment also addresses NFT offer validity, exempts issuers from their own global freeze rule when making NFToken offers in their currency, and enforces stricter permissioned DEX domain checks. For escrow-related transactions, it recycles the owner reserve for EscrowCancel and EscrowFinish, ensuring IOUs are returned efficiently at reserve limits. Additionally, it includes precision and rounding corrections for vault operations, keeping asset totals and share supply accurate and consistent.
For Single Asset Vaults and the Lending Protocol, fixCleanup3_4_0 enhances how the protocol manages freeze status, authorization, credentials, and destination restrictions. The update exempts loan defaults from asset freezes, blocks unauthorized pseudo-accounts, validates withdrawal destinations in permissioned domains, and rejects PaymentBurn transactions that attempt to process zero balances. These refinements are designed to improve compliance and ensure consistent transaction outcomes across the affected features.
FixCleanup3_4_0 introduces precision to asset handling and permission logic, supporting both institutional and individual users with improved security and reliability throughout the XRP Ledger network.
The post XRP Ledger amendment fixCleanup3_4_0 nears activation with 81.25% validator support appeared first on COINTURK NEWS.
