Bitcoin experienced a chain fork related to BIP-110 at block height 961,632. Monitoring data showed that the branch implementing BIP-110 quickly fell behind the main chain, with a noticeably slower block production rate, intensifying external skepticism about the fork's prospects.
Fell behind quickly after the fork
According to monitoring data, at the time of writing, the Bitcoin main chain has progressed to block 961,681, while a node running BIP-110 is stuck at block 961,633. This means this branch is 48 blocks behind the main chain.
The Bitcoin main chain typically operates with a block time of approximately 10 minutes. In contrast, the BIP-110 fork has an average block interval of about 6.9 hours, indicating significantly insufficient hash power support.
Miner support rate is only 2.6%
The majority of miners continue to follow the existing main chain and have not switched to the BIP-110 fork. Previously, some critics warned that if this proposal entered the signaling phase without sufficient miner support, a chain split could occur.
Strategy's Executive Chairman Michael Saylor previously stated on X that BIP-110 received only about 2.6% miner signaling support and failed to achieve broad consensus. He noted at the time that once nodes begin rejecting blocks without signaling, the fork could stall or gradually lose practical relevance.
Adam Back, CEO of Blockstream, also expressed opposition to the fork, stating that the forkers have diverged from the main chain and must bear the consequences. Based on current on-chain activity, the main chain continues to proceed normally, while the BIP-110 branch has not yet established a block production pace close to that of the main chain.
The dispute centers on data write restrictions.
The goal of BIP-110 is to limit the quantity and type of arbitrary non-financial data that can be written into Bitcoin transactions. Supporters argue that Bitcoin should be positioned as a peer-to-peer monetary system, not a general-purpose data storage network.
This proposal was put forward by the developer using the pseudonym Dathon Ohm, with long-time Bitcoin developer Luke Dashjr being one of its primary supporters. However, Bitcoin Core developers have previously opposed this approach, arguing that limiting strategies alone are insufficient, as the relevant data could still enter blocks through other means.
In 2025, Bitcoin Core 30 significantly increased the default OP_RETURN limit, raising the key cap from 83 bytes to 100,000 bytes.
Luke Dashjr still denies failure
Despite the branch being clearly behind, Luke Dashjr publicly denied that BIP-110 has failed. He accused opponents of deliberately misleading the public and stated that supporters should not accept such claims.
He acknowledged that blocks on the BIP-110 chain are produced more slowly, but considered this issue still acceptable. Thus, the debate surrounding this fork remains in the phase where the technical outcome has already materialized, but supporters have not yet stepped back.