Former Ripple CTO Criticizes Bitcoin Knots Over Failed BIP-110 Fork

What to Know

• Former Ripple CTO David Schwartz criticized Bitcoin Knots for portraying disruption on the minority BIP-110 branch as Bitcoin-wide network problems.
• BIP-110 failed to activate, leaving enforcing nodes on a minority chain that fell behind because most miners supported the Bitcoin network.
• Bitcoin Knots maintained its position while preparing mitigation measures and proposing a new proof-of-work algorithm for affected chain states recovery.

 

Former Ripple CTO David Schwartz has criticized Bitcoin Knots for its description of events surrounding the failed BIP-110 Bitcoin fork. According to Schwartz, the project presented misleading information by describing the resulting network situation as an attack against Bitcoin.

He questioned whether Bitcoin Knots intended to embarrass itself or mislead people who lacked sufficient context about the incident. Moreover, Schwartz argued that people should reject such messaging regardless of their personal views about the controversial BIP-110 proposal.

Bitcoin Knots had warned users that Bitcoin was under attack while claiming that block production had slowed considerably. However, community context attached to its post challenged those claims and explained that Bitcoin’s main network remained operational.

Instead, BIP-110 failed to activate as a soft fork, causing Bitcoin Knots nodes to separate from the dominant chain. Consequently, Schwartz’s criticism centered on how Bitcoin Knots characterized problems affecting its minority branch as broader Bitcoin network issues.

Also Read: Coreum Bridge Loses 200,000 XRP as Analysis Exposes Critical Verification Failure

BIP-110 Minority Chain Falls Behind Bitcoin

Monitoring information shared by Bitcoin commentators placed the chain split at block 961,632 during the unsuccessful BIP-110 activation. Most miners remained with Bitcoin’s established chain, leaving the BIP-110 branch with considerably less computing power supporting block production.

At one stage, Bitcoin’s dominant chain reached block 961,681 while a BIP-110-enforcing node remained at block 961,633. Additionally, the minority branch reportedly required several hours to produce individual blocks because it received limited support from miners.

Bitcoin’s network normally targets an average block interval of approximately ten minutes through adjustments to its mining difficulty. Hence, lengthy intervals on the BIP-110 branch reflected its reduced mining power rather than problems affecting Bitcoin’s majority chain.

Bitcoin Knots Maintains Its BIP-110 Position

Despite Schwartz’s criticism, Bitcoin Knots maintained its position and encouraged users who downgraded their software to install its latest version. The project also revealed work on a mitigation strategy designed to repair chain states affected by the unsuccessful BIP-110 activation.

Moreover, Bitcoin Knots announced plans to select a new proof-of-work algorithm using a deterministic random selection process. Schwartz’s response ultimately challenged the project’s presentation of the fork rather than offering an assessment of BIP-110’s technical objectives.

His remarks emphasized the distinction between disruption on the minority BIP-110 branch and conditions across Bitcoin’s dominant network. Bitcoin’s majority-supported blockchain remained operational, while limited miner participation left the BIP-110 branch significantly behind the main chain.

Also Read: Trump Media Posts $238 Million Q2 Loss as Crypto Holdings Lose $307 Million in Value

The post Former Ripple CTO Criticizes Bitcoin Knots Over Failed BIP-110 Fork appeared first on 36Crypto.