Former Ripple CTO and current JST Fellow David Schwartz weighed in to fuel debate across the XRP community by providing a more realistic perspective of the real-world transaction ability of XRP Ledger.
His comment addressed one of the memes most often repeated during XRP discussions, which is: that this XRP Ledger can process 1,500 transactions per second (TPS).
Schwartz noted that the number has long been put forward as evidence for XRPL’s speed superiority, but he emphasized this figure is a technical maximum under ideal conditions rather than a practical limit of the live network.
Schwartz responded to questions from the Banaxchange media platform and said that there is no hard cap on how many transactions can be sent to the XRP Ledger simultaneously.
It is theoretically possible to propose a very high number of transactions at the same time as they disperse over nodes, flow through networks more slowly, and eventually arrive at validators for confirmation. What this shows is that the system accommodates an architectural flexibility in how it accepts incoming transaction flow.
But Schwartz noted that while taking transactions is one thing, rapidly confirming them is another. He said that if someone suddenly sent an extremely large batch (for example, one million transactions) the network would not just instantly clear them. Validators and nodes receive, verify, relay and process that volume over a significant time period.
While the XRP Ledger scales up for heavy loads, there are limits as discussed by Brad, and certain financial institutions taking a long-term position in liability with money crowded out will in some cases, need liquidity to be finalized in real time on top speed, not just load handling.
And this difference is at the heart of Schwartz’s “reality check.” The 1,500 TPS statistic you always hear is actually what the XRP Ledger can do if everything is correct and optimal in real world conditions, he stated.
That number should not be misinterpreted as the throughput of the live network we expect to have during its current deployment. Schwartz also said the infrastructure running today is not always taking advantage of that degree of efficiency.
This distinction is relevant because XRPL supporters often point to the 1,500 TPS marker in XRP’s marketing narratives relative to much slower blockchains. Essentially, Schwartz is saying that the design itself has the potential to allow for a lot of transactions per second, in practice and depending on network conditions, node capacity, validator coordination and operational costs, less so.
He also cautioned that requiring the network to ride all the way up to that ceiling in the current environment was probably a fool’s errand. According to Schwartz, the most obvious path for pushing transaction counts to high as 1,500 TPS at this point would be a spam-like behavior—artificially spamming the network with unnecessary transactions. He argued this would be of more detriment than use.
The higher throughput, he said, stresses all of the players in the network. All nodes need to see the transaction, check signatures, send data across, process the request, write a record and return results. Indeed, at scale that increases the infrastructure costs for node operators and validators while also putting operational strain on them, running a more expensive network.
Schwartz has also faced backlash recently from many ultra-bullish XRP price predictions, including ones that claim XRP could reach $10,000 within the next ten years. He criticized the predictions as unrealistic and once more rebuffed conspiracy-fueled narratives.
His most recent comments cement a theme that has rung true in past assessments: the long-term success of XRP will be built upon reasonable expectations and pragmatic use cases, rather than grandiose promises about speed or wild predictions on price movements.
Conclusion
David Schwartz’s clarification provides a much-needed counterbalancing perspective in the current debate around XRP performance. Although proponents tout that the XRP Ledger can process upwards of 1,500 transactions shortly after inception, this belief is a slightly simplified version of the whole picture.
The figure is considered a theoretical maximum rather than the actual consistently achieved throughput on the live network today. In real conditions, the system is capable of processing a massive throughput of transactions, but confirmation through finality in terms of validator performance and on-chain network load and operating conditions.
Which means, its not maximum capacity but sustained performance under real-world load. Schwartz further raised the possibility that forcefully raising the network to unprecedented levels would inflate costs and put pressure on infrastructure.
In conclusion, the data shows that XRP Ledger is a strong, efficient, low-cost blockchain system, but actual performance can either exceed or fall short of theoretical limits depending on how those theoretical limits are presented.
