I remember the night of August 1, 2017, when Bitcoin Cash split. The air in the Paris office was thick with tension. Wallets needed splitting, exchanges scrambled, and the community fractured into two camps that would never reconcile. That was a political fork. This weekend, we’re facing something stranger: a technical fork with no clear political consensus, driven by a rule change so narrow that most users don’t even know it exists. And yet, at block 961,632, the Bitcoin network could tear in two. The countdown is 290 blocks. That’s roughly 48 hours. And the question isn’t just about code—it’s about who has the power to define what Bitcoin is.
Context: The BIP-110 Fight
BIP-110 is a soft fork proposed by pseudonymous developer Dathon Ohm. It caps the amount of arbitrary data a Bitcoin transaction can carry—a move aimed at curbing “spam” transactions that clog blockspace. The proposal is implemented in Bitcoin Knots, a smaller client maintained by Luke Dashjr, not in the dominant Bitcoin Core. The fork activates via mandatory signaling: after block 961,632, miners must set a flag called versionbit 4 in their block headers. Blocks without that flag become invalid to BIP-110 nodes.
Ohm has been blunt: “It is not recommended to run Bitcoin Core, as it will become insecure when mandatory signaling begins.” He claims that miners using Core for block templates risk producing “invalid blocks on an incoherent chain that keeps being wiped out.” Michael Saylor, the MicroStrategy executive and Bitcoin maximalist, says the opposite. He urged BIP-110’s backers to “stand down,” arguing that without major miner support, the fork will stall or die. “At 961,632, BIP-110 nodes reject non-signaling blocks. Unless major miners reverse, Bitcoin continues normally,” he wrote.
Luke Dashjr, the maintainer of Bitcoin Knots, told BeInCrypto that the outcome is settled: any miner who refuses to signal loses their block rewards. “The invalid blocks they produce serve only to mislead nodes that have not yet updated,” he said. Adam Back, CEO of Blockstream, called the proposal “a stupid idea” that “completely fails at technical consensus.”
Volatility isn’t a bug; it’s a feature. But this kind of split isn’t volatility—it’s a civil war fought with block headers. The market hates uncertainty, but it loves to dance with it. And this weekend, the dance floor is a blockchain.
Core: The Numbers Tell a Different Story
Let’s look at the data. At block 961,022 on August 4, Saylor counted 38 signaling blocks out of a total of 1,406—a rate of 2.70%. By block 961,421, the monitor logged 47 of 1,806 blocks, or 2.60%. That’s eight new signals in 392 blocks. The period rate slipped, not climbed. Early lock-in requires 1,109 signaling blocks. With only 217 blocks left in the current period, the maximum reachable total is 263. No two-week stretch since December has finished above 1.29%.
These are not just numbers; they’re a signal of miner sentiment. Miners are refusing to signal. Why? Because they don’t see the benefit. BIP-110’s own website, bip110.org, doesn’t mention critical vulnerabilities. Ohm’s claim of “critical vulnerabilities” appears only on his X posts. The project’s official pitch is about curbing spam, not security. That’s a fundamental disconnect.
Based on my experience covering miner behavior during the 2021 crackdown, I’ve seen this pattern before. Miners are rational actors. They will not stake their block rewards on a rule change that has no clear economic upside. The Bitcoin block reward after the fourth halving is already compressed. Hash power is concentrating in three major pools. The last thing miners want is a chain split that could turn their revenue into dust.
But here’s the twist: voluntary activation is already impossible. With only a day and a half left, the question is whether miners capitulate or BIP-110 nodes end up mining alone. If BIP-110 nodes hold firm, they will fork away from the main chain. The minority chain will have its own blocks, its own miners (if any), and its own version of history. The majority chain, running Bitcoin Core, will continue as if nothing happened. For users, the risk is that transactions on one chain may not be valid on the other.
In crypto, the only constant is the narrative. And right now, both sides are telling a story of victory. Ohm says the fix is in; Saylor says the fix is irrelevant. The truth is messier: the network is about to experience a stress test of its governance, not its code.
Contrarian: The Unreported Angle
Everyone is focused on the technical details—the versionbit, the lock-in threshold, the block count. But the real story is about power and identity. BIP-110 is not a technical upgrade; it’s a political statement disguised as a soft fork. The proposal’s backers are a small group of developers who believe Bitcoin Core has become too slow to adapt. They see BIP-110 as a way to force the hand of the majority. The problem is that they’re using a mechanism that requires only a minority to trigger a split.
This is the governance failure everyone is ignoring. The mandatory signaling threshold is extremely low. The versionbit 4 flag is not a consensus-critical change; it’s a signaling mechanism. But when combined with the threat of orphaned blocks, it becomes a weapon. The side that controls the nodes can declare the other side’s blocks invalid. That’s not Satoshi’s vision of “one CPU, one vote.” It’s a form of centralized control by the node-hosting minority.
I’ve seen this before in DeFi governance. During the 2020 Curve wars, small groups of token holders could vote-lock their way to control. But Bitcoin was supposed to be different. The security model relies on miners, not developers. Yet here we have a developer group telling miners they will lose revenue if they don’t comply. That’s not a decentralized consensus; it’s an ultimatum.
And what about the user? The average Bitcoin holder waking up Saturday morning may find their wallet showing two different balances. Exchanges will halt deposits and withdrawals. The price will likely gap down as uncertainty spikes. The psychological toll is real. I saw it during the 2022 crash, when panic spread through Telegram groups. The same dynamic is playing out here, but with miners instead of retail.
Takeaway: What to Watch
By Monday, we’ll know if Bitcoin holds together or fractures. But the question isn’t just about blocks—it’s about who gets to decide what Bitcoin is. The market hates uncertainty, but it loves to dance with it. For traders, the play is to reduce exposure until the dust settles. For hodlers, the advice is to wait for a clear reconciliation or a clean split. Don’t move coins during the fork window.
The real lesson is that Bitcoin’s governance is still a work in progress. The next 48 hours will test whether the network can survive a coordinated attack from within. I’ve seen the sprint, I’ve survived the trap. This time, the trap is a soft fork that could become a hard reality.