The XRP Ledger's next maintenance upgrade, version 3.1.3 of the rippled software, is set for May 27. The update bundles fixes covering NFTs, Permissioned Domains, Vaults, and the Lending Protocol. But before those changes become permanent, the network's trusted validators must hit a two-week approval threshold.
How the Amendment Process Works
XRPL uses an amendment process that requires more than 80% support from trusted validators — the operators who run the nodes that decide which rules apply. That support must stay above the line for two consecutive weeks before new rules lock in. The system doesn't rely on raw node counts; as XRPL co-creator David Schwartz put it, node count is a poor proxy for consensus power. Instead, server operators curate Unique Node Lists, or UNLs, to decide who they trust to validate transactions.
What Non-Upgrading Servers Face
Servers that don't upgrade by the activation deadline will become amendment-blocked. That's a stiff penalty: they lose the ability to determine the ledger's current validity, submit transactions, participate in consensus, or vote on future amendments. In other words, if you run a node and skip this update, your machine effectively goes dark on the network.
The Fork Question
A credible XRPL fork isn't simple. It would require five layers: a set of old-rule validators, a rival UNL, old-rule code, infrastructure support from wallets, exchanges, and explorers, and market recognition. XRPL documentation notes that competing UNLs may need up to 90% overlap in the worst case to prevent a split. That high bar makes an accidental fork unlikely, but it also means any deliberate fork faces serious coordination hurdles.
Infrastructure Risks If Upgrades Lag
Even if validators meet the threshold, the upgrade can still cause headaches downstream. Exchanges, wallets, and block explorers that stay on pre-3.1.3 software risk service disruptions — unconfirmed transactions, explorer errors, and general inconsistency. The ripple effect means the May 27 deadline matters for more than just node operators. Anyone running infrastructure that touches the ledger should check their version.
Server operators and infrastructure providers have until May 27 to update. After that, the two-week validator countdown starts — and the network moves forward with or without the stragglers.
