Bitcoin's BIP-110 pressure test just started. Miners still aren't playing along.
The proposal's real test is no longer the data limit. It's whether enforcing nodes can make miners signal without walking onto a minority chain.
CryptoVibe Desk · bitcoin · bip-110 · soft-fork
- →Bitcoin reached block 961,632, which started BIP-110's mandatory signaling window, according to the BIP specification.
- →The monitor showed 0% support in the current period as of August 8, making enforcement the real risk.
- →Watch block 963,647: if signaling stays far below 55%, enforcing nodes are testing isolation, not consensus.
- soft fork → A soft fork changes Bitcoin rules so upgraded nodes reject some blocks that older nodes may still accept.
- mandatory signaling → Mandatory signaling means upgraded nodes require miners to mark blocks as supporting the proposal during a set block range.
- miner signaling → Miner signaling is a bit in a block that shows whether the miner supports a proposed rule change.
- minority chain → A minority chain is the version of Bitcoin followed by fewer miners and less proof-of-work.
BIP-110 just entered its pressure window.
The BIP repository says mandatory signaling runs from block 961,632 through 963,647. During that window, enforcing nodes reject blocks that don't signal bit 4. That's the mechanism. It turns a low-support soft fork into a live coordination test.
The numbers don't add up yet. The BIP sets the threshold at 1,109 of 2,016 blocks, or 55%. The live BIP-110 monitor showed 0 signaling blocks out of 4 indexed blocks as of August 8, 2026, at 21:02 UTC. CoinDesk reported support had seldom passed 2.5% before this phase.
At the script level, nothing changes because Bitcoin does not have contract accounts like Ethereum. At the node level, everything changes. If you're running an enforcing node today, you're no longer just watching miner intent. You're rejecting blocks that most miners may still build.
BIP-110 is titled Reduced Data Temporary Softfork. It aims to limit certain non-financial data uses for about one year if activated. The proposal limits large data pushes, some Taproot paths, undefined witness versions, Taproot annexes, and OP_SUCCESS cases. The tradeoff is simple rules for real compatibility risk.
This is a backpressure problem, not a spam-filter problem. Policy can decide what your node relays. Consensus decides what your node accepts as Bitcoin. Moving that line is the whole fight.
If miners don't move before block 963,647, the only number that matters is not 55%. It's the share of economic nodes willing to follow a chain miners barely support.
BIP-110 supporters choosing block rejection during the mandatory window looks reckless because miners entered it near zero support.
By block 963,647, watch whether signaling reaches 1,109 of 2,016 blocks; anything far below that means enforcement pressure failed.
Primary links and supporting reads used by the desk for this story.
Forward this.
