Bitcoin Miner Defied BIP‑110 While Operating Within a Supporting Pool

In the ever‑evolving landscape of Bitcoin mining, the relationship between mining pools and the individual operators that connect to them can sometimes lead to unexpected technical decisions. One recent example involves a miner that deliberately declined to adopt Bitcoin Improvement Proposal 110 (BIP‑110) even though the pool it was attached to—Ocean—had BIP‑110 enabled by default. To understand why this occurred, and what it means for the broader ecosystem, we need to explore the roles of BIP‑110, the design of Ocean’s pool software, and the autonomy granted to miners through that software.

### What is BIP‑110? BIP‑110, formally titled “Bitcoin Core RPC Calls for Mining,” was introduced to standardize the way mining software interacts with Bitcoin Core nodes. The proposal adds a set of Remote Procedure Call (RPC) commands that allow miners to retrieve block templates, submit completed blocks, and obtain network‑wide information in a more efficient and secure manner. By using these RPC calls, miners can reduce latency, improve block propagation speed, and ultimately increase the probability of earning block rewards.

The proposal has been widely praised for its potential to streamline mining operations and for encouraging a more uniform interface across different mining software implementations. ### Ocean’s Default Support for BIP‑110 Ocean, a prominent mining pool, decided early on to adopt BIP‑110 as its default configuration.

This decision was driven by several factors: 1. **Performance Gains**: By leveraging the new RPC calls, Ocean could deliver block templates to its participants faster than pools still using older protocols. 2.

**Security Improvements**: The standardized calls reduce the attack surface that can be exploited by malicious actors attempting to inject malformed data. 3. **Future‑Proofing**: As more miners upgrade to software that understands BIP‑110, Ocean’s early adoption positions it as a forward‑looking service provider.

To implement this, Ocean integrated the BIP‑110 RPC endpoints into its pool software and set the feature to be active for all connected miners unless they explicitly disabled it. This approach mirrors the common practice in many technology platforms where a new feature is turned on by default, but users retain the ability to opt out if they have compatibility concerns. ### Simple Mining’s Choice to Opt Out Simple Mining is a company that operates a fleet of ASIC miners and connects them to Ocean’s pool via the pool’s client software. The software offered by Ocean includes a configuration option that allows each miner—or the operator managing multiple miners—to decide whether to use BIP‑110 or fall back to the older Stratum protocol.

This flexibility is crucial because not all mining firmware immediately supports the new RPC calls, and some operators may have custom monitoring tools that depend on legacy behavior. When Simple Mining set up its machines, the engineering team reviewed the pool’s configuration page and noted the toggle for BIP‑110.

After evaluating their own hardware’s firmware version and the compatibility of their monitoring stack, they concluded that staying with the traditional Stratum protocol would avoid potential disruptions. Consequently, they selected the “disable BIP‑110” option for all of their devices.

### Why the Decision Matters The fact that a miner can reject BIP‑110 while still participating in a pool that defaults to it highlights several important aspects of the mining ecosystem: - **Autonomy of Miners**: Even within a pooled environment, individual miners retain control over the protocols they use. This autonomy ensures that miners are not forced into a one‑size‑fits‑all solution that might not align with their operational constraints.

- **Compatibility Challenges**: New protocol upgrades often require firmware updates or software patches. If a miner’s hardware is not yet ready, forcing the upgrade could lead to downtime, reduced hash rate, or even hardware errors. - **Pool Flexibility**: By providing an opt‑out mechanism, Ocean demonstrates a commitment to inclusivity, allowing both cutting‑edge and legacy miners to coexist on the same platform.

This flexibility can broaden the pool’s appeal and increase its overall hash power. - **Potential Performance Trade‑offs**: While opting out preserves stability for Simple Mining, it may also mean they forego the latency and efficiency benefits that BIP‑110 offers. Over time, as the network becomes more competitive, such trade‑offs could influence profitability. ### Technical Details of the Opt‑Out Process The process by which Simple Mining disabled BIP‑110 is straightforward but worth outlining for clarity.

When a miner connects to Ocean, the pool’s client software initiates a handshake that includes a list of supported protocols. The miner’s configuration file contains a flag—`use_bip110 = false`—which instructs the client to advertise only the legacy Stratum protocol.

The pool’s server then routes the miner’s requests through the traditional Stratum interface, bypassing the BIP‑110 RPC endpoints entirely. This negotiation happens at the start of each session, meaning that a miner could theoretically switch back to BIP‑110 later simply by updating the flag and restarting the connection. ### Broader Implications for the Bitcoin Community The incident underscores a broader theme in the Bitcoin community: the balance between rapid innovation and maintaining backward compatibility.

BIP‑110 represents a significant technical improvement, yet its adoption cannot be forced upon every participant. By designing pools like Ocean to be configurable, developers encourage a smoother transition across the network.

Moreover, the ability for miners to make independent choices fosters a decentralized ethos, ensuring that no single entity can dictate the technical direction for all participants. ### Looking Ahead As firmware updates roll out and more mining hardware becomes BIP‑110‑compatible, we can expect a gradual shift toward universal adoption. Pools may eventually deprecate the older Stratum protocol, but until that point, the dual‑support model will likely remain.

For operators like Simple Mining, the key will be to monitor their equipment’s compatibility roadmap and weigh the benefits of enabling BIP‑110 against any operational risks. In summary, the case of a Bitcoin miner rejecting BIP‑110 while mining through a pool that supports it by default illustrates the nuanced interplay between pool policies, miner autonomy, and technological progress. Ocean’s default enablement of BIP‑110 showcases its commitment to modern standards, while Simple Mining’s opt‑out decision reflects prudent risk management and the practical realities of hardware compatibility.

This dynamic ensures that the Bitcoin mining ecosystem can evolve responsibly, accommodating both cutting‑edge improvements and the diverse needs of its participants.