Validators to decide XRPL’s May 27 upgrade

The XRP Ledger amendment fixCleanup3_1__3 is scheduled to activate on May 27. The change requires more than 80% support from trusted validators sustained for 14 days to become permanent. Version 3.1.3 of rippled bundles fixes for NFTs, Permissioned Domains, Vaults and the Lending Protocol. The XRPL project’s blog has set its default vote to Yes.

Under XRPL’s amendment rules, validator support determines whether the new rules take effect. Each server operator maintains a Unique Node List, or UNL, of validators it trusts. A server counts validation votes only from validators on its UNL. An amendment becomes permanent after a supermajority of trusted validators on servers’ UNLs signal approval for at least two weeks.

Servers that do not upgrade to rippled 3.1.3 by activation will become amendment-blocked if the threshold is met. Amendment-blocked servers lose the ability to determine ledger validity, submit or process transactions, participate in consensus or vote on future amendments until they update.

Infrastructure operators that remain on pre-3.1.3 code — including exchanges, custodians, wallets and explorers — will not participate in the canonical ledger while amendment-blocked. Users routing through those providers may be unable to submit transactions, confirm ledger validity in explorers or process payments through apps until operators upgrade.

A credible rival chain would require validators willing to produce ledgers under the old rules, a competing UNL that nodes can adopt or that software defaults to, maintained builds of the old code and support from wallets, exchanges and market makers. XRPL documentation cites research indicating competing UNLs may need up to 90% overlap in the worst case to prevent a split.

XRPL co‑creator David Schwartz has argued that raw node count is a poor proxy for consensus power because anyone can run large numbers of low-cost nodes. He described consensus legitimacy on XRPL as flowing from curated trust lists, validator coordination and economic adoption rather than from total node numbers.

The amendment process therefore tracks validator votes rather than raw node totals. If the validator supermajority approves and operators upgrade, the activation will apply the fixes in 3.1.3 without network-wide disruption. If significant providers remain out of date, those providers will experience localized outages until they update.