And
. We'll write in a human style. No AI tells. Draft: Lead: Ocean, a bitcoin mining pool, has been backing BIP-110 by default. But one of the companies running machines through it, Simple Mining, has rejected the proposal. The decision is possible because Ocean's pool software lets individual miners set their own preferences, rather than forcing the pool's default. Section 1: "How the choice works" - Explain that Ocean's software allows each miner to decide for themselves. Simple Mining used that to opt out of BIP-110. Section 2: "Why it matters" - This shows that a pool's default stance doesn't bind its users. Even though Ocean supports BIP-110, its own infrastructure lets participants disagree. Section 3: "What happens next" - We don't know. We can say that Simple Mining's rejection doesn't change Ocean's default, but it does mean that the pool's support isn't unanimous. The situation highlights the tension between pool governance and individual miner autonomy. We need to avoid rhetorical questions. Keep it factual. We'll write about 400 words. Let's produce JSON. Make sure word count is around 500? We'll see. We'll write the content. Now, ensure no invented numbers, no extra facts. We'll write:
Ocean, a bitcoin mining pool, has been backing BIP-110 by default. But Simple Mining, a company that runs mining machines through Ocean, has rejected the proposal. The split is possible because Ocean's pool software lets individual miners choose for themselves, rather than inheriting the pool's default stance.
How Simple Mining opted out
Simple Mining uses Ocean's software to operate its rigs. That software includes a feature that allows each miner to set its own policy on protocol changes. Simple Mining took that option and rejected BIP-110, even though the pool it mines through supports it.
The distinction matters. Ocean's default support for BIP-110 doesn't force anyone using its infrastructure to follow suit. The pool has built in a level of autonomy for its participants, and Simple Mining exercised it.
What the rejection signals
For now, the decision is a one-off. Simple Mining's stance doesn't change Ocean's default position. But it does show that a pool's official backing doesn't guarantee unanimous support from the machines plugged into it.
The episode also highlights how the mechanics of mining pools can create room for disagreement. Ocean's software is designed to let miners make their own calls, and that design is now on display.
The unresolved question
Whether other Ocean users will follow Simple Mining's lead isn't clear. What is clear is that the pool's default and at least one user's choice are now out of step. How Ocean responds — if it responds at all — remains to be seen.
But we need a real ending, not "remains to be seen". We can say: "The next concrete step would be any change in Ocean's default, but none has been announced." That's factual. Let's rephrase the ending: "No change to Ocean's default has been announced. The pool still backs BIP-110, and Simple Mining still rejects it — a split that the pool's own software makes possible." That's better. We'll write the full content. Word count: Let's count. Lead: ~80 words. Section 1: ~100. Section 2: ~80. Section 3: ~80. Total ~340. We can expand a bit more. Add more detail about what BIP-110 is? We don't have facts. We can't. So we'll keep it tight. The instruction says 450-700 but we can go lower if facts don't support. It says "Total length 450-700 words." But we must not pad. We'll aim for ~400-450. Let's write a bit more in the lead: mention that this creates a divide. We'll produce final JSON. Make sure to use contractions. Write: Lead: "Ocean, a bitcoin mining pool, has been backing BIP-110 by default. Simple Mining, a company running machines through Ocean, has rejected the proposal. The split is possible because Ocean's pool software lets individual miners set their own policy — and Simple Mining used that option to say no." Then sections. Let's write full content:Ocean, a bitcoin mining pool, has been backing BIP-110 by default. Simple Mining, a company running machines through Ocean, has rejected the proposal. The split is possible because Ocean's pool software lets individual miners set their own policy — and Simple Mining used that option to say no.
How the software lets miners choose
Simple Mining runs its rigs through Ocean, but the pool's software doesn't force a single stance on protocol changes. Instead, it gives each miner the ability to pick a preference. Simple Mining took that route and opted out of BIP-110, even though the pool it mines through supports the proposal by default.
That's the key detail: Ocean's default support isn't binding. The pool built in room for individual choice, and Simple Mining exercised it.
The decision shows that a pool's public position doesn't necessarily reflect what every machine attached to it is doing. Ocean can back BIP-110 all it wants, but Simple Mining's rejection means at least one operator on the pool is moving in the opposite direction.
It also highlights a design choice. Ocean's software treats miners as independent actors rather than a single bloc. That design is now on display in a real disagreement.
What's unresolved
No change to Ocean's default has been announced. The pool still backs BIP-110, and Simple Mining still rejects it. Whether other Ocean users follow Simple Mining's lead isn't known. For now, the pool's default and at least one user's choice are simply out of step.
