BIP-110 CHAIN SPLIT — BLOCK 961,632 REJECTED. THE FORK HAPPENED. BITCOIN CONTINUES NORMALLY. OCEAN’S DATUM PROTOCOL PROVED MINER SOVEREIGNTY.
UPDATE 4:00 PM ET — DATUM CHANGED THE STORY
Earlier framing implied Ocean the pool defected back to the main chain when block 961,634 was mined outside BIP-110. That is not what happened. Simple Mining (@simpleminingio), an Ocean pool customer, mined block 961,634 using Ocean’s DATUM protocol — Ocean’s own infrastructure that lets individual miners build their own block templates independently of what the pool operators want. Ocean’s operators supported BIP-110. Ocean’s own DATUM protocol let their customers reject it. That distinction matters. This is not a pool defection story. This is a miner-sovereignty story — and the sovereignty proof runs through Ocean’s own infrastructure.
● TRACK THE FORK LIVE
TONE VAYS LIVE COMMENTARY ON X →
BIP110.ORG PROPOSAL-SIDE DASHBOARD →
FORKWATCH.TV NEUTRAL CHAIN-TIP TRACKER →
Commentary + proposal-side data + neutral observer. Both frames of the same block-height event.
"BIP-110 nodes just forked off the main chain after rejecting a non-signaling block at height 961,632."
— TFTC (@TFTC21) · 12:40 PM ET · Sat Aug 8, 2026
— TFTC (@TFTC21) · 12:40 PM ET · Sat Aug 8, 2026
At block height 961,632 — the mandatory-rejection window opened at exactly this height per the BIP-110 activation logic — a non-signaling block was produced by a miner outside the 2.6% signaling minority. BIP-110-signaling nodes rejected it. The BIP-110 minority chain diverged from the Bitcoin main chain. Tone Vays live-streamed the moment; TFTC confirmed on X four minutes later. **The fork happened. The main chain kept clearing blocks.**
THE ARC CLOSES
Tuesday 11 AM ET — Saylor put the block math on the tape: 610 blocks to the mandate window, 2.70% signaling, "backers should stand down." Friday overnight — our HH story called the mandate opening at 2.59% with 207 blocks to go. Saturday 4:50 AM ET — Saylor's final verdict: "BIP-110 will stall or fork into irrelevance while Bitcoin continues normally." Saturday 12:40 PM ET — the fork happened at block 961,632. Every prediction landed. The block math held.
The fizzle is not a failure of the network. It is the network working exactly as designed. A minority proposal without broad miner support cannot force a chain state on the majority. The signaling window was the demonstration; the rejection at 961,632 is the outcome. BIP-110 nodes are now on a separate chain that will either reorganize back to the main chain (if the minority ever wants to rejoin) or continue as an irrelevant minority chain (if they don’t). The main chain does not need to acknowledge the fork existed to keep clearing blocks.
The four-character read. The Technologist: the network’s consensus mechanism is operating exactly per the specification — miners vote with hashrate, minority proposals require majority signaling to activate, absent that they fork into a minority chain that lacks hashrate weight. This is the mechanism doing its job. The Fundamentalist: a monetary network that can be forked at will by any minority is not sound money. A monetary network that resists minority-driven state changes is. The fizzle is the property, not the bug. The Capitalist: Saylor called it with block math on Tuesday and again this morning; the tape confirmed. The wrapper class needed to know that protocol governance would not create a discontinuity risk before the September earnings cycle. It did not. The Maximalist: the sovereignty class holds the same coins on the same chain that has been running since 2009. Nothing about the fork changes what your node validates or what your keys sign.
The Counter-Voice frame that has been running "August fork war" panic since July has 0 blocks left to be wrong about. The fork happened. The main chain did not blink. The market did not blink. The mining hashrate distribution did not blink. Bitcoin continues normally.
DATUM — THE DEEPER STORY
Ocean’s DATUM protocol (Decentralized Alternative Templates for Universal Mining) lets individual mining customers construct their own block templates rather than accepting whatever the pool operators would build. When Simple Mining rejected BIP-110 and mined 961,634 on the main chain, they did it through Ocean’s protocol — the same pool whose operators support BIP-110. This is the actual decentralization story: mining sovereignty at the individual-miner level, not just at the pool level. Simple Mining’s own post-fork read: "Ocean pool does indeed give sovereignty back to miners. BIP-110 failing just showed Bitcoin mining can be decentralized." When the pool operators wanted one outcome and the pool’s customers wanted another, DATUM was the mechanism that let the customers win. That is the pattern the operator class should notice: the mining layer’s decentralization is now tooling-level, not just pool-count-level.
THE REFRAME ATTEMPT — DASHJR CALLS THE MAIN CHAIN "COUNTERFEIT"
At 2:35 PM ET Saturday, Luke Dashjr posted a "PSA" claiming that anyone running Bitcoin Knots without the BIP-110 enforcement upgrade is "now vulnerable to double-spending attacks aided by @FoundryServices and @AntPoolofficial" and told followers to upgrade immediately or risk "accepting counterfeit bitcoins." 26.9K views. The X community note landed underneath the post in real time: "Bitcoin Knots implementation changes the consensus rules and forked off the main chain. The term 'counterfeit bitcoins' is intentionally misleading." The community-note fact-check is doing the operator-class read for us: the main chain, mined by 97%+ of hashrate and settling every economically active BTC transaction, is not counterfeit. Foundry and AntPool did not aid an attack. They mined normal Bitcoin blocks. What Dashjr is running is the standard playbook of a governance-vote loser trying to relitigate through rhetorical labeling — call the majority "counterfeit," accuse the pools that beat you of coordinated attack, weaponize double-spend FUD to drive last-minute upgrades. It doesn't survive the community note. The tape sorted this already.
THE VANGUARD STANDS DOWN — ROUGHNECKS QUITS
At 8:56 PM ET Saturday, roughly eight hours after the fork activated, Roughnecks — the mining pool that had been the loudest champion of BIP-110/Knots — posted a public exit: "We had a team meeting and made the difficult decision to stop mining operations under the name Roughnecks… Anyone who is mining on the BIP110 chain under the current algorithm is advised to stop until further notice." They framed it as escalation rather than defeat — language that reads as pre-positioning for a proof-of-work hard fork, the contingency Chris Guida rebased onto Knots earlier this year in case BIP-110 signaling failed. The BIP-110 chain's most committed pool is not just standing down; it is telling other BIP-110 miners to stand down with them. That is the honest read of a chain that cannot sustain itself economically, delivered by the operators who tried the hardest. We covered Roughnecks last week when they disabled RBF on their node to defend Coldcard rescue transactions from front-running — a genuinely operator-grade act of sovereignty defense. Tonight they made a second operator-grade call: recognizing when the ground is no longer there.
"Blip 110 minutes. Glad that’s over. Back to business."
— Mike Alfred (@mikealfred) · 7:50 PM ET · Sat Aug 8, 2026
— Mike Alfred (@mikealfred) · 7:50 PM ET · Sat Aug 8, 2026
The fizzle was quantified.
The fork happened.
Bitcoin continues normally.
The fork happened.
Bitcoin continues normally.
@TFTC21 · 12:40 PM ET Sat Aug 8, 2026 · block 961,632 rejection confirmed
TONE VAYS LIVE STREAM ON X →
@ToneVays · 12:36 PM ET · "BIP110 (aka Knots) Chain Split — Watch the Train Wreck Live!"
MORE ON THE BIP-110 + MINER SOVEREIGNTY ARC
SAYLOR PUTS THE BLOCK MATH ON THE TAPE — BIP-110 STALLS OR FORKS INTO IRRELEVANCE.
BIP-110 MANDATE OPENS AT 2.59% — 207 BLOCKS TO A FORK CLOCK NOBODY ORDERED.
ADAM BACK — "THE NETWORK IS NOT FIRING ITS MINERS."
ALDEN — BIP-110 MOSTLY REARRANGES SPAM, RAISES MINORITY-FORK RISK.