bitcoin-forks.org August 2026 consensus-event monitor
page freshness: live at launch

Live dashboard

Current state of the BIP-110 window

How to read this ›
Preview build. The compact clock strip below reads the live chain-height feed. Every other panel (mempool divergence, signalling, enforcement census, pool intent, chain tips) is still pending and activates as its feed ships.
current tip height: live at launch current tip height
deployment state: live at launch deployment state (voluntary)
blocks to 959,616: live at launch blocks to 959,616 (period 476)
blocks to 961,632: live at launch blocks to 961,632 (mandatory)
feed timestamp: live at launch Full event clock ›

Mempool divergence · Core vs Knots

pending

Source A · Core mempool

live at launch
transactions in mempool
snapshot age: live at launch
diff

Source B · Knots mempool

live at launch
transactions in mempool
snapshot age: live at launch
Classified difference: transactions present in one source but not the other, at the last aligned snapshot.
Classification In Core, not Knots In Knots, not Core Reading
Oversized output script (rule 1 shape) live at launch live at launch Held out of the Knots mempool by policy
Large data push (rule 2 shape) live at launch live at launch Policy difference, not a consensus verdict
Other / unclassified timing live at launch live at launch Propagation timing, expected churn
Total distinct live at launch live at launch
Absence is not rejection. A transaction missing from one mempool reflects that node's relay policy or propagation timing. It is never, on its own, proof that the transaction would be invalid in a block. Source: mempool-atlas headless Core/Knots difference, pending.

Signalling by period

signalling: live at launch
current-period signalling: live at launch share of the current period's blocks with bit 4 set
Red mark: 55 percent voluntary threshold (1,109 of 2,016).
PeriodHeight range startSignalsPercent
472951,552live at launchlive at launch
473953,568live at launchlive at launch
474955,584live at launchlive at launch
475 (current)957,600live at launchlive at launch
Bit 4 is a header claim, not proof of enforcement.
Source: header / signalling state (per-period counts, current-period progress), pending.

Enforcement census

crawl: live at launch
share advertising bit 27: live at launch advertising service bit 27
reachable node count: live at launch reachable nodes crawled
Reported cohortNodesShare
Knots v29.3.knots20260508live at launchlive at launch
Standalone activation client v0.4.1live at launchlive at launch
Other, bit 27 advertisedlive at launchlive at launch
A crawl sample of advertised flags. Not authenticated enforcement, hash power, or economic weight. This panel's standalone-client row counts only the exact v0.4.1 user-agent; the Learn page's dated snapshot counts all standalone UASF-BIP110 client versions, a broader, differently-dated cohort. A difference between the two is not a contradiction.
Source: enforcement census (service bit 27 node counts), pending.

Pool intent · per endpoint

pool intent: live at launch
EndpointTemplate intentLast job
OCEAN · defaultlive at launchlive at launch
OCEAN · bip110live at launchlive at launch
OCEAN · no-signallive at launchlive at launch
Comparison pool Alive at launchlive at launch
Comparison pool Blive at launchlive at launch

Template intent is what each Stratum endpoint is actually building, spooled continuously across OCEAN's three endpoint modes plus comparison pools. Intent to signal is still not proof of enforcement.

Source: Stratum archiver, per-endpoint intent, pending.

Chain tips

tip families: live at launch
TipHeightStatusSeen by
live at launch live at launch active Core, Knots, standalone
live at launch live at launch valid-fork Core, Knots (stale sibling)
live at launch live at launch headers-only Core only

Fork-observer style tip families across the monitoring fleet. In steady state there is one shared active tip: no branch extends a rejected ancestry. During a live fork, watch for a second tip that different nodes disagree about.

Source: tip families (fork-observer), multi-node view, pending.

Reading order matches how a split becomes visible: mempool policy divergence first, then template intent, then realized tips. New to these terms? The Understanding BIP-110 explainer defines every one and explains why absence, signalling, service bits, and node counts each prove less than they appear to.