David Schwartz, Ripple CTO Emeritus and one of XRP Ledger (XRPL) core developers, highlighted the network’s stability ahead of the key v3.2.0 upgrade. Meanwhile, XRPL Foundation revealed migration steps that validators need to follow due to the name transition from rippled to xrpld.
Ripple CTO Emeritus Highlights XRP Ledger Hub Stability
Ex-Ripple CTO David Schwartz took down his XRPL hub to upgrade to v3.2.0, he confirmed in a X post on June 17. Before taking the hub offline, Schwartz shared performance data showing strong stability over the past month.
The strong performance metrics indicated improved stability, efficiency, and security following recent XRP Ledger upgrades. This comes as the network aims to boost scalability and reduce costs amid tokenization and DeFi push.
Ripple CTO Emeritus noted that metrics showed only one notable incident of an unexplained burst of peer disconnections. He claimed it is likely related to a network outage near the hub.
After completing the upgrade, David Schwartz confirmed the hub was “back online and stable.” The XRP Ledger hub was down for almost 18 minutes, slightly longer than the planned 10 minutes.
“The extra downtime was due to the XRPL software taking about five minutes longer than expected to shut down cleanly,” Ripple CTO Emeritus added.
One XRP community member questioned how David Schwartz can perform XRPL hub shutdown as he is no longer Ripple CTO. He said, “Anyone can run an XRPL node, hub, validator, history server, or anything else they want.”
Key Changes in the XRPL 3.2.0 Upgrade and Migration Steps
As CoinGape reported earlier, XRP Ledger released the v3.2.0 upgrade that introduces the new fixCleanup3_2_0 amendment. The amendment includes bug fixes and cleanups, particularly for Single Asset Vaults, the Lending Protocol (XLS-66), DEX operations, Multi-Purpose Tokens (MPT), and permissioned domains.
The major visible change in this release is renaming of the core server from rippled to xrpld. The binary is now xrpld, and the main configuration file has also changed. This transition affects service names, default paths, and requires node operators to follow a structured migration process.
XRP Ledger Operations emphasized in an X post that updating to 3.2.0 requires following the official migration guide and backing up key files. Validators need to back up critical files first and remove the old rippled package to avoid data loss.
According to XRPL data, 14% nodes have updated to the latest release. The upgrade is also set to reduce the memory footprint by up to 40% and operating costs for nodes amid the scalability boost for tokenization and payments.
Ripple CTO Emeritus’ sharing stability metrics ahead of the mainnet upgrade to boost confidence among tradFi and partners. Recently, the company has launched the XRP Ledger (XRPL) AI Starter Kit to enable agentic payments using XRP and RLUSD.
-1024x669.jpg "This June, Pride Month May Be Losing Its Sparkle")
