Ripple has voted in favor of the fixCleanup3_2_0 amendment included in the latest XRP Ledger 3.2.0 upgrade. Meanwhile, validator and node operators are gradually moving to the new software version.
The upgrade introduces several technical improvements designed to strengthen network security, simplify maintenance and improve the experience for developers building on the XRP Ledger.
Ripple Backs the XRP Ledger 3.2.0 Amendment
Ripple officially supported the fixCleanup3_2_0 amendment, which is currently open for voting on the XRP Ledger mainnet.
The amendment has so far received 2.86% consensus from validators. However, significantly more support will be required before it can become fully active.
The update combines several bug fixes and improvements affecting important XRP Ledger features. These include Single Asset Vaults, the Lending Protocol, permissioned decentralized exchanges, Multi-Purpose Tokens and permissioned domains.
It also removes several older amendments that were activated more than two years ago. This cleanup could make the XRP Ledger more efficient for tokenization, decentralized finance and other blockchain applications.
XRP Ledger Node Adoption Reaches 26%
According to the latest available data, approximately 26% of XRP Ledger nodes have upgraded to version 3.2.0.
Around 65% of nodes continue to operate on version 3.1.3. The remaining nodes are still using earlier software releases.
Several major network participants, including Ripple, have already completed the upgrade. However, broader adoption will be necessary before the new amendment can achieve full activation.
The amendment must receive at least 80% support from validators on the default Unique Node List for two consecutive weeks.
Validators and node operators must upgrade before activation. Otherwise, they could become amendment-blocked and lose the ability to participate normally in the network.
Major Changes Included in XRPL Version 3.2.0
One of the most noticeable changes in XRP Ledger 3.2.0 is the renaming of the network’s core server software.
The server previously known as “rippled” is now called “xrpld.” The new name creates a clearer connection between the software and the wider XRP Ledger ecosystem.
XRP Ledger Operations also published instructions for validators preparing to install the latest release.
Operators were advised to back up important files before starting the upgrade. They were also instructed to remove the previous rippled package carefully to reduce the risk of data loss or installation problems.
Upgrade Could Reduce Node Operating Costs
The XRP Ledger 3.2.0 upgrade could reduce the memory requirements of network nodes by as much as 40%.
Lower memory usage may help validators and operators reduce infrastructure expenses. It could also make the network more scalable as demand for tokenized assets and digital payments increases.
These technical improvements may make it easier for institutions, financial companies and developers to operate XRP Ledger infrastructure.
David Schwartz, Ripple’s CTO Emeritus, recently highlighted the stability of the XRP Ledger ahead of the mainnet upgrade.
He also shared network performance data intended to strengthen confidence among traditional finance companies and Ripple’s institutional partners.
XRP Ledger Activity Falls During Upgrades
Despite the progress surrounding the upgrade, some XRP community members have raised concerns about declining network activity.
Active XRP Ledger addresses reportedly dropped by almost 50% over the previous two weeks. The number declined from approximately 50,000 addresses to around 25,000.
However, some industry observers believe the decline may be temporary. They argue that lower activity can occur when a network completes several software upgrades within a short period.
The XRP Ledger recently introduced version 3.1.3 before launching the latest 3.2.0 release. Therefore, validators, developers and users may still be adjusting to the recent technical changes.
The next major milestone will be whether enough validators upgrade and support the amendment to reach the required 80% activation threshold.
