David Schwartz, CTO Emeritus at Ripple and one of the core developers of the XRP Ledger (XRPL), highlighted the stability of the network ahead of the major upgrade to version 3.2.0. Meanwhile, the XRPL Foundation revealed the migration steps that validators must follow due to the name transition from ripple to xrpld.
Ripple CTO Emeritus highlights stability of XRP Ledger Hub
David Schwartz, former CTO of Ripple, confirmed that he has taken down his XRPL hub to upgrade to version 3.2.0. Share X On June 17th. Before shutting down the position, Schwartz shared performance data showing strong stability over the past month.
Strong performance metrics indicated improved stability, efficiency and security 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 unprovoked burst of peer-to-peer disconnection. He claimed it was likely linked to a network outage near the hub.
After the upgrade was completed, David Schwartz confirmed that the center was “back online and stable.” The XRP Ledger position remained idle for approximately 18 minutes, slightly longer than the planned 10 minutes.
“The additional downtime was due to the XRPL software taking about five minutes longer than expected to close cleanly,” added Ripple CTO Emeritus.
A member of the XRP community wondered how David Schwartz could close the XRPL position since he no longer serves as Ripple’s CTO. “Anyone can run an XRPL node, a hub, a validator, a ledger server, or whatever else they want,” he said.
Major changes in XRPL 3.2.0 upgrade and migration steps
As CoinGape previously reported, XRP Ledger has released the upgrade to version 3.2.0 Which introduces the new modification fixCleanup3_2_0. The modification includes bug fixes and cleanups, especially for single asset vaults, lending protocol (XLS-66), DEX operations, multi-purpose tokens (MPT), and permissible ranges.
The main change evident in this version is Rename the primary server from wavy to xrpld. The binary file is now xrpld, and the main configuration file has also changed. This migration affects service names and default routes and requires node operators to follow a structured migration process.
XRP Ledger Operations confirmed in an X post that updating to 3.2.0 requires following the official migration guide and backing up key files. Auditors need to back up important files first and remove the old wavy package to avoid data loss.
According to XRPL data, 14% of nodes have been updated to the latest version. The upgrade is also set to reduce memory footprint by up to 40% and running costs for nodes amid enhanced scalability for tokenization and payments.
Ripple CTO Emeritus share stability metrics ahead of mainnet upgrade to boost trust between tradFi and partners. The company recently launched the XRP Ledger (XRPL) AI toolkit to enable it Proxy payments using XRP and RLUSD.
