Ripple Chief Technology Officer David Schwartz has made a blunt claim about control over the XRP Ledger: XRPL was designed so Ripple cannot control it. He said the company cannot censor transactions, reverse payments, or double spend on the network even if it wanted to, a statement that has pushed the long-running decentralization debate around XRP back into focus.
The latest discussion started after Schwartz used X to explain how XRPL addresses double spending, one of the core problems any blockchain has to solve. What drew the strongest reaction was not the technical explanation itself. It was his clear argument that Ripple intentionally avoided building a system the company could later dominate. As a U.S.-based company with investors, Ripple can be subject to court orders or regulatory pressure. Schwartz said that is exactly why the company did not want the power to alter transactions or freeze the ledger in the first place.
Schwartz frames lack of control as a design choice
According to Schwartz, XRPL was structured so that no single entity, including Ripple, can own or control the network. His position is simple: if a company has the technical power to intervene, it can also be forced to use that power. Remove the power, and outside pressure loses much of its force.
He also presented decentralization as a practical decision rather than a purely ideological one. In his view, the network’s credibility depends on the fact that Ripple cannot step in and rewrite outcomes. That point became the center of the exchange.
Bitcoin fork history used as the main comparison
The conversation then shifted to XRPL’s Unique Node List, or UNL, the validator framework used by the network. Critics argued that choosing a UNL creates coordination challenges and leans toward centralization. Schwartz pushed back by saying many decentralization arguments ignore how consensus works in practice. A Bitcoin node can reject an invalid transaction locally, but what the network accepts still depends on the broader set of participants.
He pointed to Bitcoin’s own history. Satoshi selected Bitcoin’s mining algorithm, and changing it would have required major coordination. When Bitcoin and Bitcoin Cash split, there was no central authority that resolved the dispute for everyone. Each side proposed its own rules, and users chose which software to run. Schwartz argued that XRPL would work the same way in a disagreement: different groups could publish their own software and preferred validator lists, and node operators would decide which version to follow.
Debate over XRP decentralization remains unresolved
That comparison did not settle the issue. Critics continued to argue that the UNL model introduces coordination costs that can concentrate influence. Schwartz’s answer was that no blockchain consensus system is as clean or as simple as critics often suggest, including Bitcoin’s.
His comments leave a clear message: Ripple wants the inability to control XRPL to stand as a central defense against claims of centralization. The broader dispute over how decentralized XRP really is remains open.