The ledger never lies, only the narrative hides. On October 8, a single X post accused the XRP Ledger of running closed-source code for two weeks, of maintaining a permissioned validator set, and of preparing to force an amendment on October 9 that would eject any node that refused to upgrade. Four days later, on October 12, Evernorth — a treasury vehicle holding 473 million XRP — was set to begin trading on Nasdaq. The criticism did not arrive in a vacuum. It arrived on a schedule.
That schedule is the first thing worth auditing. When an accusation lands inside the pricing window of a public listing, the responsible analyst separates the argument from its delivery vehicle. The argument can still be correct. The timing, however, is itself a data point — and it points toward a fund with a position, not a whistleblower with a conscience. None of that invalidates the claim. It only sets the burden of proof where it belongs: on evidence, not on timing. A critic who profits from being right is still a critic worth reading — but only after the artifact is checked.
To evaluate the claim, you need the architecture. The XRP Ledger has run a live mainnet since 2012. Its consensus is not Proof of Work and not Proof of Stake. It is RPCA — the Ripple Protocol Consensus Algorithm — a member of the Federated Byzantine Agreement family, the same lineage as Stellar's SCP. Validators do not mine and do not stake. They publish the ledgers they trust, and each validator configures a Unique Node List of peers it considers honest. Consensus emerges from the overlap between those lists. There is no slashing, no yield, no economic bond. Trust is configured, not purchased.
Justin Bons, of the fund Cyber Capital, calls this Proof of Authority. David Schwartz, the ledger's original architect and now CTO Emeritus, calls it open. Both are arguing about the same mechanism from opposite ends, and the mechanism is genuinely ambiguous — which is why this debate recurs every cycle and never resolves.
The stakes explain the heat. If XRPL is decentralized, it is a neutral settlement layer and XRP is a commodity-like bridge asset. If it is permissioned, it is closer to a company-controlled database with a tradable unit — a very different regulatory and reputational object. Neither side is debating philosophy. They are debating what XRP is allowed to be.
I have run this kind of audit before. In 2018, I reviewed 47 early-stage Ethereum contracts, and the lesson was consistent: the whitepaper describes intent, the bytecode describes reality, and they frequently disagree. In 2022, mapping $15 billion of stablecoin depegs across Aave and Compound, I learned the same thing at protocol scale. XRPL is no different. The question is not what the documentation says. The question is what the validator set actually does.
Three claims are on the table. Each carries very different evidentiary weight.
Claim one: XRPL is Proof of Authority. This is a rhetorical overreach. Traditional PoA — early BSC's 21 authorized validators — fixes its validator set inside the protocol. RPCA does not. Any operator can run a validator, a hub, or a history server, and any validator can choose which peers to trust. In that narrow sense, Schwartz is correct and Bons is imprecise. But imprecise is not wrong. Ripple publishes a default UNL, the dUNL, and a large share of validators follow it out of convenience rather than conviction. That is not protocol-level permissioning. It is de facto soft centralization — a real governance soft spot the industry has discussed for years and priced at zero. The gap between "open in theory" and "centralized by default" is exactly where both camps are half right.
Claim two: the ledger ran closed-source code for two weeks. This is the most serious allegation and the least evidenced. The rippled client is open source under an ISC license. If the claim is true, it points to a specific amendment or patch whose disclosure lagged — not to a closed client. I have watched teams ship quiet patches before a governance vote, and I have watched them ship quiet patches for mundane reasons. Without a first-party diff or a third-party audit, the claim stays unresolved. It is also the only claim here capable of causing real reputational damage. A true closed-source governance change would be a transparency failure. A false one would be a credibility failure for the accuser. Neither party has produced the artifact that settles it.
Claim three: an amendment will be "forced" on October 9. This one is mechanically grounded. XRPL amendments require roughly 80% validator support to activate. Once active, any node that has not upgraded can no longer reach consensus with the mainnet — effectively, it is dropped. Bons's framing of this as coercion is overheated, but it is not invented. It is the inherent property of a supermajority activation rule. A minority cannot veto. Schwartz's softer phrasing — that "software choice resolves disputes" — glosses over exactly this asymmetry. A supermajority threshold is not a dictatorship, but it is also not consent. That is why the October 9 deadline mattered more than the rhetoric around it: it was the one claim with a clock attached.
Here is the disclosure gap that neither side addressed: the amendment's actual contents were never published in the coverage. Was it a performance optimization or a governance parameter change? That distinction is the entire ballgame, and it was left blurry. An undisclosed amendment debated only in metaphor is, by definition, a transparency problem regardless of which camp wins the argument.
Tracing the ghost liquidity back to its source, the structural facts are dull and consistent. XRP has no staking yield, no liquidity mining, and no protocol-level token incentive. Its value capture depends on demand for settlement — bridge liquidity for cross-border payments — which routes overwhelmingly through Ripple's ODL corridors. That means user growth is driven by a single company, not a community. Whether or not you call that PoA, it is the same underlying condition: one actor carries the network's commercial weight. Stellar, by contrast, runs the same consensus family under a nonprofit foundation and attracts far less governance controversy — evidence that the mechanism is not the problem, the operator concentration is.
The validator economics reinforce the point. Because running a validator pays nothing, participation is a cost center sustained by conviction or subsidy. Networks that rely on volunteer validators drift toward whoever makes participation cheapest and most convenient — and that is the entity that publishes the default list. Convenience, not coercion, is how soft centralization actually forms.
The Evernorth listing does not change any of this. Moving 473 million XRP from secondary markets into a listed treasury is a float event, not a tokenomics event. It reduces near-term sell pressure and packages the asset into a regulated wrapper. Ripple, Pantera, and Kraken are backers. The structure — a SPAC merger with Armada Acquisition Corp II — resembles the Bitcoin treasury playbook: equity premium funds accumulation, accumulation feeds the narrative, the narrative widens the premium. That flywheel spins smoothly until the premium converges. Then it reverses, and the reversal is faster than the build. The disclosed backers matter here. Ripple is simultaneously a dUNL publisher, a major XRP holder, and an investor in the vehicle buying the token. That stack of roles is the real economic root of the centralization worry — not a code license, but a balance sheet.
The contrarian point is this: the decentralization debate is largely irrelevant to XRP's actual risk, and the market is watching the wrong variable. XRP's real competitor is not Ethereum or Solana. It is USDC and USDT in cross-border settlement, and an upgraded SWIFT. Institutional clients do not buy settlement rails because they are decentralized. They buy them because they are compliant and liquid. Bons's accusation attacks retail perception; it does not touch the institutional logic that actually holds XRP's use case together. On a bear-market tape, where survival outranks upside, that distinction matters more than any validator-count chart.
There is one exception, and it is the part almost nobody is pricing. Decentralization is coupled to XRP's securities status. Under Howey, the "efforts of others" prong turns on how much control a central party exerts. If the network is effectively controlled by Ripple — as the accusers argue — that prong becomes easier to satisfy, not harder. The irony is sharp: the same claim used to attack XRP's ethos, if validated by a regulator, strengthens the case against its token classification. The technical argument is a proxy war for a legal one. The ledger is being debated in public so that a courtroom argument can be rehearsed in advance.
So watch two signals next week, not the argument. First, whether any party publishes a first-party diff or a third-party audit answering the closed-source claim — silence will be its own verdict, and it will be read as confirmation. Second, Evernorth's first-day demand. If the treasury wrapper trades at a premium, the debate was noise. If it breaks issue, the "XRP as institutional treasury" story fails its first real test. The ledger will produce blocks either way. The question is who is actually signing them — and whether anyone outside the room can verify it.