What to Know
- Simple Mining mined Bitcoin block 961,634 on the main chain without signaling support for BIP-110.
- The miner was using Ocean’s DATUM protocol, which lets individual miners decide how their own blocks are built while still mining through the pool.
- Ocean had switched miners to signal for BIP-110 by default in July, making Simple Mining’s opposite choice notable.
- BIP-110 sought to restrict non-financial data in Bitcoin transactions for a year.
- Support for BIP-110 peaked at about 2.6% of hashrate, far below the 55% threshold the proposal sought.
- BIP-110 nodes began rejecting non-signaling blocks at height 961,632.
- The BIP-110 branch produced blocks 961,632 and 961,633 before stalling.
- By Monday, a live monitor showed Bitcoin’s main chain at 961,725, placing the BIP-110 branch more than 200 blocks behind.
Miner-Level Choice Takes Center Stage in BIP-110 Split
A Bitcoin miner’s decision to reject BIP-110 has drawn attention to the practical mechanics of mining pool governance, miner autonomy, and how much real-world support a proposed rule change can command when hashpower is asked to take a side. Simple Mining said it mined block 961,634 on Bitcoin’s main chain without signaling support for BIP-110, even though it was operating through Ocean, a mining pool that had been backing the proposal by default.
The episode matters because mining pools often appear to speak for the computing power connected to them. In practice, however, the arrangement can be more nuanced. Pools coordinate hashrate, distribute payouts, and typically handle block construction, but the underlying machines are owned and operated by individual miners. In this case, Simple Mining used Ocean’s DATUM protocol to make its own decision about the block it produced.
That decision went against BIP-110. Simple Mining said its block did not include the BIP-110 signal, and that the chain extended on its block. The company framed the move as a hashrate-based rejection of the proposal, saying that hashrate is a vote that cannot be faked and that it did not consider the proposal worth following.
What BIP-110 Attempted to Change
BIP-110, short for Bitcoin Improvement Proposal-110, was designed to stop users from storing pictures, text, and other non-financial data inside Bitcoin transactions for a year. The proposal sat within a broader and long-running debate over what Bitcoin block space should be used for, how much discretion miners should exercise when selecting transactions, and whether non-financial data should be treated differently from payment-related activity.
Supporters of restrictions on non-financial data generally argue that Bitcoin’s block space should prioritize monetary transfers and settlement activity. Critics of such restrictions often argue that Bitcoin’s rules should remain neutral, that valid transactions should not be filtered based on subjective categories, and that attempts to enforce content preferences can create fragmentation risks.
BIP-110 did not achieve the level of mining support it sought. Hashrate support peaked at about 2.6%, far below the 55% threshold the proposal targeted. That gap became decisive once BIP-110 nodes began rejecting blocks that did not carry the proposal’s signal at height 961,632. With only a small minority of hashrate aligned behind the new rule set, the branch quickly fell behind Bitcoin’s main chain.
Ocean’s Role and Why the Outcome Looked Contradictory
Ocean had switched miners to signal for BIP-110 by default in July and accounted for nearly all of the proposal’s small amount of mining support before the split. That made Simple Mining’s rejection especially notable, because the miner was still operating through Ocean while making the opposite choice.
The reason lies in DATUM. The protocol allows individual miners to build their own blocks using their own Bitcoin software while still contributing hashrate through Ocean and sharing in the pool’s payouts. In a typical pool structure, the pool usually decides which transactions go into a block and which software signals the block carries. DATUM shifts that decision back toward the individual miner.
That structure helps explain why Ocean appeared on both sides of the weekend split. A miner using Ocean produced the first block accepted by the BIP-110 branch on Saturday. Simple Mining then used the same pool infrastructure to produce a block for the dominant Bitcoin chain without signaling for BIP-110. The contrast showed that a pool’s default setting does not necessarily translate into uniform miner behavior when miners have tools that let them construct blocks independently.
The Fork Stalls as Main Chain Advances
BIP-110 nodes began rejecting non-signaling blocks at height 961,632. The BIP-110 branch produced blocks 961,632 and 961,633 before stalling. Meanwhile, Bitcoin’s main chain continued advancing, with blocks being produced roughly every ten minutes.
By Monday, a live monitor showed the main chain at 961,725. That placed the BIP-110 branch more than 200 blocks behind. In Bitcoin, chain progress is not merely symbolic. The branch with overwhelming proof-of-work tends to retain economic relevance because users, exchanges, wallets, businesses, and miners generally follow the chain with the strongest accumulated work and deepest liquidity.
The widening gap underscored the central problem facing the BIP-110 branch: without sufficient hashrate, a chain that rejects the majority of blocks can quickly isolate itself. Once that happens, it becomes increasingly difficult for the minority branch to maintain momentum, attract additional miners, or present itself as the economically dominant version of Bitcoin.
Why the 2.6% Hashrate Figure Mattered
The peak support figure of about 2.6% was central to how market participants interpreted the event. BIP-110 had sought 55% support, a level that would have signaled substantially broader miner alignment. Instead, the proposal entered its activation moment with only a small fraction of hashrate behind it.
In proof-of-work systems, miner support is measured through the allocation of computing power. While social debate, software development, and user preference can shape outcomes, hashrate remains a direct signal of whether miners are willing to enforce a particular rule set. When most miners continue producing blocks under existing consensus rules, a minority branch that rejects those blocks must survive with the limited security and block production capacity it can command.
Simple Mining’s block made that reality more visible. It was not just a miner declining to signal; it was a miner declining to signal while using a pool that had backed the proposal by default. That distinction sharpened the message that pool-level defaults and individual miner choices are not always the same thing.
Mining Pools, Defaults, and Miner Autonomy
Mining pools exist because solo mining is highly unpredictable for most operators. By combining hashrate, miners can receive more regular payouts rather than waiting for their own machines to find a block independently. In exchange, they often accept that the pool manages important operational choices, including block templates and signaling preferences.
DATUM changes that relationship by giving miners more control over block construction while preserving access to pooled rewards. For some market participants, that model is important because it reduces the concentration of decision-making power in pool operators. If miners can decide which transactions to include and which proposals to signal for, the pool becomes more of a payout coordination layer and less of a central policy authority.
The BIP-110 split offered a live example of how that distinction works. Ocean’s default support for BIP-110 did not prevent Simple Mining from constructing a non-signaling block. The miner’s decision showed that when block-building authority is pushed back to machine operators, the apparent consensus inside a pool can fragment into miner-by-miner choices.
Broader Implications for Bitcoin Governance
Bitcoin governance often plays out through a combination of software rules, miner behavior, node operation, market liquidity, and user preference. No single group controls the network in isolation. Developers can propose changes, nodes can enforce software rules, miners can decide where to point hashrate, and economic actors can decide which chain to treat as Bitcoin.
The BIP-110 episode reinforced that proposals requiring miner enforcement face a high practical bar. Even a pool-level default does not guarantee durable support if individual miners can override the setting or choose competing software. It also showed how rapidly a minority fork can lose relevance if it cannot attract enough hashrate to keep producing blocks at a competitive pace.
For Bitcoin watchers, the event may also strengthen interest in decentralized block construction. Tools that allow miners to make independent decisions can reduce the appearance that mining pools act as monolithic voting blocs. At the same time, they can make governance outcomes more complex, because visible pool signaling may not fully represent the intent of every miner connected to the pool.
Market Reaction Remains Focused on Network Continuity
From a network perspective, the main Bitcoin chain continued to advance while the BIP-110 branch stalled. That continuity is important for users and market infrastructure because it means the dominant chain kept processing blocks despite the dispute. The fact that the main chain moved more than 200 blocks ahead by Monday indicated that the attempted rule change had not disrupted the broader network’s forward progress.
Some chart watchers and protocol-focused traders may continue to monitor whether any additional hashrate moves toward the stalled branch, but the early evidence pointed to limited miner appetite for BIP-110. With support having peaked at about 2.6%, the proposal remained far from the 55% threshold it sought. Simple Mining’s public rejection added another visible marker that the dominant mining path remained with Bitcoin’s main chain.
For FXCOINZ readers, the key takeaway is that this was not only a dispute about non-financial data in transactions. It was also a test of how mining pools, individual miners, and block construction tools interact when a contentious rule proposal reaches an enforcement point. In that test, miner autonomy proved highly consequential.
Frequently Asked Questions (FAQs)
What did Simple Mining do?
Simple Mining mined Bitcoin block 961,634 on the main chain without signaling support for BIP-110, despite mining through Ocean, a pool that had backed BIP-110 by default.
What is BIP-110?
BIP-110 is short for Bitcoin Improvement Proposal-110. It sought to stop people from storing pictures, text, and other non-financial data inside Bitcoin transactions for a year.
Why was Simple Mining’s decision notable?
The decision was notable because Ocean had switched miners to signal for BIP-110 by default in July, yet Simple Mining used Ocean’s DATUM protocol to make the opposite choice.
What is DATUM?
DATUM is an Ocean protocol that lets individual miners build their own blocks using their own Bitcoin software while still contributing hashrate to Ocean and sharing in pool payouts.
How much hashrate supported BIP-110?
Support for BIP-110 peaked at about 2.6% of hashrate, far below the 55% threshold the proposal sought.
What happened at block height 961,632?
At height 961,632, BIP-110 nodes began rejecting blocks that did not carry the proposal’s signal, creating a minority branch separate from the main Bitcoin chain.
How far behind did the BIP-110 branch fall?
By Monday, a live monitor showed the main Bitcoin chain at 961,725, putting the BIP-110 branch more than 200 blocks behind.
Why do mining pools matter in this dispute?
Mining pools usually coordinate hashrate and often decide which transactions and signals go into blocks. This event showed that miner-level tools can let individual operators override pool defaults.
What is the broader significance for Bitcoin?
The broader significance is that miner autonomy and actual hashrate support remain crucial in Bitcoin governance, especially when a proposal attempts to change transaction policy or split from the dominant chain.
Photo by Bastian Riccardi on Pexels