Ripple’s Schwartz Calls Out Bitcoin Knots for Misleading Network Narrative

Ripple Executive Questions Bitcoin Knots’ Network Communications

David Schwartz, the chief architect behind the XRP Ledger and a respected veteran developer at Ripple, publicly expressed strong criticism toward Bitcoin Knots regarding their handling of recent Bitcoin network communications. In a pointed message shared on X, Schwartz challenged the motivations behind Bitcoin Knots’ statements, directly questioning whether the project intended to damage its own reputation or was deliberately attempting to deceive community members who lacked comprehensive understanding of the technical situation. His intervention signaled growing concern within the broader cryptocurrency development community about the accuracy and integrity of network communications during periods of technical disruption.

Parsing the Real Events Behind the BIP-110 Controversy

Bitcoin Knots had issued urgent warnings claiming that the Bitcoin network was experiencing an “attack” and that block production rates had declined substantially. The project advised network users against downgrading their software and cautioned against adopting alternative node implementations, which it characterized as potentially insecure. These alarming communications caused concern among segments of the cryptocurrency community that relied on Bitcoin Knots’ guidance.

However, a different narrative emerged from analyses provided by Bitcoin community observers and blockchain monitoring services. According to these independent sources, the situation was not a traditional network attack but rather a technical consequence stemming from a failed soft fork activation attempt. The distinction proved crucial for accurately understanding what had transpired.

BIP-110 represented a proposed Bitcoin protocol upgrade seeking consensus through the soft fork mechanism. When this activation attempt failed to achieve sufficient support, nodes configured to enforce BIP-110’s parameters automatically diverged from the main Bitcoin blockchain at block 961,632. The majority of miners and network nodes continued operating on the main chain uninterrupted, while only nodes enforcing BIP-110 found themselves isolated on a minority chain. On-chain monitoring data documented this divergence precisely: the primary network had reached block 961,681 while BIP-110-enforcing nodes remained at 961,633, representing approximately eight hours of elapsed block production. Adding to this evidence, the BIP-110 chain’s block production slowed dramatically to intervals spanning several hours—compared to Bitcoin’s standard ten-minute target—reflecting minimal miner participation on the minority chain.

Governance Lessons and Bitcoin Knots’ Response

Despite evidence that BIP-110 had become an isolated minority chain, Bitcoin Knots persisted in its defiant position. The project directed users who had downgraded software to upgrade to its latest version and announced active development of mitigation strategies for affected nodes. Additionally, Bitcoin Knots revealed plans to implement a new proof-of-work algorithm through a deterministic random selection process.

Schwartz’s public criticism underscores a fundamental principle for cryptocurrency networks: transparent, technically accurate communication becomes especially critical during periods of protocol disruption or contentious upgrade attempts. When mischaracterized narratives about network attacks circulate, they can undermine community confidence and create unnecessary friction during technical incidents that require calm, factual analysis.

Source: David Schwartz, via U.Today. Not financial advice.