TLDR
- David Schwartz shut down his personal XRPL hub to prepare for the version 3.0 upgrade.
- He released one month of performance data from the experimental node before the shutdown.
- The XRP Ledger version 3.0.0 includes fixes for escrow accounting and AMM rounding bugs.
- The update introduces new simulation metadata fields and the STInt32 type.
- Schwartz’s node maintained bandwidth between 100 and 200 Mbps with peaks during high loads.
David Schwartz has taken his XRP Ledger (XRPL) hub offline to prepare for a planned upgrade to version 3.0, marking the transition with the release of detailed performance data. His hub had served as a consistent routing and peer discovery point within the XRP Ledger, offering key infrastructure insights. The timing aligns with the official launch of XRP Ledger version 3.0.0, which introduces multiple system-wide changes.
XRP Ledger Sees Version 3.0 Launch
The XRP Ledger version 3.0.0 introduces system improvements, including tighter API validations and updates to escrow handling. Developers also fixed metadata omissions and rounding issues affecting AMM-related transactions. These changes aim to improve accuracy and consistency across the platform.
The release includes simulation metadata additions and a new STInt32 type for improved internal type handling. Refactored continuous integration workflows now support better test coverage. Testing infrastructure has also been modularized and enhanced using the doctest framework.
The update strengthens backend processes by improving debugging capabilities and reducing manual intervention. These changes help ensure stronger validator behavior. Version 3.0 also reinforces operational consistency for long-term network stability.
Ripple Labs confirmed the official rollout of version 3.0.0 earlier this week. The update followed months of testing and codebase validation. Network participants are expected to transition gradually as validators adopt the upgrade.
Schwartz’s Experimental Hub Showcases Performance Data
Schwartz released one month of performance metrics before shutting down his long-running XRPL node. His hub maintained steady traffic flow, serving as a routing and peer endpoint. Bandwidth remained consistent throughout the observation period.
Here’s the last month of stats up until I shut it down to upgrade it: pic.twitter.com/mOmAZyg8vX
— David ‘JoelKatz’ Schwartz (@JoelKatz) January 25, 2026
Data shows outbound traffic peaked at 219 Mbps, while inbound rates reached up to 138 Mbps during high network activity. Average throughput stayed between 100 and 200 Mbps. These stats reflect stable performance under varying conditions.
Latency remained controlled with occasional high-percentile spikes, touching 1,270 milliseconds in rare instances. These moments may indicate peer-related inefficiencies. Still, overall node responsiveness stayed within reliable thresholds.
Schwartz also tracked disconnection data, reporting 17.4 average peer drops every five minutes. Abuse-driven disconnections averaged only 0.2, suggesting minimal disruption. Peer count stabilized near 386 by the shutdown date.
Schwartz Prepares Upgrade for Hub v3.0
The shutdown process for Schwartz’s hub followed a methodical approach, according to statements from the former CTO. The reboot intends to align the node with XRP Ledger version 3.0. Schwartz emphasized infrastructure readiness as a core reason.
His node had long served the XRPL network and demonstrated consistent reliability. The decision to retire it temporarily reflects a forward-looking infrastructure plan. Schwartz confirmed the reboot will include architectural updates.
“Keeping my infrastructure current is part of supporting XRPL’s long-term growth,” he shared on social media. The upgraded hub aims to reduce latency and support routing for global throughput. Schwartz will implement the updated node using modern test frameworks.