Ripple CTO Emeritus Claps Back: XRP Ledger Centralization Claims Debunked

Another day, another decentralization debate—and this time, the XRP Ledger is in the crosshairs. Ripple's former Chief Technology Officer just fired a volley at critics calling the network centralized. His rebuttal? A point-by-point dismantling of what he calls 'misguided' arguments.

The Core of the Controversy

Critics often point to Ripple's influence over validator nodes as proof of centralization. It's a familiar tune in crypto—where every chain not named Bitcoin gets accused of being a corporate puppet show. The CTO Emeritus counters that the XRP Ledger's consensus mechanism, the Federated Byzantine Agreement, is built for speed and efficiency, not just ideological purity. He argues that true decentralization is a spectrum, not a binary checkbox.

Validator Nodes Under the Microscope

The network's health, he insists, hinges on a diverse and growing validator set—not the absence of any single entity. The focus should be on resilience and censorship-resistance, not just counting who runs the servers. It's a pragmatic stance that prioritizes function over form, a move that would make any traditional finance exec nod in approval—after all, they've been running centralized systems for centuries and calling it 'stability.'

The Bigger Picture for Crypto

This spat highlights a fundamental tension in the industry: the trade-off between perfect decentralization and real-world utility. Blockchains chasing enterprise adoption often face these accusations. The retort from Ripple's camp is clear: building a payments rail that works at scale sometimes requires different architectural choices. Whether that satisfies the crypto purists is another matter entirely—most of whom are probably too busy checking their own node's uptime to care.

So, is the XRP Ledger centralized? The answer depends entirely on your definition. One thing's for sure: in the world of crypto governance, the only consensus harder to achieve than on-chain is off-chain opinion.

The XRP Ledger Centralization Allegation

In his thread, Bons lumped Ripple alongside Canton, Stellar, Hedera, and Algorand as networks with permissioned or semi-permissioned elements. His XRPL-specific charge was straightforward: because XRPL nodes typically rely on a published UNL, “any divergence from this centrally published list would cause a fork,” which in his view concentrates power in the hands of whoever publishes that list.

Bons framed it as a binary question: “either fully permissionless or it is not” and argued that even partial permissioning is a deal breaker. He also extended the critique into a broader institutional-adoption thesis: banks and incumbents may prefer controlled environments, but “those institutions will be left behind,” while “crypto natives” win by building and using fully permissionless systems.

Schwartz’s opening rebuttal attacked the logic of Bons’ “absolute power” framing. “‘…effectively giving the Ripple Foundation & company absolute power & control over the chain…’” Schwartz wrote, calling it “as objectively nonsensical as claiming someone with a majority of mining power can create a billion bitcoins.”

Bons responded that he wasn’t alleging supply manipulation or fund theft, but insisted majority influence can still matter. “They can not steal funds, either, but they could potentially double-spend & censor,” Bons said. “Which, again, is exactly the same if someone controlled the majority of mining power in BTC.” He then suggested they debate live on a podcast.

Schwartz rejected the equivalence on mechanics, emphasizing that XRPL nodes do not accept censorship or double-spend behavior simply because a validator says so. “That’s not true. XRPL and BTC don’t work the same,” Schwartz wrote. “You count the number of validators that agree with your node and your node will not agree to double spend or censor unless you, for some reason, want it to.”

He continued the point across multiple posts, leaning on a simple intuition: a dishonest validator is not an oracle; it’s just one vote. “If a validator tried to double spend or censor, an honest node WOULD just count it as one validator that it did not agree with.”

What Schwartz Says The Real Attack Looks Like

Schwartz acknowledged there is still a failure mode, but described it as a liveness problem rather than a theft or double-spend scenario. “Validators could conspire to halt the chain from the point of view of honest nodes,” he said. “But that’s the XRPL equivalent of a dishonest majority attack except they never get to double spend. The cure is to pick a new UNL just as with BTC you’d need to pick a new mining algorithm.”

He also argued the empirical record matters, contrasting XRPL with other major networks. “The practical evidence tells this story,” Schwartz wrote. “Transactions are discriminated against all the time in BTC. Transactions are maliciously re-ordered or censored all the time on ETH. Nothing like this has ever happened to an XRPL transaction and it’s hard to imagine how it could.”

Schwartz later laid out a more detailed explanation of XRPL’s consensus model, emphasizing fast “live consensus” rounds—“every five seconds”—where validators vote on whether a transaction is included now or deferred to the next round. In that framing, the system’s key requirement is not blind trust in validators, but agreement on whether a transaction was seen before a cutoff.

He argued XRPL needs a UNL for two reasons: to prevent an attacker from spawning unlimited validators that force excessive work, and to prevent validators from simply not participating in a way that makes consensus impossible to measure. “That’s it. There’s no control or governance here other than coordinating activation of new features,” Schwartz wrote, adding that validators cannot force a node to enforce rules it does not have code for.

Schwartz closed with a longer, unusually candid rationale: that XRPL’s architecture was intentionally built to reduce Ripple’s ability to comply with demands to censor, even if Ripple itself wanted to be trusted.

“We carefully and intentionally designed XRPL so that we could not control it,” he wrote. “Ripple, for example, has to honor US court orders. It cannot say no… We absolutely and clearly decided that we DID NOT WANT control and that it would be to our own benefit to not have that control.”

He added a blunt incentive argument: even if Ripple could censor or double-spend, using that power would destroy trust in XRPL and therefore destroy the network’s utility. “And the best way to be able to say ‘no’ is to have to say ‘no’ because you cannot do the thing asked,” Schwartz wrote.

At press time, XRP traded at $1.3766.