XRP Ledger activates fixCleanup3_1_3; many nodes lag

The XRP Ledger activated the fixCleanup3_1_3 amendment on May 27, 2026. The upgrade is included in version 3.1.3 of the rippled software and applies maintenance fixes across several protocol modules.

The changes address handling of expired NFT offers, new security invariants for Permissioned Domains, improved withdrawal logic and single-asset vault behavior, and corrections to lending protocol trust line limits and related elements.

Nodes and validators that do not run the updated software before the deadline will become amendment-blocked and will be disconnected from the network, unable to participate in consensus, process transactions, or exchange ledger data with peers.

By mid-May, roughly 40% to 46% of network nodes had reported completing the update, leaving a substantial portion yet to migrate. The XRP Ledger Foundation and core developers advised operators to update ahead of activation to avoid availability issues.

On-chain activity remained high during the activation. In the 24 hours around the upgrade the ledger processed about 1.76 million transactions, including close to one million payments, and recorded more than 18,000 active accounts. Average ledger close times stayed below four seconds.

Decentralized exchange activity continued during the activation. Tens of thousands of automated market maker pools remained active, with the XRP/RLUSD trading pair among the most used on the DEX.

Market metrics showed little immediate change tied to the upgrade. XRP traded near $1.35 at the time of reporting, with a market capitalization above $83 billion, a 0.4% decline over 24 hours, and daily trading volume above $1.2 billion.

Ordinary token holders were not required to take any action. Wallets did not need to be connected, transactions did not require re-signing, and tokens required no migration. The ledger continued to accept and process transactions during the amendment activation.

Developers publish amendments and operators adopt them by updating rippled. When a supermajority of validators signals support and activation conditions are met, the amendment goes live. Maintenance-focused amendments are intended to remove accumulated data and correct protocol behavior rather than add user-facing features.

The activation occurred while many operators completed migrations to the new software version.