XRPL v3.1.3 Released: The fixCleanup Amendment and What It Means for NFTs, Vaults, and the Lending Protocol

The XRP Ledger's latest release introduces a critical cleanup amendment with a default Yes vote — an unusual move that signals both urgency and the maturity of XRPL's amendment governance model.

The XRPL Foundation published version 3.1.3 of the XRP Ledger node software on May 14, according to the official xrpl.org blog. The release is technically a patch update — no new features, no protocol changes beyond the single amendment it introduces — but the details of how that amendment is being handled are worth paying attention to.

What the fixCleanup Amendment Does

The fixCleanup3_1_3 amendment addresses a set of edge-case bugs that surfaced in features added during the v3.x development cycle. Specifically, it targets issues in four areas:

• NFTs (XLS-20): Cleanup of ledger object lifecycle edge cases — conditions where NFT-related objects could be left in an inconsistent state under specific transaction sequences.
• Permissioned Domains: Fixes to how domain authorization records interact with account deletion and object cleanup.
• Vaults: Corrections to vault object handling, relevant to the emerging on-chain asset custody use cases being built on XRPL.
• Lending Protocol: Bug fixes in the native lending protocol's object management — a feature set that has been in development and is drawing significant builder interest.

None of these are catastrophic bugs. The XRPL Foundation's description frames them as cleanup — edge cases that needed tightening before more users and more volume arrive in these feature areas.

The Default Yes Vote — Why It Matters

What makes this release notable is that the fixCleanup3_1_3 amendment ships with its default validator vote set to Yes. That's not standard practice on XRPL. Most amendments ship neutral — validators review, debate, and vote individually, with the amendment activating only after 80% of the UNL has voted Yes for two consecutive weeks.

A default Yes vote means validators running v3.1.3 automatically support the amendment unless they actively override it. The practical effect is that the amendment is likely to reach the activation threshold faster than a standard amendment would.

What This Means for Builders

If you're building on XRPL in any of these four feature areas, v3.1.3 is worth tracking closely. The NFT and Lending Protocol fixes in particular affect areas where transaction volume is growing and where developers are actively building production products.

For node operators, the upgrade path is standard — there are no breaking changes and no migration steps beyond updating the rippled binary. The amendment activates on-ledger through the normal consensus process; node operators don't need to do anything special beyond running the new version.

For developers building on top of the lending protocol or vault features, watching the amendment's vote progress over the coming two weeks will tell you how quickly the fix takes effect on mainnet. You can monitor validator votes in real time through the XRPL amendment tracker.

The Broader Governance Signal

XRPL's amendment process is one of the more deliberate upgrade mechanisms in major public blockchain infrastructure. Changes require sustained supermajority validator support over a two-week window before activating — which means upgrades move slower than a centrally-controlled chain, but with a higher confidence threshold when they do activate.

The v3.1.3 release, and the default Yes approach, reflects a governance system that has matured to the point where the distinction between routine maintenance and significant protocol changes is well-understood by the validator community. That's not a minor thing for infrastructure that is increasingly being used for institutional-grade applications.

The full release notes are available on the xrpl.org blog. Node operators should plan upgrades accordingly.