TLDR
- Ripple CTO David Schwartz shared detailed data on the XRPL Hub’s performance for the first time.
- Schwartz confirmed that the XRPL Hub has been running smoothly on version 2.6.2 without any operational issues.
- The XRPL Hub is currently operating below capacity, which allows it to avoid activating peer reservation settings.
- Ripple CTO rejected proposals to add features solely for generating revenue for validators.
- Schwartz emphasized that changes to the protocol must be driven by real demand, not validator profit.
Ripple CTO David Schwartz has revealed new details about the XRPL Hub, a private infrastructure he has been operating. This disclosure marks the first public look at the system’s performance, providing key benchmarks for those managing or studying XRPL infrastructure. Schwartz shared the hub’s operational data, which includes information about its traffic, response times, and connection stability.
Data Released by Ripple CTO Shows XRPL Hub Performance
Schwartz has been running the XRPL Hub on version 2.6.2 for over a month without issues. In his update, he made the hub’s hostname and port details public so node operators could examine it in real network conditions. Schwartz’s graphs showed traffic levels, peer activity, and response times, offering valuable insights into the hub’s operation under live conditions.
The hub is currently operating below capacity, meaning Schwartz has not needed to activate peer reservation settings. He clarified that he could enable these restrictions if usage increases. For now, the system is handling the traffic without any need for adjustments.
Following the release of this data, some members of the XRP community discussed the possibility of expanding XRPL’s functionality to create new income streams for validators. However, Schwartz dismissed the idea, stating that it goes against the core principles of the ledger. He emphasized that introducing features solely to generate revenue for validators is not aligned with XRPL’s goals.
He acknowledged that staking opportunities might appeal to XRP holders, but he rejected the idea of altering the protocol for that reason. Schwartz reiterated that the ledger’s financial components should serve broader use cases. He made it clear that changes to the protocol must be driven by real demand, not by a desire for validator profits.
Complexity of Introducing Smart Contracts
Schwartz also addressed the challenges of introducing advanced smart contract capabilities to XRPL. He explained that such changes require substantial engineering work and carry uncertainties regarding their success. Even well-received features like the automated market maker feature don’t guarantee widespread adoption.
Schwartz warned that any significant modifications to the ledger must come from a clear demand. He stressed that the community must demonstrate strong support before any major changes are implemented.


