The XRP Ledger 3.2.0 upgrade has reached network operators, bringing infrastructure improvements and software changes across the ecosystem. David Schwartz, Ripple’s CTO emeritus and one of the original architects of the XRP Ledger, recently upgraded his independent hub server to the latest version after a short maintenance period.
Source: https://x.com/JoelKatz/status/2067004655021048252?s=20
The XRP Ledger 3.2.0 upgrade focuses on maintenance, cleanup, and reliability improvements. While the release does not introduce major new features, it strengthens existing systems and prepares the network for future development. As operators begin deployment, the update marks another step in the network’s ongoing technical evolution.
David Schwartz Completes Hub Upgrade
Schwartz announced on X that he temporarily took his hub offline to install the XRP Ledger 3.2.0 upgrade. He initially expected the process to take about ten minutes. However, the server required additional time to shut down safely before the installation could proceed.
Alongside the announcement, Schwartz shared performance data covering the previous month. He stated that the charts showed only “one real event,” which he described as an “unexplained burst of peer disconnections.” According to his comments, the disruption likely resulted from a nearby network outage rather than an issue within the XRP Ledger itself.
His hub serves as part of the broader peer-to-peer infrastructure that supports connectivity and data exchange across the network. Although the hub does not function as a validator replacement, it helps participants monitor network activity and maintain reliable connections.
Xrp Ledger 3.2.0 Upgrade Introduces Key Changes
The XRP Ledger 3.2.0 upgrade includes several technical improvements. Developers removed amendments that had remained active for more than two years. The release also continues the modularization of libxrpl, which supports long-term software maintenance.
In addition, the update introduces fixCleanup3_2_0. This package addresses issues affecting Single Asset Vaults, the Lending Protocol, permissioned decentralized exchange tools, Multi-Purpose Tokens, and permissioned domains.
The fixes improve precision, rounding processes, validation checks, and system invariants. As a result, operators gain a more stable software environment for running network services and supporting advanced blockchain functions.
Software Rename Marks New Network Identity
One of the most visible parts of the XRP Ledger 3.2.0 upgrade is the renaming of the core server software. Under XLS-0095, developers changed the server binary name from rippled to xrpld. They also renamed the default configuration file from rippled.cfg to xrpld.cfg.
The migration requires operators moving from version 3.1.3 to complete additional configuration steps. Network documentation advises operators to update systems promptly to avoid service interruptions.
Beyond technical changes, the new name creates a clearer connection to the XRP Ledger network. At the same time, the release supports broader development efforts, including lending tools and programmable escrow features that continue to expand the network’s functionality.
