Bitcoin’s BIP-110 split is widening, and the minority chain is barely moving
Bitcoin’s BIP-110 enforcement branch has stalled at two blocks while the main chain keeps advancing, leaving a widening gap and very little sign that miners are willing to back the fork in meaningful numbers.
- Enforcing branch at block 961, 633
- Main Bitcoin chain at block 961, 744
- Gap widened to 111 blocks
- No support seen in the current signaling window
- Replay risk remains a real concern
As of Aug. 9, the BIP-110 branch had reached block 961, 633 while Bitcoin’s dominant chain had moved on to 961, 744, according to the reporting and monitor data cited. That 111-block gap is not a healthy split. It is a blunt sign that the minority branch is struggling to keep up under the same mining difficulty as the rest of the network.
The timing matters. BIP-110 entered its mandatory signaling phase at block 961, 632 on Aug. 8. The first two blocks on the enforcing side were mined by Roughnecks, and OCEAN said its DATUM system was used to mine the first BIP-110 block. Since then, the branch has failed to produce a third block while the main chain has kept moving. The wider context is laid out in Bitcoin BIP-110 split widens as fork freezes at 2 blocks and Bitcoin's Splintered BIP-110 Fork Falls Behind by 18 Blocks.
For readers who do not live and breathe Bitcoin upgrade politics: BIP-110 is a temporary soft fork proposal called Reduced Data Temporary Softfork. In plain English, it tries to make certain data-heavy transaction and script forms invalid under new consensus rules for about one year, while leaving older coins spendable through grandfathering rules for pre-activation UTXOs, or unspent transaction outputs.
The proposal is not just one narrow tweak. The BIP text limits a range of data-heavy constructions, including oversized scriptPubKeys, large OP_PUSHDATA payloads, certain witness items, some Taproot annex and control-block behavior, OP_SUCCESS* usage in tapscripts, and OP_IF / OP_NOTIF execution in tapscripts. Supporters say that is a necessary cleanup job. Critics say it is a consensus-level power grab dressed up as housekeeping. For a deeper look at the risks, see Bitcoin BIP-110 Raises Replay Risk Concerns Amid Miner and Bitcoin BIP-110 Debate: Saylor Warnings of Protocol Risks Amid.
Why the fork is bogging down
A fork does not survive on hot takes or righteous posts. It survives on hash power, the computational work miners put in to find blocks. When most miners stay on the main chain, the enforcing branch is left fighting the same difficulty target with far less muscle.
At the time of the split, difficulty was 127.48 trillion. Bitcoin normally recalculates mining difficulty every 2, 016 blocks so average block times stay near 10 minutes. But a minority branch that barely attracts miners can get stuck under the same brutal setting for a very long time. If blocks are scarce, the chain cannot retarget. If it cannot retarget, the blocks stay scarce. That is the trap.
Michael Saylor said “about 99.85% of Bitcoin’s hashpower stayed with Bitcoin, ” while the fork attracted only “~0.15% of Bitcoin’s hashpower.” He also said the fork could take “~25 years” to reach its first difficulty adjustment. His broader warning is captured in Saylor Warns BIP-110 Protocol Change Could Harm Bitcoin and the more bluntly titled 110 Reasons BIP 110 Is a Bad Idea.
That is Saylor’s estimate, not a measured network law. But it does capture the basic problem: if the minority chain really has only a sliver of hash power, it is economically stranded for now.
The current-period numbers point in the same direction. The reporting says there has been zero support among 113 main-chain blocks mined since mandatory signaling began, while the previous difficulty period saw just 51 of 2, 016 blocks signal support, 2.53%. That is not momentum. That is a shrug with a timestamp. The same trend was noted in Bitcoin BIP-110 split widens as fork freezes at 2 blocks, where the fork’s stagnation was already looking ugly.
What mandatory signaling actually means
BIP-110 uses a BIP 9-style deployment process, which means miners signal support by setting a required bit in the block version field. During the mandatory signaling phase, nodes enforcing the proposal reject blocks that do not include the expected signal.
In plain terms, miners have to show their hand. If they do not, nodes running the enforcing rules toss the block out. That is why the split matters: the enforcing branch is no longer just a passive preference. It is a chain with teeth, but not much hash power behind them.
The proposal’s deployment schedule is reported as running through block 963, 647, with LOCKED_IN expected no later than 963, 648 and the reduced-data rules beginning at block 965, 664 for 52, 416 blocks, roughly one year. Those heights are part of the reported deployment path, but the practical question is more basic: will enough miners support it for the schedule to matter at all?
Supporters and critics are arguing over Bitcoin’s boundaries
Supporters of BIP-110 argue that Bitcoin should not be treated like a junk drawer for arbitrary data. Their case is simple: block space is scarce, and if non-monetary data crowds the chain, node operators pay the price. They say consensus-level restrictions help keep Bitcoin focused on money and make it harder for abusive data patterns to distort incentives.
That argument is not nonsense. Bitcoin block space is limited by design, and scarce resources invite abuse. If users and developers keep stuffing more and more non-monetary data into the chain, someone eventually gets stuck paying the bill. A useful bit of background is the broader List of bitcoin forks, which is basically a museum of “we know better” moments that did not all age well.
Critics see something uglier: a precedent. Adam Back Warns BIP-110 Could Split Bitcoin Into a Minority warned that consensus-level restrictions could damage Bitcoin’s credibility as a store of value and open the door to censorship-by-precedent. That is the real fear. Once a network starts drawing political or moral lines in consensus rules, people begin asking who gets to draw the next one.
Luke Dashjr, the Bitcoin Knots maintainer, has pushed users to upgrade and warned about vulnerability to double-spending attacks. That is his side of the fight, and it should be read as such: a participant warning, not a neutral audit. Still, the underlying point is serious. When Bitcoin splits, confusion is where users get hurt.
Replay risk is the part ordinary users should actually worry about
When two chains stay compatible enough, a transaction sent on one side can sometimes be valid on the other too. That is replay risk. It means a payment intended for one branch can be copied onto the other unless wallets, exchanges, or users take precautions.
Kevin Loaec warned about that risk for holders. The concern is not theoretical. Chain splits without built-in replay protection have a long and ugly history of causing accidental duplicate spends, wallet confusion, and a lot of frantic support tickets from people who just wanted to move their coins without starting a fire. The concern was also summarized in Bitcoin BIP-110 Raises Replay Risk Concerns Amid Miner.
The materials note that BIP-110 does not inherently provide replay protection. That is the key point. If the split persists, users cannot treat coin movement as a casual click-and-send exercise. They need to wait for guidance from wallets or exchanges, use replay-safe tools if available, and avoid blindly moving funds across both branches.
The chain is alive, but that does not mean it is healthy
The minority branch is stalled, not formally dead. More hash power could still move over later if the economics change or if miners decide the fork is worth backing. Bitcoin history has plenty of examples of people changing their minds when incentives shift.
But the current block data suggests the enforcing branch has attracted very little hash power so far. That makes its near-term survival look shaky. A chain that cannot keep pace with the main network is not just under pressure technically; it is also fighting an economic reality that does not care about ideology.
That is why the split is more than a philosophical squabble. It is a live stress test of Bitcoin’s consensus mechanics, miner incentives, and the social cost of trying to enforce new rules at the protocol level. Bitcoin does not run on slogans. It runs on proof of work, incentives, and miner behavior, not thread warfare and wishful thinking. The arguments have been laid out across several venues, including Bitcoin BIP-110 Debate: Saylor Warns of Protocol Risks Amid, while the practical fork risk has been aired in Adam Back Warns BIP-110 Could Split Bitcoin Into a Minority Fork.
Key questions and takeaways
- Is the BIP-110 fork dead or just stalled?
It is stalled, not conclusively dead. But with only two blocks on the enforcing branch and no meaningful support from the dominant chain, the economics look brutal right now. - Why is the minority chain struggling so much?
It is mining under the same difficulty as Bitcoin’s main chain without enough hash power to move efficiently. Until it attracts more miners, it is stuck fighting physics. - What does BIP-110 change?
It is a temporary soft fork that restricts several data-heavy transaction and script forms, while grandfathering pre-activation UTXOs so older coins remain spendable under the new rules. - What is the biggest risk for users?
Replay risk. If both chains remain active and compatible enough, a transaction may be valid on both sides unless wallets or exchanges add safeguards. - What is the core dispute here?
It is a fight over whether Bitcoin should enforce stricter consensus limits on certain kinds of data, or stay as neutral as possible and let fee markets sort the mess out. - What should holders do now?
Treat coin movement cautiously, wait for wallet and exchange guidance, and do not assume a chain split automatically protects you from double-spend or replay problems.
For now, the message from miners is plain enough: Bitcoin follows hash power, not talking points. BIP-110 may still have a political future. Its economic future looks a lot less certain.
