CryptoSlate
XRPL's known amendments page schedules fixCleanup3_1_3 for activation on May 27, bundling fixes for NFTs, Permissioned Domains, Vaults, and the Lending Protocol into rippled 3.1.3. The XRPL blog set the default vote to Yes, and the amendment requires more than 80% support from trusted validators sustained for two weeks before the new rules become permanent. Servers that fail to upgrade become amendment-blocked — they can no longer determine ledger validity, submit transactions, or vote on future amendments.
Why it matters
Co-creator David Schwartz used the moment to clarify what a real XRPL fork would actually require, and his answer exposes how protocol legitimacy works on any chain. Raw node count is a poor proxy for consensus power: a system that weighs votes by node count creates a cheap attack surface, since anyone can spin up thousands of machines. XRPL routes legitimacy through Unique Node Lists (UNLs) — curated sets of trusted validators whose messages each server counts during consensus. The 80%-for-two-weeks threshold ensures the entities the network already trusts have reached a durable agreement before rules become permanent. XRPL documentation cites research showing rival UNLs may need 90% overlap to prevent a fork, meaning a dissenting set that diverges sharply from the canonical validator cohort risks producing a ledger that cannot sustain its own consensus.
Market impact
A credible XRPL fork would need five layers beyond unupgraded nodes: old-rule validators still producing ledgers, a rival UNL servers can configure to, a code distribution preserving the old rules with default routing, infrastructure support from wallets, exchanges, and explorers, and market recognition. The economics of following the canonical chain almost always outweigh building a parallel one, and the canonical chain is whichever the market decides is real. Sustained infrastructure lag across exchanges, wallets, or custodians still running pre-3.1.3 software would create user-facing friction — failed transaction submissions, explorers unable to confirm ledger validity, payment apps dropping off — even as the upgraded chain continues normally.
Frequently asked questions
-
What is XRPL's fixCleanup3_1_3 amendment activating on May 27?
It is rippled version 3.1.3, bundling fixes for NFTs, Permissioned Domains, Vaults, and the Lending Protocol. Activation requires more than 80% support from trusted validators sustained for two weeks before the new rules become permanent.
-
Why does David Schwartz say raw node count is a poor proxy for consensus power?
Because a system that weighs votes by node count creates a cheap attack surface — anyone can spin up thousands of machines at low cost. XRPL routes legitimacy through Unique Node Lists of trusted validators rather than counting every node equally.
-
What would a credible XRPL fork actually require?
Five layers beyond unupgraded nodes: old-rule validators still producing ledgers, a competing Unique Node List servers can configure to, code preserving the old rules with default routing to the rival UNL, infrastructure support from wallets, exchanges and explorers, and market recognition of the new chain.
-
What happens to servers that don't upgrade by May 27?
They become amendment-blocked: they lose the ability to determine ledger validity, submit or process transactions, participate in consensus, or vote on future amendments — turning infrastructure lag into operational cost for exchanges, wallets and custodians still on pre-3.1.3 software.
-
How does XRPL's governance layer compare to Bitcoin and Ethereum?
XRPL makes the legitimacy layer explicit through UNLs and the 80%-for-two-weeks threshold. Bitcoin embeds the equivalent in mining power distribution and economic node adoption; Ethereum embeds it in validators, staking economics, and social consensus around client software. All three convert coordinated human…
CoinDesk
TheBlock
CoinTelegraph
WuBlockchain