BIP-110 CONSENSUS WATCH
connecting…
Reduced Data Temporary Softfork · version bit 4
Reading the chain…

Fetching block headers and cross-checking independent nodes.

Chain tip
height
To mandatory window
block 961,632
Signalling, period
bit 4 · needs 55%
Knots-valid tip
blocks a BIP-110 node accepts

Version bits, block by block

loading…
bit 4 set — signalling BIP-110 other bit set bit clear bits 13–28: AsicBoost version rolling, meaningless here

Who is signalling

loading…

Split check · independent nodes

loading…
Comparing block hashes at a common height.

Where this lands

Knots stalls

Under ~5% of hashrate signals. From block 961,632 a BIP-110 node rejects nearly every block, sees maybe a handful a week, and becomes unusable. Core nodes notice nothing. No split — a stuck minority of wallets.

Real chain split

Enough hashrate (roughly 55%+ committed, or a determined 20–40%) mines a signalling chain. Two histories persist, both spendable, and the ticker BTC becomes contested. This is the outcome that needs 2+ major pools.

Soft fork activates

Signalling clears 55% in a retarget period, or mandatory signalling forces lock-in. New data limits apply at block 965,664 and expire on their own about a year later. Old nodes keep following the chain — that is what makes it soft.