Check the logs.
At 6:34 a.m. UTC on Aug. 9, Bitcoin's dominant proof-of-work chain was at block 961,690. The BIP-110 enforcing branch sat at block 961,633. That is a 57-block gap. The newest block on that branch was eight hours and forty-five minutes old. Not stale. Not delayed. Dead.
Miners produced 59 consecutive blocks inside the mandatory-signaling window. Zero of those 59 carried version bit 4. The enforcing chain answered with two blocks, both attributed to OCEAN, both carrying the required signal. Then silence. No further blocks. No catch-up. No hash rate migration.
I don't care about the Twitter war between BIP-110 supporters and the neutrality crowd. I care about consensus. The consensus is clear: no one is mining BIP-110. This is not a disagreement. This is a miner boycott executed through the cheapest possible mechanism: indifference.
Let's unpack what actually happened, why this "split" is not a fork, and why a silent miner boycott is the closest thing to an economic veto that Bitcoin's proof-of-work system can produce. Then I'll tell you what to do with your node, your exchange account, and your portfolio.
What BIP-110 Actually Is
BIP-110 is a proposed temporary soft fork that restricts several methods of placing arbitrary data in Bitcoin transactions. It wants to keep Bitcoin transactions focused on money and limit the use of blocks as cheap storage. The exact restrictions matter less than the deployment mechanics.
The proposal uses a 55% threshold. It requires 1,109 of 2,016 blocks to signal support. The mandatory-signaling window runs from height 961,632 through 963,647. For nodes enforcing the proposal, blocks without version bit 4 are not valid during this window. That is what "mandatory" means. It is mandatory for enforcers, not for miners.
Miner signaling data from BGeometrics shows 0.42% support since May 1. That is not a groundswell. That is background noise. In a 2,016-block window, a 0.42% signal rate would produce roughly eight or nine blocks. The proposal needs 1,109. The gap is not a matter of persuasion. It is a matter of three orders of magnitude.
Under BIP-110's state machine, a compliant enforcing chain that reaches height 963,648 enters LOCKED_IN. The proposed restrictions become ACTIVE only if that chain later reaches height 965,664, one retarget period after lock-in. The current split is happening during mandatory signaling. The actual transaction restrictions are two stages away. BIP-110 is not active. It is not locked in. It is barely started.
How We Got Here
The fight did not appear overnight. In March, a sudden wave of BIP-110 signaling nodes may have inflated visible support. Jameson Lopp said it may have been one actor posing as thousands. That should have been the first warning. Real support does not need to wear a mask.
By June, Bitcoin was less than 10,000 blocks away from what analysts called its most contentious fork fight in years. BIP-110 supporters wanted the blockchain to stay focused on money. Critics warned that filtering valid transactions would weaken Bitcoin's neutrality. The debate was real. The votes were not.
In July, Farside's alerts made the August deadline harder for exchanges, wallets, pools, and node operators to ignore. The lock-in window was coming. The exchanges had time to prepare. The miners had time to signal. The result of that prep time: zero signals out of 59 blocks.
The Deployment Math Is Brutal
Let's talk about the 59 blocks.
The divergence began at height 961,632, when enforcing nodes started rejecting blocks that did not set version bit 4. A review of the dominant chain's first 59 block headers in the window found zero bit-4 signals.
Fifty-nine blocks. Zero signals. That is not a slow start. That is a unanimous negative.
The BIP-110 enforcing branch produced two blocks, at heights 961,632 and 961,633. Both were attributed to OCEAN. Both carried bit 4. By the 6:34 a.m. UTC snapshot, the branch had produced no further blocks. For enforcing nodes, this is a consensus split. Bitcoin's dominant proof-of-work chain continued advancing, leaving the two-block branch isolated.
Let's do the arithmetic. The window has 2,016 blocks. Fifty-nine have passed. One thousand nine hundred fifty-seven remain. BIP-110 needs 1,109 of those remaining blocks to signal. That is 56.7%. The current in-window signal rate is zero percent. The two OCEAN blocks are not a trend. They are a statistical accident.
At the rate the enforcing branch produced blocks, roughly one block every four and a half hours, it would take more than two hundred days to produce 1,109 blocks. The window closes after about fourteen days. The math is not close. The math is over.
Who Is Mining What
Blocks attributed to Foundry, F2Pool, AntPool, ViaBTC, and MARA all appeared on the dominant branch during the 59-block sample. No major pool switched after the window opened. Explorer pool attribution is coinbase-based, so it does not formally establish policy. But it creates a map. The map has one pin on the enforcing side: OCEAN. Every other major pin is on the dominant chain.
This is not a 51% attack. It is not a malicious reorg. It is the exact opposite. Miners are not fighting BIP-110. They are ignoring it. They are producing blocks with no version bit 4, and the network moves forward. The enforcing branch is not being attacked. It is being starved.
A soft fork requires active signaling to activate. By refusing to signal, miners exercise a veto that does not require a single competing block. The silence is the signal. The absence of bit 4 in 59 headers is louder than any manifesto.
The State Machine Doesn't Care
Smart contracts don't have feelings. They have state transitions. BIP-110's state machine is programmed to move from mandatory signaling to LOCKED_IN at height 963,648, then to ACTIVE at height 965,664. Right now, the enforcer's state machine is running on a chain that is 57 blocks behind and growing.
A state machine that stops receiving new blocks is not a state machine. It is a snapshot. The enforcing branch's latest block was eight hours and forty-five minutes old at the snapshot. At Bitcoin's 10-minute average, that is more than 50 missed blocks. The branch is not consolidating. It is expiring.
The dominant chain, meanwhile, is producing blocks normally. Coinbase and Kraken reported Bitcoin-related systems operating normally. That is a bounded check. It means their centralized systems are synced to whatever chain they recognize. It does not mean their nodes enforce BIP-110. It does not mean wallets, merchants, or self-hosted nodes are safe. Those remain outside the sample.
The Silent Boycott Is Not a Bug
Here is the insight most coverage misses.
Miners don't have to attack BIP-110. They don't have to run a counter-campaign. They don't have to coordinate a public statement. The deployment design requires active approval from miners. Doing nothing is enough to kill it. A minority can enforce a rule on itself forever. But a soft fork is a social contract. The contract requires the miner majority to carry the change.
The silent boycott is the purest form of miner veto. It is not a war. It is a cold shoulder. And it is brutally effective.
Code is law, but human greed is the bug. Miners don't signal out of ideology. They signal when the incentive makes sense. BIP-110 adds validation rules. It restricts transaction data. It creates a risk of confusing exchanges and node operators. It has no obvious revenue upside for miners. So they vote with their hash rate. The vote is zero.
This is not a failure of governance. This is governance working. Bitcoin's deployment mechanism is designed to make controversial changes difficult. BIP-110 is difficult. The mechanism is doing its job.
The Retail Trap
This is where the market gets stupid.
Retail sees "Bitcoin split into two chains" and immediately thinks there are two Bitcoins. They check exchanges for a new ticker. They search Twitter for "BIP-110 fork." They do not check version bits. They do not check block height. They do not check whether the "fork" has any hash rate.
Smart money watches hash rate. Smart money watches the order flow. And the order flow says one pool, two blocks, zero continued production. There is no second Bitcoin. There is a failed deployment.
The enforcing branch is not an underdog fighting a corrupt establishment. It is a self-selected minority that decided to reject blocks without bit 4. The rest of the network simply kept mining. The enforcing branch's "defiance" produced two blocks and then stopped. That is not a fork. That is a fizzle.
I have seen this pattern before. In 2020, I watched DeFi protocols split over emission schedules. The ones without liquidity died within weeks. In 2022, I watched Terra's "alternative" continue printing blocks while the withdrawal queue drained. The blockchain kept producing, but the exit side was already gone. The block height lags the truth. By the time the chain stops, the price is already gone.
I don't say that to be dramatic. I say it because I've watched too many projects confuse enforcement with support. Enforcement on a minority branch is not support. It is self-selection. And self-selection cannot survive a 57-block deficit.
The Exchange Status Feeds Are a Red Herring
Coinbase and Kraken both reported normal Bitcoin operations. That is good for their customers. It is not good for BIP-110.
The status feeds are a bounded check. They tell you that the exchange's database is moving. They do not tell you that the exchange is running BIP-110 enforcement. They do not tell you that merchants, wallets, or self-hosted nodes are aligned. The feeds are quiet because the exchanges are not on the enforcing branch. They are on the dominant chain, waiting for the drama to end.
If an exchange had switched to the enforcing branch, we would have seen a status page with a warning, a delay, or a maintenance message. Instead, we see normal. Normal means the dominant chain is the only chain that matters for liquidity.
The Node Operator Dilemma
If you are running a self-hosted node with BIP-110 enforcement, you are not running a testnet. You are running a minority branch that will not reach LOCKED_IN. Your wallet has not received a new block in almost nine hours. That is not a sync error. That is a consensus split.
You need to decide whether your principle is worth an orphan. My answer is no.
I spent 2017 auditing ICO contracts instead of buying whitepapers. I learned to trust code over claims. But I also learned that a contract no one calls is just a text file. BIP-110's enforcing branch is a text file with no miner. Smart contracts don't care about your conviction. They care about the next block. The next block is not coming for BIP-110 at this hash rate.
What Could Change the Outcome
Could BIP-110 still activate? Yes, but only if the numbers change. Let's be precise about what would have to happen.
A major pool would need to start setting version bit 4. Foundry, F2Pool, AntPool, ViaBTC, or MARA would need to flip. That would put the signal rate above 55% and make the window competitive. But there is zero evidence of that. No major pool switched after the window opened. The first 59 blocks show zero signals. The only bit-4 blocks are OCEAN's two. One pool cannot carry a 55% deployment.
Exchanges could also change the balance. If major exchanges announced they would follow the enforcing chain, miners might reconsider. But Coinbase and Kraken status feeds showed normal operation. No exchange is enforcing BIP-110. No exchange is hiding the 57-block gap behind a status page. The market is not choosing the minority branch.
The enforcing nodes themselves could choose to abandon the branch. If a meaningful number of node operators deactivate BIP-110 enforcement, the split disappears instantly. The dominant chain becomes the only chain. The enforcing branch becomes a memory. That is the most likely ending.
The Two Stages Nobody Talks About
Most coverage treats the split as if the restrictions are already active. They are not.
The enforcing chain would need to reach height 963,648 to enter LOCKED_IN. From the current enforcing branch height of 961,633, that is 2,015 blocks. At OCEAN's observed production rate, that would take more than a year. The window will close in about thirteen days.
Even if the enforcing branch somehow reached 963,648, the restrictions would not become ACTIVE until height 965,664. That is a second retarget period. The proposal has to survive two full retargets. It will not survive one.
The split is happening during mandatory signaling. The transaction restrictions are two stages away. That means the enforcers are not defending an active rule change. They are defending a request for approval. The request is being denied by every miner except OCEAN.
The Traders' Playbook
Let's get tactical. I run a copy trading community. My members ask the same question every time a headline says "split" or "fork." Should we buy the new chain? Should we short the old one?
The answer is no. You do not trade a chain that is 57 blocks behind and two stages from activation. There is no liquid market for an orphan. You cannot short a chain that has no market. You sit on the dominant chain. You treat BIP-110 as a tail risk that is already dead.
If you are long Bitcoin, you are long the dominant chain. The dominant chain is not forking. It has 961,690 blocks. The enforcing branch has 961,633. The price you see on your exchange is the price of the chain the exchange recognizes. That chain is not BIP-110.
If you are holding a wallet on the enforcing branch, the balance is real on that branch. But that branch is not producing blocks. It is not producing security. It is not producing liquidity. It is producing a lesson. History does not reward lessons bought at full price.
What I'm Watching Next
I watch the blockchain, not the ticker. The ticker still shows one Bitcoin price. The blockchain shows two realities: one chain with 961,690 blocks and one chain with 961,633. The market cannot price an orphan. It simply does not care.
The next thing I'm watching is the next 100 blocks on the dominant chain. If they also produce zero bit-4 signals, the window is effectively dead. If a major pool flips, I will change my view. Until then, the evidence is unidirectional.
I'm also watching the enforcing branch's orphan risk. A chain that falls 57 blocks behind on Bitcoin's difficulty schedule is not just slow. It is on a different difficulty trajectory. As the dominant chain's difficulty adjusts, the enforcing branch's difficulty will not adjust accordingly. It will become even harder for the minority to catch up. The gap will widen. The branch will become a historical footnote.
The Cold-Blooded Takeaway
Here is where I land.
BIP-110 will not activate through this window. The signal count is zero for 59. The required count is 1,109 of 2,016. The enforcing branch is a two-block orphan with no active production. The proposal is two stages away from activation and cannot reach the first stage.
Do not buy a narrative. Do not run an enforcing node unless you enjoy being isolated. Do not ask whether the exchange supports the "fork." Ask whether the fork is mining. The answer is no.
This is not a prediction. It is arithmetic. The window has 1,957 blocks left. The dominant chain will mine nearly all of them. The enforcing branch will mine none, unless a major pool flips. There is no sign of that.
The silent miner boycott has already halted the enforcing BIP-110 chain. The branch just doesn't know it yet. I don't trade beliefs. I trade blocks.
I watch the blockchain, not the ticker.
