Disclaimer: The opinions expressed by our writers are their own and do not represent the views of U.Today. The financial and market information provided on U.Today is intended for informational purposes only. U.Today is not liable for any financial losses incurred while trading cryptocurrencies. Conduct your own research by contacting financial experts before making any investment decisions. We believe that all content is accurate as of the date of publication, but certain offers mentioned may no longer be available.
Ripple CTO Emeritus and XRP Ledger chief architect David Schwartz has supported the global migration to xrpld 3.2.0 software and successfully moved his independent hub server to it. A brief technical interruption in the node's operation lasted 18 minutes instead of the planned 10, as the system needed slightly more time to safely shut down all core processes and prevent local database corruption.
The migration of Schwartz's hub confirmed the overall stability of the software, while the monthly peer chart he published showed only one minute-long outage, which was caused by a local internet provider.
XRP Ledger decentralizes further
This migration became a powerful political and symbolic gesture for the ecosystem. By removing references to the commercial company Ripple from the source code, the blockchain deprives regulators, including the SEC, of a key argument about the network's centralization.
Moreover, while other blockchains are becoming heavier and require increasingly expensive servers, XRP Ledger has moved in the opposite direction. The reduction in system requirements will make node maintenance more accessible to ordinary participants, attracting a new wave of geographically diverse independent validators.
The global update brought three key changes to the network architecture:
- Final rebranding of the software: Under the XLS-0095 specification, the network's server software was officially renamed from rippled to xrpld.
- Radical reduction in hardware requirements: Developers managed to optimize node RAM consumption by 30–40%.
- Technical code cleanup: Old software amendments were removed from the system, and a package was launched to fix bugs in the DeFi sector.
David Schwartz's own hub in New York operates as a powerful transit node that connects validators, reduces network latency, and ensures rapid ledger synchronization.
In this context, the fact that the network's creator personally supported the migration and upgraded his server confirms the legitimacy and full readiness of the new software for high loads across the ecosystem.
U.Today Editorial Team
Dan Burgin
