XRPL v3.1.3 Released: Critical Fixes for NFTs, Vaults, and the Lending Protocol

The XRP Ledger reference implementation ships version 3.1.3 with the fixCleanup3_1_3 amendment — carrying critical bug fixes across four active feature areas. Server operators are urged to upgrade immediately.

Version 3.1.3 of rippled — the reference server implementation of the XRP Ledger protocol — was released on May 14, 2026. The release introduces a single amendment, fixCleanup3_1_3, which the XRPL Foundation is voting Yes on by default due to the critical nature of the included fixes.

The default Yes vote is a strong signal. The XRPL Foundation typically leaves amendment votes to validator operators. Defaulting to Yes means the Foundation considers these fixes important enough to push for rapid adoption across the validator network.

What fixCleanup3_1_3 Fixes

The amendment bundles fixes across four areas that have been active development fronts on XRPL:

NFT Fixes

The NFT implementation on XRPL has had several edge-case bugs related to object cleanup when NFT offers are cancelled or NFT pages are deleted. The v3.1.3 fixes address ledger object lifecycle issues — specifically scenarios where cancelled NFT offers or deleted NFT page entries left orphaned ledger objects that accumulated reserve requirements on affected accounts.

Permissioned Domains

Permissioned Domains are XRPL's mechanism for defining KYC/AML credential requirements for specific DEX pools and token interactions. The fix addresses a cleanup edge case where domain credential entries were not being correctly removed in certain deletion sequences, causing reserve to be locked incorrectly.

Vaults

XRPL Vaults — introduced as part of the DeFi protocol expansion — allow users to deposit assets and receive vault shares representing their proportional claim. The v3.1.3 fix addresses an accounting issue in vault share redemption under specific conditions involving partial fills on the DEX.

Lending Protocol

The Native Lending Protocol is still in its pre-mainnet development phase, but test implementations on Devnet and Testnet have been active. The fix addresses a collateral accounting bug discovered during Testnet validation that could cause incorrect collateral valuations under edge-case liquidation scenarios.

How XRPL Amendments Work

For readers unfamiliar with the amendment process: XRPL protocol changes don't activate automatically. An amendment requires sustained support from 80% of trusted validators for two continuous weeks before it activates on mainnet. This two-week window gives operators time to upgrade their software before the amendment goes live.

The process prevents hard forks — operators who don't upgrade in time will find their nodes in an amendment-blocked state (able to follow the ledger but not validate) rather than operating on a divergent chain. It's a deliberate design choice that prioritizes network cohesion over rapid deployment speed.

Who Needs to Upgrade

Any operator running an XRPL validator node, full history node, or clio server should upgrade to v3.1.3. The XRPL Foundation's guidance is explicit: "Server operators are urged to upgrade as soon as possible to ensure service continuity."

For token issuers, DeFi protocol builders, and NFT platforms building on XRPL, the upgrade itself is a server-side concern — your application code doesn't need to change. But if you're running infrastructure that depends on the features being fixed (NFT operations, permissioned domain transactions, vault interactions), you'll want your RPC provider to be on v3.1.3 before relying on those features in production.

The Bigger Picture: XRPL's Active Development Velocity

v3.1.3 follows v3.1.2 from March 2026 and v3.1.1 from January 2026. The cadence of point releases with targeted amendments reflects an XRPL development team moving faster than at any point in the ledger's history — driven by the institutional demand created by RWA tokenization activity and the DeFi expansion announced in late 2025.

The upcoming Native Lending Protocol and Smart Escrows (Advanced Programmability), previewed by XRPL Foundation Community Director Hussain Zangana in May 2026, will require their own amendments when they're ready for mainnet. v3.1.3 is part of the cleanup work that makes those larger amendments viable on a well-maintained ledger state.