They promised you "full block-template control." Then they pointed your hardware at a dead chain for 18 hours — and called it a mistake.
OCEAN, the mining pool that built its entire brand on giving individual miners control over their own blocks, just got caught redirecting some users’ hashrate to the failed BIP-110 minority fork. Without consent. For roughly 18 hours.
Here’s what happened. When BIP-110’s mandatory enforcement triggered at block 961,632 on August 9, the breakaway chain mined exactly two blocks — 961,632 and 961,633 — and went silent. The main chain raced ahead 48 blocks within a day. It was dead on arrival: the fork inherited Bitcoin’s full mining difficulty with almost no hashpower, meaning its next difficulty adjustment was roughly 350 days away. Michael Saylor put it best: "Consensus is earned, not declared." About 99.85% of Bitcoin’s hashpower never left the main chain.
But OCEAN had a problem. Miners who believed they were using non-BIP-110 Stratum templates found their hardware mining blocks on a separate fork instead. OCEAN acknowledged a "configuration error" directed a portion of its hashrate to the BIP-110 chain for roughly 18 hours — and has now committed to compensating affected miners about 0.3 BTC each, based on what they would have earned mining the main chain.
Read that again. The pool whose entire pitch is "returning full block-template control to individual miners" silently decided which chain your hardware pointed at — and only apologized after it got caught.
The mining community isn’t buying it. One X user called it a hashrate "hijack" and demanded those responsible be removed. Blockstream CEO Adam Back called the move unacceptable and demanded the financial losses be deducted directly from OCEAN co-founder Luke Dashjr’s salary — the same Dashjr who just lost his BIP Editor seat and stepped back from OCEAN leadership. Miners are now calling for the ousting of OCEAN leadership entirely. In the fallout, OCEAN’s reported hashrate collapsed by more than 96%.
And here’s the uncomfortable part for every miner reading this: your hardware is yours, but your pool is a custodian. The same trust problem that makes exchanges dangerous applies to pools — they decide which transactions your machines include and which chain they support. "Not your keys, not your coins" apparently extends to "not your pool, not your hash."
Bitcoin shrugged off the fork. It always does. But this should scare you more than the fork itself: the people you trusted with your hashpower decided your votes for you — then told you it was a bug.
If a pool can point your hardware at a dead fork for 18 hours and call it a "configuration error," what else can it decide for you without asking?
Hold your own keys. Mine your own blocks if you can. And if you’re done trusting middlemen with your money — get a hardware wallet with the LOVEISBITCOIN coupon at loveisbitcoin.com/bull. No custodians. No "configuration errors." Just you and the chain.
Source: NostrMag / BeInCrypto via Yahoo Finance
NOT YOUR POOL, NOT YOUR HASH — OCEAN JUST RENTED YOUR RIG TO A DEAD FORK FOR 18 HOURS
