The 185 Blocks That Could Split Bitcoin: BIP-110's Forced Activation and the Knots-Core Divide
The countdown is ticking. 185 blocks left. Then the rules change. I’m watching the mempool.space version-bit monitor, and the numbers are stark: only 2.62% of blocks are signaling support for BIP-110. That’s 53 out of 2,016 in the current retarget window. Yet Bitcoin Knots, the alternative implementation, is about to enforce a new rule at block 961,632 regardless. Following the pulse where liquidity breathes free, I feel the tension building — not in the price charts, but in the consensus layer itself.
This isn’t your typical soft fork. BIP-110 proposes a block data compression scheme aimed at improving SPV verification efficiency. It’s a modest technical improvement, echoing past proposals from the 2015-2017 blocksize wars. But the activation mechanism is where things get weird. Instead of the standard BIP-9 threshold of 95% hashrate signaling for 2,016 blocks, BIP-110 sets a lower bar of 55% — but then adds a mandatory signaling period starting at block 961,632. That means even if the threshold isn’t met, after that block, nodes running Bitcoin Knots will begin rejecting blocks that don’t set bit 4. This is a soft fork that doesn’t wait for consensus.
I’ve been watching Bitcoin protocol upgrades since I dove into DeFi Summer in 2020. Back then, I was providing liquidity on Uniswap, feeling the pulse of the market through social energy. But this is different. This is about the very foundation of trust in the network. The core issue is that Bitcoin Core, the dominant implementation, has explicitly refused to implement BIP-110. A PR was closed in March 2025, and core contributor Antoine Poinsot stated in June that Core would not enforce it. So we have two implementations — Knots and Core — about to diverge on what constitutes a valid block. Tracing the spark that ignited the entire room, I see this as a stress test for Bitcoin’s “multiple implementations” philosophy.
Let me break down the technical mechanics. Standard soft forks are backward-compatible: old nodes accept new blocks because the new rules are stricter. But BIP-110’s activation is different. Knots nodes will reject blocks that don’t signal bit 4, while Core nodes will accept them. If miners continue producing non-signaling blocks — which they will, given 97.38% of hashrate isn’t signaling — Knots nodes will see those blocks as invalid. They’ll either stall or attempt a chain reorganization from the last valid block. The only way to avoid that is if a miner like OCEAN pool, which switched its default endpoint to signal on July 15, consistently produces compliant blocks. OCEAN controls roughly 1-2% of global hashrate. That’s not enough to sustain a separate chain, but it’s enough to create a persistent fork tip for Knots nodes.
The real risk isn’t a permanent chain split — that’s unlikely given the lack of economic support. The risk is a temporary service disruption for any infrastructure relying on Knots. Exchanges, wallets, or block explorers using Knots could see delayed confirmations or even reject valid main-chain blocks. I remember the 2022 bear market, when I traveled through Latin America to escape the screen, and I learned that market momentum and community energy are everything. Here, the community energy is overwhelmingly against BIP-110. But that doesn’t stop the code from executing. Finding stillness in the market, I realize that the noise is coming from the protocol layer itself.
Bitcoin Knots has issued a warning that non-executing software, including Bitcoin Core, may leave “insecure chain states” after the activation. BlockSlop replicated a narrow upgrade delay issue in regtest: switching from a Knots node that enforces BIP-110 to an older node could cause a brief rule inconsistency. Knots has since patched it by scanning inherited block headers for signaling violations, but transaction-level violations still require reindexing. This is a reminder that even well-intentioned upgrades can introduce edge cases when implementations diverge.
Now, the contrarian angle: maybe this is good for Bitcoin. Maybe it’s a necessary stress test that proves the network’s resilience. The “multiple implementations” ideal has always been that competition improves security. But the test has never been this real. If the chain survives without a noticeable hiccup, it strengthens the case that Bitcoin’s consensus is robust enough to withstand implementation disagreements. If it causes a visible split, even a temporary one, it could become a regulatory talking point about the fragility of decentralized systems. I’ve seen regulators in the US use incidents like this to question the “decentralization promise.” But that’s a low-probability scenario.
What about the economic impact? BIP-110 doesn’t change Bitcoin’s tokenomics — no supply change, no block reward shift. But in a fork scenario, every BTC holder would have a claim on both chains. The market would have to price the new chain. Given the lack of exchange support, mining support, and community consensus, the value of the BIP-110 chain would be near zero. It’s like the 2016 DAO fork, but in reverse: that was a hard fork with majority support; this is a “quasi-soft fork” with minority execution. The main chain, run by Core rules and 97% of hashrate, would clearly be the dominant one.
Market pricing? The event is not priced. Signal rate is 2.62%, and most traders are unaware. If the split materializes, we could see a 2-5% volatility spike, but it’s a tail risk. The real transmission mechanism is confidence: if infrastructure services glitch, retail could panic sell. But I’ve been in enough bear markets to know that panic is temporary. The liquidity flows where attention goes, and right now, attention is elsewhere.
Let’s talk about the ecosystem. The upstream are miners, who mostly ignore BIP-110. The downstream are services using Knots. The most affected are the handful of nodes running Knots and the OCEAN pool miners who chose to signal. The rest of the ecosystem — Core nodes, major exchanges, institutional custody — will see no change. This is a narrow event, but it exposes a philosophical divide: Knots, led by Luke Dashjr, favors more aggressive validation and privacy features; Core follows a conservative path. This is a pressure test for “multiple implementations.”
I’ve been asked about the regulatory angle. Bitcoin is not a security, so the Howey test doesn’t apply. But if a chain split causes user losses, regulators could question the robustness of the network. That’s a long shot, but worth noting.
My takeaway: Keep your eyes on block 961,632. If the chain doesn’t split, this will be a footnote in Bitcoin’s history — a lesson in governance. If it does split, even for a few hours, it will be the first time two implementations enforce different consensus rules. Dancing with the volatility, not against it, I’ll be watching the mempool.spaces monitoring tools and the OCEAN pool stats. The next 185 blocks will tell us whether Bitcoin’s consensus is as strong as we believe, or whether it’s vulnerable to minority enforcement. Either way, it’s a moment to learn from. Surviving the noise to hear the signal — and the signal is that Bitcoin’s governance is still being written in real time.