BIP-110 Debate Separates Bitcoin Data Limits from Blake2b PoW Fork

The Bitcoin (BTC) BIP-110 debate has intensified alongside attempts to implement a BLAKE2b proof-of-work hardfork. The core issue centers on whether BIP-110 itself was meant to change the proof-of-work algorithm or if it was merely an extension of failed data limit softfork efforts. David Schwartz, Ripple (X) CTO emeritus, criticized the 'chain modification' phrasing in a recent X conversation, saying 'Listen to yourself.' The official Bitcoin/BIPs repository lists BIP-110 as 'Reduced Data Temporary Softfork,' authored by Dathon Ohm with status 'Closed' and dated December 3, 2025. It describes a one-year temporary deployment with restrictions on scriptPubKey (over 34 bytes), OP_RETURN (over 83 bytes), and data pushes exceeding 256 bytes.
BIP-110's original text does not mention proof-of-work changes or BLAKE2b transition. Meanwhile, btc-blake2b.org describes its own release as a 'proof-of-work hardfork inspired by BIP-110,' clarifying that 'BIP-110 is not this hardfork.' The release states it would replace the existing SHA256d proof-of-work with BLAKE2b. This has led to confusion between the official proposal and a separate fork narrative emerging after BIP-110's failure.
The timeline adds complexity: BIP-110's documentation cites an activation ceiling at block height 965,664 (around September 1, 2026), but Bitcoin development mailing lists already debated chain splits and mining halts on August 9. Jon Atack proposed moving the status to 'Closed' after a potential split during forced signaling intervals, while Murch noted BIP-110 failed with only two blocks found before stopping. Greg Tonoski countered that BIP-110 was activated at block height 961,633 with two bit 4 signal blocks.
Doubleblock reported that BIP-110-supporting nodes split from the main network at block height 961,632, creating a chain lagging by seven blocks as of reporting. Bitcoin.com News noted the forked chain produced only four blocks over seven days with over 400,000 pending transactions, lacking exchange support or market pricing. The technical dispute has also raised concerns about replay attacks—where transactions valid on one chain might be processed incorrectly on another if wallets and exchanges don't implement safeguards.
Bitcoin.com News highlighted that the debate has expanded beyond data limits to economic viability of the forked chain and user protection. While the main Bitcoin network's consensus rules remain unchanged, key infrastructure like major exchanges, wallets, and Lightning implementations have not confirmed support for the forked chain. The site previously reported on BIP-110's failed fork attempt alongside Dash Junior's announcement of a hiatus.
Korean Source
This article is an English localization of a Korean-language crypto news report. Original headline: 비아이피-110은 데이터 제한안, 작업증명 분기와 별개