Bitcoin's consensus rules go on public trial this week. The outcome is close to a foregone conclusion, and that is precisely why the episode is worth understanding.
At block 961,632, expected on or around 9 August, BIP-110 enters its mandatory signalling window. From that point until block 963,647, any miner that does not set the proposal's version bit produces a block that BIP-110-enforcing nodes will reject. Activation would follow near block 965,664 in early September, with the restrictions expiring automatically about a year later.
Miner support currently sits at roughly 2.6% of blocks. Activation requires an overwhelming majority. This is not going to activate.
What BIP-110 actually proposes
BIP-110 is a temporary soft fork that restricts non-financial data in blocks. It caps large scriptPubKeys, witness data above 256 bytes, and OP_RETURN outputs above 83 bytes — the mechanisms that inscription and token protocols use to embed images, text and arbitrary payloads directly into the chain.
Supporters frame it as reclaiming block space for monetary settlement, the purpose Bitcoin was built for. They argue that subsidising data storage with a monetary network's security budget is a category error that grows worse as the block subsidy shrinks.
Opponents make two objections. The first is technical: content filtering is unenforceable, because arbitrary data can be disguised inside transactions that look entirely ordinary. The second is political: once the network starts rejecting valid transactions on the basis of what they contain rather than whether they are valid, the precedent is harder to contain than the problem it solves.
Neither camp has convinced the constituency that decides the matter — the miners.
Where the signalling actually stands
Signalling closed the most recent completed difficulty period at 1.29% of blocks, up from 0.45% two periods earlier. The current period is running near 2.6%. Almost all of it comes from Ocean, which switched to signal by default on 15 July, supplemented by independent and small-scale miners.
The industrial pools have not moved. Foundry, AntPool, ViaBTC and F2Pool between them command the large majority of network hash rate. F2Pool has refused outright. AntPool has stayed silent. None have merged support.
Bitcoin Core, the dominant node implementation, never merged the BIP-110 patch and has not endorsed the proposal. That detail carries more weight than it appears to. A soft fork with no support in the reference client and no support from industrial hash rate has no realistic activation path, regardless of how loud the surrounding argument gets.
Jason Hughes, vice president of engineering at Ocean and one of the proposal's more visible advocates, has publicly described BIP-110 as on track to fail.
The mechanical detail node runners should know
The signalling window is mandatory, not advisory. That word does real work.
A node running BIP-110 enforcement will reject any block that fails to set the version bit. If roughly 97% of hash rate declines to signal, those nodes reject 97% of blocks for the duration of the window. They stop following the chain the economic majority is building, and either stall or track a minority chain with almost no work behind it.
This is a self-inflicted condition, not a network failure. The Bitcoin that exchanges, custodians, ETF issuers and ordinary wallets follow will continue exactly as before, because none of them are running enforcement software. But anyone operating their own node — the small, serious minority who verify rather than trust — should confirm which client and which version they are running before 9 August.
Sovereignty cuts both ways. Running your own node means you choose your own rules, and choosing rules the rest of the network rejects means you leave the network.
A proxy fight for two much larger questions
BIP-110 will fail. The argument it opened will not.
The first larger question is covenants. Proposals such as OP_CTV and OP_CAT would let Bitcoin enforce constraints on how coins can be spent in the future, enabling vaults, better custody constructions and more efficient second-layer designs. They are also the most consequential change to Bitcoin's scripting model since Taproot, and the same governance machinery that is failing to activate BIP-110 would have to deliver them.
The second is post-quantum migration. A March 2026 paper from Google Quantum AI cut the estimated qubit requirement for breaking Bitcoin's elliptic-curve signature scheme to under 500,000 qubits, roughly an order of magnitude below earlier estimates. That moved BIP-360 and the broader post-quantum discussion from a distant hypothetical to a live engineering agenda with a decade-scale clock attached.
Both of those changes will need far broader coordination than BIP-110 ever assembled. Which is what makes this month useful: it is a full-scale rehearsal, with real stakes and real data, of how Bitcoin's actors behave when a contested change is actually put to them.
Bitcoin Gate Take
The failure of BIP-110 is the system working, not breaking. A change with under 3% hash rate support, no reference-client backing and unresolved objections from serious engineers should not activate, and the fact that it cannot be forced through is the property that makes Bitcoin worth holding for decades rather than quarters.
What to watch is not the activation counter but the aftermath. If the covenant and post-quantum debates inherit BIP-110's tone — factional, deadline-driven, signalling-first — Bitcoin will struggle to ship changes it genuinely needs before the quantum timeline forces the issue. That is the risk worth tracking, and it will play out over years, not weeks.
If you run a node and want to understand what consensus rules you are actually enforcing, the self-custody and protocol modules in the free Bitcoin Gate course cover the mechanics from first principles.