BIP110 activation tracker

Mandatory signalling (version bit 4) begins at block 961,632. This page is static and permanent: your browser measures the last 144 blocks directly from the mempool.space API — nothing is precomputed or served fresh by me. After 961,632 the number that decides the fork is not the signalling percentage but the consecutive streak from the boundary: an enforcing node rejects the first non-signalling block and everything built on it. This page measures that streak.
Chain tip
…
fetching
Activation
…
Signalling, last 144 blocks
…
Pools signalling
…
Loading block data…

Last 144 blocks, newest first — blue = signals bit 4

signals BIP110   does not signal   at or after block 961,632

By pool (last 144 blocks)

PoolSignalling / totalShare of pool's blocks

Did the chain split? — four independent sources, checked in your browser

Checking…
SourceTip heightTip hashStatus
Each source is a separate node operator with its own view of the chain. Same height + same hash = same chain. A source a block or two behind is normal; it is only a split if the same height carries a different hash (checked against mempool.space's block at that height). Blockchair reports a block count, shown here as count − 1 = height. Note: a BIP110-enforcing node showing a lower tip than these is not a split of this chain — it is the enforcing chain above, frozen on purpose.

Context (fixed reference points, measured 2026-08-08 09:36 UTC)

432-block pre-activation window: 11/432 = 2.5% signalling — all OCEAN, which signalled in 11 of its own 16 blocks (69% of templates; Datum miners choose their own). testnet4: 0/288 — no rehearsal anywhere. Method: version bit 4 sits outside the BIP320 rolling mask, so setting it is deliberate.
— · auto-refresh every 2 min