XRPL v3.2.0 tops default UNL threshold, but node uptake and amendment vote lag
Validator readiness is already above the 80% activation bar, while fixCleanup3_2_0 remains a separate, slower catalyst.
XRP Ledger’s v3.2.0 server release has reached roughly 89% adoption among default UNL validators, clearing the threshold required for activation if sustained for two straight weeks. The broader node base is still skewed to v3.1.3, and a separate security-focused amendment tied to the release is polling well below the software upgrade rate.
Key Takeaways
- XRPL server software v3.2.0 shipped on June 15 with stated goals of lower operating costs, improved stability, and stronger institutional appeal.
- XRPSCAN’s snapshot showed about 833 active XRPL nodes, with roughly 43% on v3.2.0 versus about 51% still running v3.1.3.
- Default UNL validators are further along than the node base: 31 of 35 validators were on v3.2.0, around 89%.
- The fixCleanup3_2_0 on-ledger amendment, which bundles security fixes and improvements for newer XRPL features, remained under voting and was described as polling far below the software rollout.
V3.2.0 Clears the Default UNL Bar, Pending the Two-Week Window
XRPL’s v3.2.0 server software rolled out June 15 with an operational pitch: cheaper to run, more stable, and more attractive for institutional use. By July 8, the upgrade had already crossed the key validator-layer threshold on the default Unique Node List.
XRPL’s activation mechanics are binary and time-gated. “For a new software version or amendment to activate, it needs sustained support from more than 80% of validators on that list for two straight weeks.” On the default UNL of 35 validators, 31 were running v3.2.0, about 89%, which is above the >80% requirement. The open question is duration, since the two-week condition is not confirmed as met.
For traders, that split matters because it frames the rollout as closer to completion at the consensus layer than the broader network distribution implies. Validator readiness can be high even while a large share of nodes remain on the prior release.
FixCleanup3_2_0: The Security Amendment on a Separate, Slower Track
The more material risk sits in the second track. Alongside the software release, XRPL has an on-ledger amendment, fixCleanup3_2_0, still under formal voting as of July 8.
The amendment bundles security fixes and improvements tied to newer XRPL features, including single-asset vaults, permissioned decentralized exchanges, multi-purpose tokens (MPTs), and the lending protocol. It also adds internal checks intended to prevent deleted accounts from leaving behind stray data.
Critically, the amendment is not moving in lockstep with the software upgrade. It was described as polling far lower than the v3.2.0 adoption rate, reinforcing that “upgrading a validator and voting the amendment through are two distinct steps.” Ripple voted in favor of fixCleanup3_2_0.
Operationally, the amendment introduces a hard edge for laggards. “Validators that fail to upgrade before the amendment activates risk being cut off from the ledger in what the ledger calls an amendment-blocked state.” That turns version lag from a cosmetic split into a potential connectivity event if the vote eventually clears.
Signals That Could Tighten—or Extend—the Upgrade Timeline
The first timer is validator support persistence. The threshold that matters is whether default UNL support for v3.2.0 stays above 80% for the required two straight weeks, since that is the activation condition.
The second timer is distribution cleanup. XRPSCAN’s node mix is still tilted toward v3.1.3, so traders will be watching whether v3.2.0’s share rises toward, and then through, the older version’s roughly 51% share as operators catch up.
The third timer is the amendment itself. The exact fixCleanup3_2_0 vote tally was not specified, only that it is well below software adoption, so any published percentage or visible acceleration in voting becomes the next concrete catalyst. Operator communications that explicitly reference avoiding an amendment-blocked state would also be a tell that upgrade urgency is shifting from optional to mandatory.
Adoption Split: Validators Upgraded, the Broader Node Base Hasn’t
XRPSCAN showed about 833 active nodes at the time of the snapshot, with roughly 43% on v3.2.0 and about 51% still on v3.1.3. That is a slow-looking rollout if the only lens is raw node count.
But the validator layer is telling a different story. On the default UNL, 31 of 35 validators were already on v3.2.0, around 89%. In XRPL’s market structure, that’s the more actionable metric because it governs whether upgrades and amendments can actually flip into an active state.
This is why traders tend to weight UNL readiness over broad node distribution. A network can look “behind” by node count while still being close to a consensus-layer transition, and those transitions are where operational risk and narrative volatility tend to concentrate.
Two-Track Activation Risk Is the Real Trade Signal Here
I treat this as two separate catalysts that can hit on different clocks. v3.2.0 is already above the default UNL threshold, so the real test is whether that support stays pinned for the full two-week window, because that’s what turns “rolled out” into “activated.”
The bigger uncertainty is fixCleanup3_2_0. If that amendment eventually reaches activation while polling is still lagging, the setup starts to look structural rather than narrative-driven, because amendment-blocked risk forces late operators to move. This looks more like a sentiment catalyst than a fundamental shift until the amendment vote tightens and the network’s long tail of nodes closes the version gap in a way that reduces surprise downtime risk.
