XRP Ledger activates a network upgrade on May 27 via the fixCleanup3_1__3 amendment, bundling critical fixes across NFTs, Permissioned Domains, Vaults, and the Lending Protocol. The XRPL Foundation set the default validator vote to Yes given the maintenance nature and scope of the patches.
The upgrade exposes how XRPL's amendment process distributes control over protocol changes. Unlike proof-of-work blockchains where miners enforce consensus rules, XRPL relies on validator-driven governance. Validators must achieve 80 percent supermajority approval for any amendment to activate. This threshold forces genuine consensus rather than unilateral developer deployment.
Version 3.1.3 of rippled, the reference implementation, bundles multiple bug fixes targeting ecosystem stability. The NFT fixes address transaction handling in the NFT marketplace, while Vault improvements enhance custody and security mechanisms. Lending Protocol patches strengthen collateral calculations and liquidation mechanics, both critical for DeFi applications built on XRPL.
The amendment framework creates natural checkpoints for blockchain splits. If validators fracture over a contentious upgrade, two chains emerge. Exchanges and market participants then choose which version to support, effectively deciding the economically dominant chain. This mechanism contrasts sharply with Ethereum's centralized core developer group or Bitcoin's rough consensus model.
XRPL's validator set includes node operators from Ripple, institutional players, and independent operators. The 80 percent threshold means holdouts cannot unilaterally block upgrades, but neither can a small cabal force changes. The May 27 activation requires sufficient validator adoption before the amendment takes effect.
The timing signals confidence in validator alignment. Maintenance upgrades typically face high approval rates, but the supermajority requirement remains non-trivial. Any validator running outdated software after May 27 risks forking off the canonical ledger. This creates operational pressure to upgrade while preserving validator sovereignty through explicit choice rather than automatic enforcement.