Timeline of blocks signalling support for BIP 110 (Reduced Data Temporary Softfork)
Loading BIP 110 block data
About BIP 110 Miner Support
What is BIP 110?
BIP 110 (Reduced Data Temporary Softfork) is a consensus soft fork proposal that temporarily limits arbitrary data embedding in Bitcoin transactions. It aims to restrict data storage methods (such as inscriptions and large OP_RETURN outputs) while preserving monetary use cases, refocusing Bitcoin on its role as sound money.
How Are Blocks in Support of BIP 110 Detected?
Blocks signalling support for BIP 110 are detected using the version bits mechanism (BIP 9). Miners set a specific bit in the block header's version field to indicate readiness for the soft fork:
Bit 4 is assigned to the BIP 110 "reduced_data" deployment
When a miner includes bit 4 set in the block version (e.g. 0x20792010), that block is counted as signalling support
Detection methods may include parsing the block version field and checking for the presence of the deployment bit
This page displays blocks that have been identified as signalling BIP 110 support through version bit 4
How Will the BIP Mechanism Kick In?
BIP 110 uses a modified BIP 9 deployment with several key parameters:
Threshold: 55% â Only 1109 out of 2016 blocks (55%) need to signal for early activation, compared to 95% for traditional soft forks like SegWit
Early activation â If 55% of blocks in a retarget period signal support, the deployment locks in and activates one retarget period later
Mandatory activation â Regardless of miner support, BIP 110 activates unconditionally at block 965,664 (~September 2026)
Mandatory signaling period â During blocks 961,632 to 963,647, all blocks must signal bit 4 or they are rejected as invalid
Temporary deployment â The rules are enforced for approximately one year (~52,416 blocks), then expire. UTXOs created before activation remain exempt
Once activated, the new consensus rules limit OP_RETURN to 83 bytes, cap data pushes at 256 bytes, and restrict several other data-embedding vectors. The goal is to reduce block space consumption from arbitrary data storage while keeping Bitcoin focused on its monetary function.