The XRP Ledger's fixCleanup3_2_0 amendment was set to activate on July 29, 2026 at 09:57:00 UTC if support held, and servers below xrpld v3.2.0 risk being amendment blocked once it does. Validator adoption ran well ahead of general node adoption through July, leaving part of the network on older builds as the countdown closed.
Any XRP Ledger server still running below xrpld v3.2.0 risks becoming amendment blocked once the fixCleanup3_2_0 amendment activates, interrupting normal operation. An amendment-blocked server stops participating in consensus and falls out of sync while the ledger keeps moving without it. The amendment cleared the supermajority at 85.71% approval on July 15 and entered a two-week clock, placing activation on July 29 at 09:57:00 UTC if support did not dip.
Validators upgraded faster than the wider node set
On July 8, trackers showed roughly 833 active nodes, about 43% of them on v3.2.0 and about 51% still on v3.1.3. The UNL pool ran further ahead, with 31 of 35 validators, roughly 89%, already upgraded.
Adoption kept pushing higher into the second half of the month. By July 21–22, multiple trackers cited around two thirds of validators on v3.2.0, and one widely shared snapshot showed about 57.3% of nodes, around 481, on the new version.
Operators nudged to finish the job
Public nudges from operators followed. On July 22, validator account Vet urged anyone lagging to update before the window closed, warning that older servers risk becoming amendment blocked and hitting service issues once activation lands.
For operators, the change is mostly a compatibility and stability upgrade rather than an app-stack rewrite. The checklist is short: confirm build_version reads 3.2.0 or later through server_info, back up validator keys and snapshot the database directory, schedule a brief maintenance window, then use feature or server_features calls to confirm the node recognises the pending amendment.
Most XRP users should see little
Most holders of XRP will not notice much, because in a clean rollout balances update as usual. Some exchanges may post short maintenance windows around activation out of caution, and a wallet app can lag if it leans on an older public node that falls behind before its operator upgrades.
Anyone who misses the window can still upgrade afterwards and resync, with downtime while the node catches up.
Source: Crypto Daily
Trading involves risk.
Risk Disclaimer
