Justin Bons Calls XRP Marketing Misleading as Closed-Source Code Hits Two Weeks

Cyber Capital Founder Targets Closed-Source Code

A centralization fight over XRP reignited this week after developers shipped an emergency update to the XRP Ledger without releasing the source code behind it. Cyber Capital founder Justin Bons says the token is being presented to individual investors as a decentralized network in a way that does not match how the system actually runs. The XRP price is not the subject of the argument; the dispute sits in the software layer underneath it. The latest flashpoint for the altcoin involves code governing the ledger's consensus and administration, which has stayed out of public view since late September.

The XRP Ledger, the Layer 1 blockchain that verifies transactions and carries consensus for the XRP ecosystem, received version 3.4.1 of its server software on September 25. Developers described the release as an emergency update addressing security-sensitive issues, and it included a change identified as fixBatchV1_2. What the team did not publish alongside it is the code for those security fixes. Withholding patch code even briefly is a sensitive step for a ledger whose pitch rests on open, verifiable operation. The developers have confirmed the source will follow later, together with a technical retrospective review of the changes.

Bons counts the closed period at roughly two weeks and still running as of publication. His case targets the unpublished section touching the network's governance and consensus structure, which he argues leaves serious questions open about how the system actually operates. The amendment tied to the update is expected to become mandatory on Friday, October 9. If it gathers enough support and activates, servers on older software will reach the amendment block and stop staying in sync with the network. Support for the change builds from validators already running the new release, which turns a disclosure dispute into a deadline for every operator still on the previous version. Older servers that fall behind stop processing the shared ledger state, which in practice removes them from the network.

UNL Validator Model Under Scrutiny

The focal point of the criticism is the XRP Ledger's Unique Node List, the UNL, the list of validators a node trusts when reaching consensus. The same infrastructure settles the token's payments and much of its DeFi footprint, which is why the governance layer draws this much attention. Unlike Bitcoin's proof-of-work design, the ledger runs on participants trusting a configured set of validators rather than competitive mining. Ripple and the XRP Ledger Foundation publish recommended validator lists that server operators can adopt as defaults. Anyone may run a validator, and operators stay technically free to configure whichever validators they choose. The constraint sits in the documentation, however: the ledger's own materials warn that a node whose list overlaps too little with the rest of the network can diverge from it.

That warning is what gives the recommended lists their practical weight, and it forms the core of Bons's case. He claims the institutions publishing those lists hold too much influence over the network, and that closing the source even temporarily creates a needless perception of risk, whatever its security justification. The developers, for their part, have confirmed the security-sensitive fixes remain unpublished in code form and that the release will come later with a technical evaluation attached. The tension between the team's security-first method and the transparency critics expect has become the main axis of the XRP governance debate.

Market readers are folding the dated risk into their positioning: XRP technical analysis now carries the October 9 activation alongside the usual support and resistance levels. Anyone weighing an entry into the token can follow our guide on where and how to buy XRP for the practical steps. The expectation among observers is that the argument intensifies in the coming days, hinging on whether the amendment actually goes mandatory.

Two Weeks of Closed Code, One Date

Our reading: the timing, not the patch, is what makes this fight land. Coordinated withholding of security fixes is standard practice across software generally, and publishing the code later with a retrospective review is a defensible plan. The problem is the sequence. Activation on October 9 would make the network require code the public has never seen, and that ordering hands critics their strongest line. Distribution questions are already live elsewhere on this ledger, where whale dominance dropped 27% in eight days by our recent count, and the ecosystem's calendar rolls on regardless, with David Schwartz's Swell 2026 keynote set for October 28. Two weeks of closed code is the number this debate will be measured against, and the window closes only when the code ships.