The fixCleanup3_1_3 amendment for the XRP Ledger (XRPL) version 3.1.3 is on the cusp of activation, with its current countdown indicating approximately 9 days and 16 hours remaining until its anticipated activation date of May 27, 2026. This amendment is a critical 'default-yes' fix, meaning it required no manual voting process, and updating alone is sufficient for its implementation. The XRP Ledger Foundation officially released the latest XRPL software, version 3.1.3, on May 8, which included this essential amendment.

The fixCleanup3_1_3 amendment is a comprehensive package designed to address various issues across multiple core features of the XRPL. It specifically targets improvements and fixes related to Non-Fungible Tokens (NFTs), Permissioned Domains, Vaults, and the Lending Protocol. As this significant fix amendment enters its two-week activation period, XRP Ledger validators are strongly advised to update their nodes to XRPL 3.1.3. This proactive measure is crucial to prevent potential amendment blocking, ensure network stability, and avoid service interruptions for users.

One key aspect of the fixCleanup3_1_3 amendment is its resolution of an issue concerning NFTs. Specifically, it fixes the problem of expired NFTokenOffer entries that would persistently remain on the ledger. With the amendment fully enabled, any subsequent use of the NFTokenAcceptOffer transaction on an expired NFTokenOffer will now correctly trigger its deletion as part of the transaction processing, ensuring a cleaner and more efficient ledger.

Furthermore, the amendment introduces important enhancements for Permissioned Domains and Vaults. It adds an invariant check designed to ensure that Permissioned Domains are not inadvertently modified by failed transactions, thereby maintaining their integrity. For Vaults, the amendment rectifies a previously skipped trust line token limit check that occurred when withdrawing vault assets. Once enabled, VaultWithdraw transactions, whether specifying vault shares or vault assets, will accurately respect and adhere to the trust line token limit of the destination address, preventing potential over-withdrawal issues.

The Lending Protocol also receives significant attention through this amendment. It specifically fixes problems where loan accounting information failed to update correctly in associated Loan, LoanBroker, and Vault entries when a loan was defaulted, impaired, or unimpaired. Additionally, the amendment corrects a LoanPay error that would occur when attempting to overpay on a loan that explicitly does not permit overpayments. To further bolster the integrity of the Lending Protocol, an additional check for 'LoanBroker' invariants has been implemented, ensuring that the listed 'CoverAvailable' precisely matches the assets held within the associated pseudo-account, enhancing transparency and reliability.