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.
| Period | First block | Last block | Blocks tracked | Signaling | Signal % | |
|---|---|---|---|---|---|---|
| 471 | 949,536 | 951,551 | 2,016 / 2,016 | 7 | 0.35% | |
| 470 | 947,520 | 949,535 | 2,016 / 2,016 | 0 | 0.00% | |
| 469 | 945,504 | 947,519 | 2,016 / 2,016 | 0 | 0.00% | |
| 468 | 943,488 | 945,503 | 2,016 / 2,016 | 2 | 0.10% | |
| 467 | 941,472 | 943,487 | 2,016 / 2,016 | 3 | 0.15% | |
| 466 | 939,456 | 941,471 | 2,016 / 2,016 | 0 | 0.00% | |
| 465 | 937,440 | 939,455 | 2,016 / 2,016 | 1 | 0.05% |
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.
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.
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