XRP Ledger Activates fixCleanup3_1_3 Upgrade on May 27

iconCryptoBriefing
Share
Share IconShare IconShare IconShare IconShare IconShare IconCopy
AI summary iconSummary

expand icon
On-chain news: The XRP Ledger activated the fixCleanup3_1_3 amendment on May 27, delivering bug fixes for NFTs, vaults, lending, and permissioned domains. Included in rippled version 3.1.3, the blockchain upgrade adds automatic removal of expired NFT offers and an invariant check for Permissioned Domains. As of mid-May, 40-46% of nodes had upgraded, with unupgraded nodes unable to process transactions post-activation.

The XRP Ledger is activating its fixCleanup3_1_3 amendment on May 27, bringing a bundle of bug fixes that touch NFTs, vaults, lending, and permissioned domains.

The amendment arrives as part of rippled version 3.1.3, which first shipped on May 8. The XRP Ledger Foundation flagged the upgrade on May 14, co-developed alongside the RippleX team, and the message was clear: update your nodes or get left behind.

What the upgrade actually fixes

The headline change is automatic deletion of expired NFTokenOffer entries. When someone accepts an NFT offer on the ledger, the system will now scrub any expired offers tied to that token in the same transaction.

Beyond the NFT cleanup, the amendment introduces an invariant check for Permissioned Domains. Invariant checks are essentially safety rails baked into the protocol, rules that must always hold true regardless of what transactions do. Adding one for Permissioned Domains means the ledger can catch edge-case violations before they become actual problems.

Advertisement

There are also fixes for vault and lending operations. Trust-line token limits will now be properly enforced during VaultWithdraw transactions, closing a gap that could theoretically allow withdrawals to exceed intended constraints. Loan accounting for defaulted or impaired loans gets corrections too, ensuring the numbers actually add up when things go sideways with a borrower.

The node upgrade problem

As of mid-May, only about 40-46% of XRPL nodes had upgraded to version 3.1.3. That’s a concerning number when an amendment is days away from activation.

Nodes that haven’t upgraded will become “amendment-blocked” once fixCleanup3_1_3 goes live. That means they can’t process transactions or participate in the consensus mechanism.

The XRP Ledger Foundation has been pushing communications to node operators. Amendment blocking is a well-known consequence in the XRP Ledger’s governance model, where amendments require sustained validator support over a two-week period before activation.

Stabilization over spectacle

XRPL has been seeing increased network activity recently, including notable minting of RLUSD, Ripple’s dollar-pegged stablecoin. The ledger is also building out infrastructure for tokenized vaults and institutional lending. The collaborative effort between the XRP Ledger Foundation and RippleX teams on this release reflects a deliberate strategy of patching the foundation rather than racing to ship new protocol features.

What this means for investors

No significant price movement has accompanied the announcement or the approaching activation date. The fixes directly support three growth vectors for the network: NFT marketplaces, tokenized vaults, and institutional lending.

The node upgrade rate also deserves attention. If a significant portion of nodes remain unupgraded past the activation date, it could temporarily reduce the network’s operational capacity.

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.