Ripple’s CTO, David Schwartz, has opened the doors to his long-running XRPL Hub, making critical network information publicly available. The move reveals real-time performance metrics such as uptime, peer data, and traffic charts, which were once kept within Ripple’s internal infrastructure. This decision transforms the previously private setup into a public reference point for XRPL operators.
Schwartz shared impressive stats about his XRPL Hub, including that the system has been running on version 2.6.2 for over a month without encountering any issues. The disclosure provides the hostname and port for those interested in connecting, alongside charts that display peer counts, latency, traffic load, and disconnection rates. These metrics offer a comprehensive view of the hub’s performance, helping others gauge their own XRPL setups.
My hub has been running 2.6.2 for more than a week now and there have been no issues. If you run an XRPL node, feel free to connect:
Hostname: hub . distributedagreement . com
Domain: distributedagreement . com
Port: 51235
PubKey:… pic.twitter.com/bcE3Dt4GPQ— David ‘JoelKatz’ Schwartz (@JoelKatz) December 4, 2025
Preparedness for Future Demand
Despite the current lack of peer reservations, Schwartz highlighted that the hub remains under capacity. As a result, the need for peer reservations hasn’t arisen yet. However, Schwartz is ready to enable peer reservations should demand increase, ensuring that the system remains scalable as more participants join.
The announcement comes amidst ongoing discussions around XRPL’s programmability. In response to some community members suggesting that validators should benefit financially from features added to the network, Schwartz expressed his disagreement. He believes that such a rationale doesn’t align with XRPL’s original design, emphasizing that features should drive real utility rather than just enabling financial incentives for validators. Schwartz also mentioned that the idea of staking for revenue, while appealing, isn’t sufficient to warrant significant changes to the network.
Caution on Major Smart Contract Additions
Schwartz also addressed the risks of adding radical smart contract functionalities to the network. He cautioned that such changes could lead to unpredictable outcomes and potentially disrupt core aspects of the XRPL. While he acknowledged the success of projects like automated market makers (AMMs), Schwartz stressed that the real-world usage of these features has yet to be proven on a wide scale. Therefore, he maintains that any major updates should be based on strong evidence of demand and necessity.
Ripple’s CTO has shown a clear commitment to transparency while maintaining a careful, evidence-driven approach to the evolution of XRPL. His decision to make operational data public sets a new precedent for openness in the XRP community. However, he continues to prioritize caution when it comes to altering the underlying structure of the network.
