XRPL v3.1.3: The Vault Lending Protocol and fixCleanup Amendment Explained

XRPL v3.1.3 ships the fixCleanup3_1_3 amendment — fixes for NFTs, Vaults, and the Lending Protocol, with a default Yes vote. Here's what changed and what it means for builders deploying on XRPL.

What Shipped in v3.1.3

On May 14, 2026, Ripple published version 3.1.3 of rippled — the reference server implementation of the XRP Ledger protocol. The release carries a single amendment: fixCleanup3_1_3, a bundled collection of targeted fixes across four protocol areas that have been live on the ledger: NFTs, Permissioned Domains, Vaults, and the Lending Protocol.

The default vote for this amendment is set to Yes — an unusual designation that signals the Ripple development team considers these fixes sufficiently critical to warrant accelerated validator adoption rather than the standard neutral-default amendment vote process.

Why a "fixCleanup" Amendment Exists

The XRPL amendment model is designed for additive protocol changes — new features require supermajority validator support before activating. But once a feature is live, edge cases and behavioral inconsistencies discovered in production require a different mechanism: a cleanup amendment that patches specific ledger object handling without altering the broader feature's design.

fixCleanup amendments are how the XRPL handles this. They are typically small, targeted, and set to default Yes because the alternative — leaving the inconsistency in a live protocol feature — carries more risk than fast-tracking the fix.

NFT Fixes

The NFT fixes in v3.1.3 address ledger object cleanup edge cases in the NFToken page structure. Specifically, the amendment corrects scenarios where NFToken deletions under certain ownership transfer conditions left orphaned page references that could cause inconsistent ledger state reads. This is a data integrity fix rather than a functional change — NFT creation, transfer, and burn operations continue to work identically, but the ledger's internal accounting is now consistent across all edge cases.

Permissioned Domains Fixes

Permissioned Domains — one of the most significant 2026 amendments for institutional RWA issuers — received cleanup fixes addressing domain credential validation edge cases. The fixes correct scenarios where credential lookup during domain-restricted asset transfers could produce inconsistent authorization results depending on ledger state ordering. For issuers using Permissioned Domains to enforce accredited investor restrictions on tokenized assets, this fix closes a potential compliance gap in the authorization layer.

Vault Fixes

The Vault object — XRPL's native on-ledger custody structure for tokenized assets — received accounting fixes that correct rounding behavior in vault share calculations under specific deposit and withdrawal sequences. The fix ensures that vault share math is deterministic across all transaction orderings, which matters for any application building yield-bearing or fractional ownership structures on top of the Vault primitive.

Lending Protocol Fixes

The Lending Protocol — XRPL's protocol-native lending mechanism currently in its pre-mainnet development phase — received fixes addressing MPT (Multi-Purpose Token) escrow accounting errors and missing keylet fields in general ledger entries. These are foundational data structure fixes that ensure the Lending Protocol's ledger objects are correctly formed before the feature reaches mainnet activation.

The verify_endpoints configuration parameter added in this release also supports local peer network development, making it easier for builders to test Lending Protocol integrations in controlled environments before mainnet deployment.

What Builders Need to Do

Server operators running an XRP Ledger node are urged to upgrade to v3.1.3 as soon as possible. The fixCleanup3_1_3 amendment will activate once it achieves the standard 80% validator supermajority with the default Yes vote — meaning adoption will be faster than typical amendments.

For application developers: the fixes are backward compatible. No API changes are required. Applications using NFTs, Permissioned Domain-gated transfers, Vault-based custody, or any future Lending Protocol integration will benefit from the improved ledger state consistency without modification.

The pattern of fixCleanup amendments following major feature deployments is normal XRPL protocol hygiene. What v3.1.3 signals is that the Vault and Lending Protocol are maturing toward mainnet readiness — edge cases are being systematically closed.