What happened
Schwartz, who built much of the original XRP Ledger code and still speaks for Ripple's technical history, posted a clarification stating that Ripple does not control consensus on XRPL. U.Today reported the post on May 13 and flagged it as a response to a recurring misconception that Ripple, as the largest corporate steward of the network, can decide what the ledger validates. Schwartz's framing was narrow and technical. He didn't announce a governance change, a validator addition, or a protocol amendment. He drew a line between Ripple's commercial role and the consensus mechanism that decides which transactions get included in each XRPL ledger.
The distinction matters because XRPL consensus runs on Unique Node Lists, or UNLs. Each validator picks a list of validators it trusts. Transactions get confirmed when a supermajority of trusted validators agree. Ripple publishes a recommended default UNL, but it operates only a portion of the validators on that list, and node operators can swap in alternatives. Schwartz's post, per U.Today, was aimed at people conflating Ripple's outsized commercial footprint with veto power over the network's state.
Why it matters
This is a governance framing fight, and Ripple has been losing it in public for years. The SEC case settled the securities question for programmatic sales on exchanges, but the centralization argument never fully went away. Critics point to the default UNL, Ripple's escrow holdings, and the company's documentation footprint as evidence that XRPL is effectively a corporate-run chain. Schwartz is pushing back on the strongest version of that claim: that Ripple can decide what the ledger records.