XRP Ledger 3.1.3 upgrade to activate on May 27; FixCleanup3_1_3 enters two-week activation period

icon币界网
Share
Share IconShare IconShare IconShare IconShare IconShare IconCopy
AI summary iconSummary

expand icon
The XRP Ledger (XRPL) 3.1.3 blockchain upgrade, featuring the fixCleanup3_1_3 amendment, is scheduled to activate on May 27, 2026. The network upgrade is currently in its two-week activation period. Validators must update to version 3.1.3 to avoid transaction issues. The amendment removes expired NFTokenOffer entries, enforces trust line token limits for VaultWithdraw, and corrects loan accounting errors.
CoinDesk reports:

According to data from XRPScan, the fixCleanup3_1_3 amendment will take effect in a few days, with a current countdown of 9 days and 16 hours.

"fixCleanup3_1_3" represents the amendment to fix XRPL 3.1.3, which is currently in a two-week activation period, with an expected release date of May 27, 2026.

On May 8, XRP Ledger Foundation announced the release of the latest version of the XRP Ledger software, XRPL 3.1.3, which includes a fix amendment enabled by default. This amendment requires no manual voting—only an upgrade is needed.

The fixCleanup3_1_3 patch included in XRPL version 3.1.3 is a set of fixes for NFTs, authorized domains, vaults, and lending protocols.

Due to the amendment fix in XRPL 3.1.3 entering a two-week activation period, we urge XRP Ledger validators to update their XRP Ledger nodes to version 3.1.3 to prevent amendment blocking and user service disruptions.

XRP Ledger multiple feature updates: What are the changes?

As previously mentioned, the fixCleanup3_1_3 update resolves issues related to NFTs, licensed domains, vaults, and lending protocols. This fix addresses the issue of expired NFTokenOffer entries remaining on the ledger.

After enabling this change, using the NFTokenAcceptOffer transaction on an expired NFTokenOffer will now delete it during transaction processing.

The amendment adds an immutability check to ensure that the authorized domain is not modified due to transaction failure, and also fixes a missing trustline token limit check when withdrawing treasury assets.

After enabling this amendment, VaultWithdraw transactions that specify vault shares or vault assets will adhere to the trust line token limits of the destination address.

This amendment fixes the issue where loan accounting information was not updated in its associated Loan, LoanBroker, and Vault entries, regardless of whether the loan was defaulted, impaired, or unimpaired. Additionally, it resolves the LoanPay error that occurred when attempting to make an overpayment on a loan that does not permit overpayments.

This amendment adds an additional check for the "loan broker" invariant to ensure that the listed "available funds" exactly match the assets held in the associated pseudo-account.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.