Ripple’s XRP Ledger Is About to Change: What Happens Next Week?

XRPL’s next major upgrade could slash node memory usage by 40% while boosting network efficiency and long-term scalability.

The XRP Ledger (XRPL) is set to activate version 3.2.0 of its core server software on June 15. While the update does not introduce major user-facing features, it includes several changes aimed at improving the network’s long-term operation.

Among the most notable is the renaming of the server software from “rippled” to “xrpld,” a move intended to better reflect the broader XRPL ecosystem and reduce confusion with other Ripple-related products.

Improving Network Efficiency And Stability

Following the upgrade, node operators checking their software versions will see “xrpld 3.2.0” displayed in the command line. Developers said the change reflects the growing independence and technical maturity of the XRP Ledger infrastructure.

The release also delivers significant performance improvements across the network. According to developers, server memory usage may drop by as much as 40%, allowing nodes to operate more efficiently under higher demand.

Beyond memory optimization, the update introduces additional system-wide refinements. These changes are designed to improve overall network efficiency. They also support higher transaction throughput as activity expands across decentralized finance, tokenization, and real-world asset applications.

In addition to performance upgrades, version 3.2.0 includes multiple bug fixes and technical refinements. Improvements to number handling, rounding logic, and core code maintenance are aimed at strengthening network stability without affecting end-user experience.

Notably, the upcoming release follows the deployment of version 3.1.3 on the XRPL mainnet in late May. That earlier update fixed issues involving NFTs, Permissioned Domains, Vaults, the Lending Protocol, and Multi-Purpose Tokens.

You may also like:

Most XRPL Nodes Already Upgraded

Network data indicates that about 84% of XRPL nodes have already adopted version 3.1.3. This level of adoption suggests the ecosystem is preparing for a relatively smooth migration to the new software version.

Developers are encouraging validators and node operators to update their systems before the activation date. Servers that remain on older versions may face limitations in participating fully in consensus and other network functions after the upgrade.

In addition to upgrade readiness, the release also includes ongoing security enhancements behind the scenes. Expanded AI-assisted testing and active bug bounty efforts are part of broader measures designed to strengthen the ledger. These efforts aim to improve resilience as institutional and blockchain-based use cases continue to expand.