The XRP Ledger's fixCleanup3_1_3 amendment activates on May 27, 2026 — but as of May 17, fewer than half of the network's validators had installed the software version that carries it. XRPL Foundation Director of Community Hussein Zangana, known as Vet on X, issued a public warning that day: 40% of the network had updated to version 3.1.3, with nine days left. Any node still running older code when the amendment goes live faces amendment-blocking — a state where the node can no longer communicate with the network, validate ledger entries, or process transactions.
That four-day window is now the operative pressure point.
What fixCleanup3_1_3 does
The amendment is a maintenance release. Version 3.1.3, released by the XRP Ledger Foundation on May 8, 2026, bundles fixes across several features: NFT processing, permissioned domains, vaults, and a new lending protocol. The XRP Ledger Foundation's release notes instruct every server operator to upgrade immediately. The amendment itself, fixCleanup3_1_3, is tagged default-yes — meaning it activates automatically once it clears the support threshold, without requiring a separate opt-in vote from validators.
How XRPL amendments activate
The XRP Ledger's amendment mechanism works on a two-week clock. Once a default-yes amendment appears in a new release, it enters a mandatory 14-day activation period. To lock in cleanly, it is supposed to hold support from more than 80% of trusted validating nodes for the full two weeks, per the XRPL documentation. The fixCleanup3_1_3 window opened May 13. Lock-in is expected May 27.
If a node has not upgraded by that date, it does not simply stop receiving the amendment — it becomes amendment-blocked. Amendment-blocked nodes, per the XRPL's own infrastructure documentation, cannot validate ledgers, process transactions, or participate in consensus. They are effectively frozen out of the live network until they upgrade.
The compliance gap
Vet's May 17 post on X was unambiguous: "XRPL 3.1.3 is available for over a week now. 40% of the network is updated. The fix amendment in it will be active in 9 days. Every node that hasn't been updated to 3.1.3 will be unable to communicate with the network."
That figure — 40% — meant more than half of validators had not yet installed the update, with little over a week left. The warning came from the XRPL Foundation itself, the organization that co-maintains the network's default Unique Node List (UNL). The deadline was not speculative. XRPScan data confirmed the May 27 activation timeline.
Protos reported on May 23 that more than half of XRP Ledger nodes were still running outdated software with six days remaining. The compliance rate had not meaningfully improved in the week since Vet's warning.
What amendment-blocking means in practice
The XRP Ledger does not use proof-of-work or proof-of-stake. Consensus runs through a network of trusted validators, each of which maintains a local copy of the ledger and participates in agreement rounds. Amendment-blocking removes a node from that process entirely. It cannot see new ledger closes that incorporate the amendment's rule changes, and it cannot propose or validate transactions under those rules.
For an exchange or institutional custodian running its own XRPL node, this is not a theoretical risk. An amendment-blocked node would be unable to confirm or submit transactions — deposits, withdrawals, or any on-chain activity — on the live network until the operator upgrades.
Network-split risk
XRPL co-creator David Schwartz addressed the prospect of a chain split directly on May 18, following community concern about a contested validator split. Schwartz downplayed the probability, but walked through the mechanics: a functional fork would require a group of non-upgrading validators to form their own Unique Node List with enough members to produce a continuous ledger stream under the old rules.
The XRPL's UNL structure makes spontaneous splits structurally difficult — almost every operator relies on one of two UNLs maintained by Ripple-backed entities, meaning consensus converges on whichever chain those UNLs support. But Schwartz acknowledged the threshold: at a minimum, any group wanting to maintain the old ledger would need to find at least a handful of validators willing to run under legacy rules and update their local UNL to form a functioning minority chain. The practical cost of running a hosted validating node — a few thousand dollars annually — keeps that scenario non-trivial to execute but not impossible.
The more immediate and probable risk is a wave of amendment-blocked nodes: validators that simply fail to upgrade in time, fall off the live network, and create operational disruption for operators and users relying on them.
Market context
The compliance gap is arriving during a period of active institutional engagement with XRP. XRP-linked exchange-traded products posted $60.5 million in weekly net inflows for the week ending May 19, 2026, the largest weekly figure of the year, according to CoinDesk data cited by BingX and MEXC. Separately, blockchain analytics firm CryptoQuant reported that approximately 403 million XRP left Binance between May 3 and May 15, with most outflows in batches of 1 million XRP or more — a pattern consistent with whale or institutional custody transfers.
Both signals point to rising institutional exposure to XRP in the same window when the network's infrastructure reliability is under pressure. An amendment-blocking event on major exchange or custodian nodes during peak inflow activity would be a poor time for any operator to discover their node was not upgraded.
What operators need to do
The action is straightforward: upgrade to XRPL version 3.1.3 before May 27. The release is available from the XRP Ledger Foundation's GitHub repository and documented at xrpl.org. The Foundation's release notes state explicitly that the upgrade is mandatory for continued network participation.
The XRPL Foundation has been working with exchanges to inform them of the deadline, per Vet's May 17 post. Operators still running any version below 3.1.3 have four days. After lock-in, catching up requires the same upgrade — but in the interim, any blocked node will be unable to process transactions or participate in consensus on the live network.
Sources: XRPL Foundation release notes (xrpl.org/blog/2026/rippled-3.1.3); Vet (@Vet_X0) on X, May 17, 2026 (x.com/Vet_X0/status/2056146934071509460); David Schwartz (@JoelKatz) on X, May 18, 2026; Protos, "David Schwartz warns of hard fork because XRP nodes won't upgrade," May 23, 2026 (protos.com); CoinDesk ETF inflow data cited by BingX (bingx.com); CryptoQuant Binance outflow data cited by Bitcoin Sistemi (en.bitcoinsistemi.com); XRPScan amendment timeline data; XRPL amendment documentation (xrpl.org/docs/concepts/networks-and-servers/amendments).