David Schwartz, Ripple’s CTO emeritus and one of the XRP Ledger’s original architects, moved his independent hub server to xrpld 3.2.0 as the network’s latest software release reached operators. Summary David Schwartz moved his independent XRPL hub to 3.2.0 after a brief maintenance window successfully. The upgrade renames rippled to xrpld, giving XRP Ledger software a clearer network identity. Cleanup fixes target vaults, lending, permissioned DEX tools, Multi-Purpose Tokens, and permissioned domains for operators. Schwartz said on X that he was taking his hub down for about ten minutes to upgrade to 3.2.0. He also shared one month of performance charts and said they showed only “one real event,” an “unexplained burst of peer disconnections” likely tied to a nearby network outage. I’m about to take my hub down for about ten minutes to upgrade to 3.2.0. Here’s the performance graphs for the past month. They show only one real event, an unexplained burst of peer disconnections likely associated with some network outage somewhere close to the hub. pic.twitter.com/xLBStkZ72f— David ‘JoelKatz’ Schwartz (@JoelKatz) June 16, 2026 XRP Ledger 3.2.0 upgrade reaches operators The XRP Ledger 3.2.0 release is now available for server operators. The official XRPL release describes version 3.2.0 as mainly a cleanup and maintenance update. The release retires amendments that have been active for more than two years. It also continues the modularization of libxrpl and adds fixCleanup3_2_0, which bundles fixes for newer XRPL features. The update affects Single Asset Vaults, the Lending Protocol, the permissioned DEX, Multi-Purpose Tokens, and permissioned domains. The fixes cover precision, rounding, invariants, and validation checks used by those tools. As previously reported by crypto.news, Schwartz recently explained his long role in XRP Ledger development while developers prepared version 3.2.0. That report noted that the release would rename rippled to xrpld and require some operators to update systems. xrpld rename changes software identity One of the most visible changes is the software rename. Under XLS-0095, the core server binary moved from rippled to xrpld, while the default configuration file changed from rippled.cfg to xrpld.cfg. The official migration guide says operators moving from version 3.1.3 to 3.2.0 must follow extra steps because the rename changes default configuration and database paths. XRPL urged operators to upgrade to keep service continuity. The name change also carries community meaning. It moves the reference server away from older Ripple-branded naming and toward a clearer XRP Ledger identity. Some supporters may view that as a step toward stronger network independence. Still, legal and regulatory questions depend on more than software labels, so the change remains technical and branding-related. Schwartz hub points to network reliability Schwartz’s hub is not a validator replacement. It works as part of wider peer infrastructure that helps participants connect, exchange data, and observe ledger behavior. His public upgrade gives the community a visible example of a long-time XRPL architect running the new release on live infrastructure. The post also gave a short view into month-long hub performance. Schwartz said the only real event in the charts was linked to peer disconnections. The issue appeared local to the hub’s network path rather than a confirmed XRP Ledger failure. The maintenance took slightly longer than planned because the server needed more time to shut down safely. That detail was not confirmed in the readable X preview. XRPL development continues beyond payments The 3.2.0 release also connects with broader XRPL work on finance tools. As crypto.news reported earlier, XRPL has been preparing native lending and programmable escrow features for more advanced on-chain activity. Those plans rely on reliable server software and clean upgrade paths. A release that removes old amendments, cleans up code, and fixes DeFi-related components supports that direction without changing the network’s role overnight. As crypto.news reported earlier, XRPL operators also faced upgrade pressure around version 3.1.3, when nodes that missed the deadline risked amendment blocking and service disruption.
