Validators embrace XRP Ledger's recent upgrade. But not everyone’s on board yet
AI-assisted summary based on the linked source. Verify market-moving details at the original publisher before acting.
The XRP Ledger has released its new server software version 3.2.0, aimed at reducing operating costs and improving network stability, particularly to attract institutional users. While the upgrade is making progress, it has not yet become the dominant version among all nodes on the network. Data from XRPSCAN indicates that about 43% of the roughly 833 active nodes have upgraded to v3.2.0, with 51% still running the previous v3.1.3. Despite the slower overall node adoption, validators—who play a crucial role—have largely adopted the new software, with approximately 89% of the 35 validators on the trusted Unique Node List running version 3.2.0. Crossing the 80% validator threshold means the upgrade is officially recognized at the network level.
In addition to the software upgrade, there is an on-ledger amendment called fixCleanup3_2_0 currently undergoing a formal vote among validators. This amendment includes important security fixes and improvements for newer XRP Ledger features such as single-asset vaults, permissioned decentralized exchanges, multi-purpose tokens, and an on-chain lending protocol that allows loans against pooled collateral. Unlike the server software update, which has already passed, this amendment is polling well below the necessary support threshold, indicating that validator voting on this aspect is lagging behind.
Ripple, the company behind the XRP Ledger's creation, has voted in favor of the fixCleanup3_2_0 amendment. Validators that do not upgrade to the new software and vote in favor of the amendment risk being disconnected from the network in what is known as an amendment-blocked state. This situation underscores the distinction between upgrading software and voting for protocol amendments, a two-step process critical for continued network compatibility and security.
The adoption status matters because the new software version is designed to make the XRP Ledger more efficient and appealing for large-scale institutional use, potentially influencing future growth and usage patterns. Meanwhile, the delayed approval of security-related amendments poses risks to the integrity and functionality of recent ledger features until consensus is reached. The ongoing split in node and validator adoption highlights the challenges of coordinating upgrades in decentralized networks.