XRP Ledger v3.2.0 upgrade gains 89% validator support, clears activation threshold

The XRP Ledger’s v3.2.0 software upgrade has reached 89% adoption among the network’s most critical validators, clearing the 80% threshold required to proceed with activation. Of the 35 validators on the default Unique Node List, 31 have now upgraded to the new version, according to data from CoinDesk and XRPScan.

The upgrade, released on June 15, is designed to cut operating costs and improve network stability, particularly for institutional users. The most operationally significant improvement is a projected 30-40% reduction in memory usage, according to Yahoo Tech and Binance reporting.

While the software adoption among validators is strong, the broader rollout remains uneven. Of approximately 833 active nodes on the XRP Ledger, only 43% are running v3.2.0, while 51% still operate on the older v3.1.3 version, according to CoinDesk. However, the network’s amendment process relies on the validator threshold, not total node count, making the 89% figure the critical metric for determining whether the upgrade can proceed.

A separate on-ledger amendment bundled with the upgrade, called fixCleanup3_2_0, is progressing far more slowly. This amendment packages key security fixes and improvements for newer features including single-asset vaults, permissioned decentralized exchanges, multi-purpose tokens, and the network’s lending protocol. Support for fixCleanup3_2_0 currently stands at 40%, well below the 80% threshold needed for activation, according to Tech Times, Crypto News, and KuCoin.

The distinction between software adoption and amendment voting reflects how the XRP Ledger’s governance works. Validators can run the new software without formally voting to activate the bundled amendment, and the two processes move at different speeds. Ripple, the payments company whose founders created the XRP Ledger, has voted in favor of fixCleanup3_2_0, but broader validator consensus on the security fixes remains incomplete.

For validators that do not upgrade before the amendment activates, the network can place them in what it calls an “amendment-blocked state,” preventing them from processing transactions, according to CoinDesk. This enforcement mechanism incentivizes adoption, though the lagging amendment vote suggests some validators may be waiting to see how the security fixes perform or have other concerns about the bundled changes.

Sources

  • CoinDesk — validator adoption at 89% (31 of 35), software release date of June 15, 43% node adoption, fixCleanup3_2_0 amendment details and voting status, amendment-blocked state explanation
  • Yahoo Tech — 30-40% memory usage reduction projection
  • Binance — 89% validator support, 40% memory usage reduction, fixCleanup3_2_0 security fixes scope
  • Gate.com — v3.2.0 cleared critical adoption threshold on June 15
  • Tech Times — fixCleanup3_2_0 at 40% support
  • Crypto News — fixCleanup3_2_0 at 40% support and migration issues
  • KuCoin — fixCleanup3_2_0 at 40% support, migration monitoring

Give your feedback

Be the first to rate this post
or leave a detailed review



ECIKS.org is an independent media. Support us by adding us to your Google News favorites:

Post a comment

Publish a comment