BIP110 MONITOR

Bitcoin signaling monitor · since block #937,440
connecting

Current BIP-110 Signaling Status — Difficulty Adjustment Period 477: 0.00% of blocks signaling

Indexed tip961,815
Chain tip961,815
Period signal rate0.00%
Signaling vs 55% target0.00%
Syncing historical data — 100% complete (0 blocks remaining)
Chain divergence · since block 961,632
NON-ENFORCING CHAIN
961,815
mempool.space
last block 4 min ago
gap
182
blocks
BIP-110 ENFORCING CHAIN
961,633
mempool.guide
frozen · last block 1d ago
The enforcing chain follows nodes that reject non-signaling blocks. With little hashpower it advances slowly and stays far behind the non-enforcing chain.

BIP-110 — A temporary soft fork that limits data field sizes to reduce blockchain bloat and refocus development on monetary use cases. Miners signal support by setting bit 4 in the block version field. Activation requires 55% of blocks within a single difficulty adjustment period (2,016 blocks, ~2 weeks).

Voluntary signaling deadline: block 961,632 (period 477). After this block, mandatory signaling begins.

Current Difficulty Adjustment Period
477
1,832 blocks left (~12.7 days)
Signaling blocks 0 of 184 blocks
Signal rate 0.00% need 55% to activate
Signaling rate (orange)   Period progress (blue) 184 / 2,016 blocks
Signaling Period progress 55% activation threshold
961815
961814
961813
961812
961811
961810
961809
961808
961807
961806
961805
961804
961803
961802
961801
961800
961799
961798
961797
961796
961795
961794
961793
961792
961791
961790
961789
961788
961787
961786
961785
961784
961783
961782
961781
961780
961779
961778
961777
961776
961775
961774
961773
961772
961771
961770
961769
961768
961767
961766
961765
961764
961763
961762
961761
961760
961759
961758
961757
961756
961755
961754
961753
961752
961751
961750
961749
961748
961747
961746
961745
961744
961743
961742
961741
961740
961739
961738
961737
961736
961735
961734
961733
961732
961731
961730
961729
961728
961727
961726
961725
961724
961723
961722
961721
961720
961719
961718
961717
961716
Signal Rate by Period
Difficulty Adjustment Period History
PeriodFirst blockLast block Blocks trackedSignalingSignal %
476959,616961,6312,016 / 2,01651
2.53%
475957,600959,6152,016 / 2,01626
1.29%
474955,584957,5992,016 / 2,01620
0.99%
473953,568955,5832,016 / 2,0169
0.45%
472951,552953,5672,016 / 2,01616
0.79%
471949,536951,5512,016 / 2,0167
0.35%
470947,520949,5352,016 / 2,0160
0.00%
469945,504947,5192,016 / 2,0160
0.00%
468943,488945,5032,016 / 2,0162
0.10%
467941,472943,4872,016 / 2,0163
0.15%
466939,456941,4712,016 / 2,0160
0.00%
465937,440939,4552,016 / 2,0161
0.05%
Frequently Asked Questions

BIP-110 is a proposed Bitcoin soft fork. A temporary soft fork that limits data field sizes to reduce blockchain bloat and refocus development on monetary use cases. This dashboard tracks miner signaling since block #937,440.

BIP-110 uses the BIP9 version-bit signaling mechanism. Miners signal support by setting bit 4 in the block version field. Activation requires 55% of blocks within a single difficulty adjustment period (2,016 blocks).

Bitcoin’s mining difficulty adjusts every 2,016 blocks — approximately every two weeks at the target rate of one block per 10 minutes. BIP9 uses this same window to tally miner signaling: if enough blocks in one period signal support, the soft fork locks in.

When a miner mines a block, they can set specific bits in the block’s nVersion field to signal readiness for a proposed soft fork. Setting the relevant bit with the BIP9 prefix (top 3 bits 001) indicates the miner is prepared to enforce the new rules.

Miners signal to indicate they have upgraded their software and are ready to enforce the new consensus rules if the proposal activates. A supermajority of signaling miners ensures a safe, coordinated activation without the risk of a chain split.

Once 55% of blocks in a difficulty period signal support, the soft fork locks in. After one additional grace period (~2 weeks), the new consensus rules become active and non-compliant blocks are rejected by upgraded nodes.

This dashboard fetches block data from mempool.space, checks the nVersion field of each block, and tracks the signaling rate in real time. Once mandatory signaling begins, the BIP-110-enforcing chain is tracked in parallel via mempool.guide.

Yes. A JSON API is available at https://bip110monitor.com/api with current signaling rates, block counts, and period history. Updated every minute. If you use it in a project, please link back to this page.

Public API

A public JSON API is available at the URL below, reflecting the latest signaling data. If you are using this API, please add a link to this page.

https://bip110monitor.com/api