David Schwartz has upgraded his independent XRPL hub server to version 3.2.0. In a post on X, he said the hub would go down for about 10 minutes for maintenance, then reported the upgrade was completed successfully. He also shared one month of performance charts and said they showed only “one real event,” described as an unexplained burst of peer disconnections that was likely tied to a nearby network outage rather than a confirmed XRP Ledger failure.
Version 3.2.0 is now in operators’ hands
The XRP Ledger 3.2.0 release is now available to server operators. Official release notes describe it as a cleanup and maintenance update, not a feature-heavy overhaul. The release removes amendments that have been active for more than two years, continues the modularization of libxrpl, and adds fixCleanup3_2_0, a bundled set of fixes aimed at newer XRPL components.
Those fixes touch Single Asset Vaults, the Lending Protocol, the permissioned DEX, Multi-Purpose Tokens, and permissioned domains. The listed areas include precision, rounding, invariants, and validation checks used by those tools. The changes may look narrow on the surface. For operators and services built around these components, they are operationally important.
The rippled name is being retired
One of the clearest changes in 3.2.0 is the software rename under XLS-0095. The core server binary shifts from rippled to xrpld, and the default configuration file changes from rippled.cfg to xrpld.cfg. The official migration guide says operators moving from 3.1.3 to 3.2.0 need extra steps because the rename changes default configuration and database paths. XRPL has urged operators to complete the upgrade to maintain service continuity.
The rename also changes how the reference server is presented to the community. The software moves away from older Ripple-branded naming and adopts a more explicit XRP Ledger identity. The source article notes that this should still be viewed as a technical and branding change; legal and regulatory questions do not turn on software labels alone.
Schwartz’s public upgrade offers a live infrastructure example
Schwartz’s hub is not a validator substitute. It sits within the broader peer infrastructure used to connect participants, exchange data, and monitor ledger behavior. His decision to publicize the upgrade gave the XRPL community a visible example of a long-time architect running the new release on live infrastructure.
The performance charts added a small operational snapshot. According to Schwartz, the only meaningful event during the month was the burst of peer disconnections. The report says the issue appeared local to the hub’s network path, not evidence of a confirmed XRPL problem. It also mentioned that the maintenance window ran a bit longer than planned because the server needed more time to shut down safely, though that detail was not confirmed in the readable X preview.
Cleanup work supports broader financial tooling on XRPL
The release also ties into wider XRPL work beyond payments. The source says XRPL has been preparing native lending and programmable escrow features to support more advanced on-chain activity. A release that removes old amendments, cleans up code, and fixes DeFi-related components strengthens the software base for that direction while keeping the focus on reliability and upgrade execution.
The article also points back to version 3.1.3, when some XRPL operators faced upgrade pressure and risked amendment blocking or service disruption if they missed deadlines. In that context, version 3.2.0 is centered on stability, migration, and maintenance. The biggest headline may be the new xrpld name, but the release is also about making sure the network’s server stack stays clean and dependable.