Bitcoin Miner Rejects BIP-110 Despite Pool Support, Stalling Fork

A Bitcoin miner rejected the implementation of BIP-110 around August 10, 2026, despite utilizing a mining pool that officially supported the proposal. The incident reveals a critical friction point in Bitcoin's governance, where individual software configurations can override the operational policies of the pools they join.

According to reports from CoinDesk and corroborated by industry sources including SignalPro and SimpleMining, the miner in question operated through the Ocean mining pool. While Ocean signaled its support for BIP-110, the individual miner configured their own node to reject the proposal. This discrepancy contributed to the eventual failure of the BIP-110 fork, which stalled after producing only two blocks.

The Battle Over Data Fields

BIP-110 was designed as a consensus-level limit on the size of data fields, specifically targeting OP_RETURN. The goal of the proposal was to prevent arbitrary data from distorting network incentives by restricting how much non-transactional information could be embedded into the blockchain.

In the Bitcoin ecosystem, Bitcoin Improvement Proposals (BIPs) serve as the primary mechanism for protocol upgrades. While mining pools often signal support for these changes to coordinate network-wide adoption, the decentralized nature of the network allows individual miners running their own nodes to maintain final veto power over which blocks they accept as valid.

The Miner-Pool Power Dynamic

This event underscores a persistent tension in the 'miner vs. pool' power dynamic. While pools provide the necessary hash power to secure the network and coordinate block production, the ultimate authority rests with the node operator. When a significant number of individual miners reject a BIP that pools have endorsed, it creates a fragmented environment that can lead to chain splits or total instability during protocol upgrades.

For the broader market, this incident serves as a reminder that pool signaling is not a guarantee of implementation. The failure of BIP-110 demonstrates that decentralized autonomy can effectively block changes even when centralized entities are in alignment.

Future Implications

As Bitcoin continues to evolve, the gap between pool signaling and individual miner behavior remains a primary risk factor for network upgrades. Observers will be watching to see if future BIPs incorporate more robust coordination mechanisms or if the network continues to rely on a fragile consensus between pool operators and independent node runners. For now, the stalled BIP-110 fork stands as a case study in the difficulty of achieving true consensus in a permissionless system.