Ripple released a new software update, v3.2.0, for the XRP Ledger (XRPL) over three weeks ago. While a substantial portion of the Unique Node List (UNL) validators have adopted the new version, the overall adoption rate among general validator nodes remains notably lower.
Data from XRPScan indicates that as of the reporting date, only 43% of XRPL nodes, equating to 357 out of 828 total nodes, have upgraded to v3.2.0. In contrast, 51% of nodes, or 426 out of 828, are still running on the previous version, v3.1.3. This disparity highlights a gap in the network’s immediate uptake of the latest software.
Network Activation Amidst Adoption Gap
Despite the lower adoption among general nodes, the XRPL network considers upgrades activated once a sufficient percentage of UNL validators have upgraded. Currently, 89% of the UNL validators are running on the new v3.2.0 software. The XRPL protocol requires 80% of the UNL to activate network upgrades, a threshold that has been met. Specifically, 31 out of 35 UNL validators have cleared the necessary threshold for v3.2.0 activation.
The v3.2.0 upgrade introduces several changes, including the rebranding of the core server software from ‘rippled’ to ‘xrpld’. It also aims to reduce operating costs and memory usage by an estimated 30% to 40%, which could optimize institutional usage and improve network efficiency.
Amendment Voting Faces Deficit
However, an aspect of the v3.2.0 rollout is the ongoing voting process for an amendment titled ‘fixCleanup320′. This amendment is intended to deploy fixes for various components, including single-asset vaults, lending protocols, multi-purpose tokens, permissioned domains, and permissioned decentralized exchanges. To be approved, the amendment requires 28 out of the 35 UNL votes. As of the reporting date, only 17 UNL votes have been received for fixCleanup320, representing approximately 48.57% of the trusted validators having voted so far. This indicates a deficit in the votes needed for the amendment’s approval.
The timeline for the remaining nodes to upgrade to v3.2.0 remains uncertain. Similarly, the outcome of the vote for the fixCleanup320 amendment is yet to be determined. The exact release date of the v3.2.0 upgrade is also not precisely specified, beyond being over three weeks ago.
While the network technically considers the v3.2.0 upgrade active due to high UNL validator adoption, the slow uptake by general nodes and the current voting deficit for the fixCleanup320 amendment present ongoing points of observation for the XRPL network’s progression and security.
Why This Matters
The materials describe an update: Ripple released software update v3. The timeline for the remaining nodes to upgrade to v3.2.0.
Broader Context
Source materials place the factual news in this context: The latest infrastructure upgrade introduces several new features to the XRPL.
Leave a Reply