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.
According to data from XRPScan, the fixCleanup3_1_3 amendment is set to activate in a few days, with the current countdown being 9 days 16 hours.
"fixCleanup3_1_3" represents the fix amendment in XRPL 3.1.3, which is now in a 2-week activation period with an expected timeline of May 27, 2026.
On May 8, the XRP Ledger Foundation announced the release of the latest XRP Ledger software, XRPL 3.1.3, which included one default-yes fix amendment. This needed no manual voting, with upgrading alone being enough.
The fixCleanup3_1_3 amendment included in the XRPL version 3.1.3 is a collection of fixes for NFTs, Permissioned Domains, Vaults, and the Lending Protocol.
As the fix amendment in XRPL 3.1.3 enters a 2-week activation period, XRP Ledger validators are urged to update their XRP Ledger nodes to 3.1.3 to prevent amendment blocking and service interruption for users.
XRP Ledger multi-feature amendment: What's in it?
As stated, the fixCleanup3_1_3 amendment includes fixes for NFTs, Permissioned Domains, Vaults, and the Lending Protocol. This fixes an issue with expired NFTokenOffer entries remaining on the ledger.
With the amendment enabled, using the NFTokenAcceptOffer transaction on an expired NFTokenOffer now deletes it as part of transaction processing.
The amendment adds an invariant check to ensure Permissioned Domains are not modified by failed transactions and also fixes a trust line token limit check that was skipped when withdrawing vault assets.
With the amendment enabled, VaultWithdraw transactions that specify either vault shares or vault assets will respect the trust line token limit of the destination address.
The amendment fixes loan accounting information not updating in its associated Loan, LoanBroker, and Vault entries if the loan was defaulted, impaired, or unimpaired. It also changes a LoanPay error when attempting to overpay on a loan that doesn't permit overpayments.
The amendment adds an additional check for 'LoanBroker' invariants to ensure the listed 'CoverAvailable' exactly matches the assets held in the associated pseudo-account.
Dan Burgin
