- XRPSCAN data showed 89% of the XRP Ledger’s 35 default UNL validators running the v3.2.0 server software as of July 8, above the 80% share amendments needed to activate.
- The release’s fixCleanup3_2_0 amendment held 19 of the 28 required validator votes and must sustain 80% support for two consecutive weeks before it takes effect.
- Node adoption is split, with 43% of roughly 833 active nodes on the new version and 51% still running the previous v3.1.3 release.
XRP Ledger server software v3.2.0 was running on 89% of the network’s 35 default Unique Node List validators as of July 8, XRPSCAN data showed, clearing the 80% share of trusted validators that amendments need before they can activate.
The formal on-ledger vote trails the software rollout. The release’s bundled fixCleanup3_2_0 amendment held 19 of the 35 trusted validators’ votes, short of the 28 required, according to XRPSCAN’s amendment tracker. Amendments activate two weeks after support first holds above 80%, so the countdown starts once the vote crosses that line.
Ripple’s own validator is among the 19 voting yes, alongside operators including Bitso, Peersyst and a group of university-run validators, the tracker showed.
Related: Bitcoin Squeezes Past $63K, But Traders Brace for “Monday Curse” to Strike Again
What Version 3.2.0 Changes
Released on June 15, v3.2.0 renames the XRP Ledger’s core server from rippled to xrpld under the XLS-0095 standard, a change that also moves default configuration and database paths.
The release retires more than 30 amendments that have been active for over two years, among them HardenedValidations, ImmediateOfferKilled and CheckCashMakesTrustLine, and continues splitting the codebase into the libxrpl library.
The fixCleanup3_2_0 amendment bundles corrections across the ledger’s newer institutional features: precision and rounding fixes for single-asset vaults and the lending protocol, an invariant fix for the permissioned decentralised exchange, validation of non-canonical multi-purpose token amounts, and a new check that stops deleted accounts leaving stray data behind.
Of roughly 833 active nodes on the network, 43% were running v3.2.0 as of July 8, while 51% remained on the previous v3.1.3 release, XRPSCAN data showed.
Under the ledger’s documented amendment mechanics, servers still running older software when an amendment activates become amendment-blocked and stop processing transactions until their operators upgrade.
The project urged operators to move in its release announcement: “If you run an XRP Ledger server, upgrade to version 3.2.0 as soon as possible to ensure service continuity.”
Related: TeraWulf Lands $19B Anthropic AI Deal, Sending Bitcoin Miners Soaring
Be the first to comment