David Schwartz, chief architect of the XRP Ledger and Ripple’s CTO Emeritus, has upgraded his independent hub server to xrpld 3.2.0 as the network rolls out its latest server software. Schwartz said the migration took 18 minutes, longer than the planned 10-minute maintenance window because the system needed extra time to shut down core processes safely and prevent database corruption.
He described the interruption as brief and said the software performed as expected on critical infrastructure. Schwartz also shared that his hub had only one separate outage over the past month, lasting about one minute, and said that incident was caused by a local internet provider rather than the software itself.
New York Hub Upgrade Serves as a Live Network Test
The migration drew attention because Schwartz’s New York-based hub functions as an important transit node in the XRP Ledger ecosystem. The server helps connect validators, reduce latency, and support ledger synchronization across the network. Its successful move to xrpld 3.2.0 offered a practical signal that the release is ready for use on significant infrastructure.
Node operators across the network are continuing to upgrade to the new version. Based on the data Schwartz published, his server transition remained stable and did not encounter major issues during the process.
rippled Name Retired Under XLS-0095
One of the most visible changes in version 3.2.0 is the official renaming of the server software from “rippled” to “xrpld” under the XLS-0095 specification. The update removes the remaining Ripple branding from the codebase that powers the network.
Supporters of the change see it as a step that reinforces XRP Ledger’s identity as an independent network. The rebrand also draws a clearer line between Ripple as a company and the decentralized blockchain maintained by a global group of developers and validators.
Memory Use Falls by 30% to 40%
The release also includes technical changes beyond the name update. According to the published details, memory consumption is down by about 30% to 40%, reducing the hardware burden required to run nodes. That lowers operating demands for participants managing network infrastructure.
Developers also removed outdated amendments from the codebase and added fixes aimed at issues affecting decentralized finance applications. The stated goal is to improve efficiency while making long-term maintenance easier. Lower system requirements could make it easier for more independent operators to join, which may help broaden validator distribution across the XRP Ledger network.
In that sense, xrpld 3.2.0 is not just a routine software release. It combines a naming shift, lower resource usage, and maintenance-focused code changes, while Schwartz’s completed migration offers a concrete example of how the rollout is progressing.