BIP-110 Defeat Sparks Debate Over Separate Proof-of-Work Chain

Bitcoin (BTC) BIP-110 controversy has escalated into a dispute over the creation of a separate proof-of-work (PoW) chain. David Schwartz, Ripple (XRP) CTO emeritus, viewed continuing to operate a new chain after losing a soft fork vote as an attack rather than governance participation. According to CryptoPotato, Schwartz engaged in a debate with BIP-110 supporter loogart during an X conversation on March 31.
Loogart had opposed Bitcoin Core's direction and decided to create a separate chain using a different proof-of-work algorithm after hearing calls for a fork. Schwartz stated, "You're not still attacking; you moved from governance participation to attack when you didn't accept the defeat." He claimed there was ample evidence suggesting attempts to appear as legitimate governance disagreements.
Loogart countered that his group accepted their loss and continued their Bitcoin version elsewhere. He emphasized that neither public discussion, soft fork, nor subsequent hard fork constituted an attack since "no one was forced to follow us." The core issue lies in distinguishing BIP-110 itself from later hard fork attempts.
The official bitcoin/bips repository lists BIP-110 as a 'Reduced Data Temporary Softfork' with status 'Closed.' It proposed temporary restrictions on certain data fields for one year, including limits on new output scriptPubKey exceeding 34 bytes, OP_RETURN exceptions up to 83 bytes, and limited data pushes of 256 bytes. The article previously clarified that BIP-110 was a data restriction soft fork proposal separate from proof-of-work changes.
The current dispute stems from the creation of a new chain following the failed data restriction soft fork. This chain activated at block height 961,640 with a flagday hard fork. It replaced Bitcoin's mining algorithm SHA256d with BLAKE2b, introduced a 164-byte block header, and implemented a block size limit of approximately 300 kilobytes until September 2027.
Previous BIP-110-related fork chains failed to secure sufficient mining support. CryptoPotato reported that after splitting from the Bitcoin main chain at block height 961,632, supporting mining pool Roughnecks produced only two blocks before falling hundreds of blocks behind the main chain.
Bitcoin Knots developer Luke Dashjr advocated for the BLAKE2b transition on March 30. He argued BLAKE2b lacks known weaknesses like ASICBoost in SHA256d and that the new block header closes a vulnerability previously reliant on miner monitoring for block withholding.
Dashjr also faced controversy over conflicts of interest related to BIP-110 processing, with CryptoPotato reporting he was removed as an editor from the Bitcoin Improvement Proposal repository due to these issues. Opposing views were also publicized; Strategy founder Michael Saylor criticized BIP-110 for potentially restricting valid transaction functionality and creating a precedent that limits certain usage patterns through consensus restrictions.
The underlying dispute involves OP_RETURN data limitations. Bitcoin Core's removal of existing OP_RETURN data limits allowed non-payment data like Ordinals and Runes to occupy block space, while BIP-110 supporters argued for maintaining block space focused on payments. A soft fork introduces stricter consensus rules than current ones, whereas a hard fork creates an incompatible new chain.
This situation does not immediately alter Bitcoin's price or payment functionality but highlights the conflation of disputes over consensus rules, data storage, and mining algorithm changes under the same name. Korean investors now need to distinguish between BIP-110 and the BLAKE2b chain.
Korean Source
This article is an English localization of a Korean-language crypto news report. Original headline: 비아이피-110 패배 뒤 작업증명 체인 논쟁 확산