Bitcoin Improvement Proposal 110 enters mandatory signaling stage
According to the BIP-110 monitor, Bitcoin Improvement Proposal 110 entered the mandatory signaling stage on Saturday at Block 961,632. Miners issued support signals in only 51 of the previous 2,016 blocks, accounting for 2.53%, far below the 55% threshold required for early activation.
Starting from blocks 961, 632, nodes executing BIP-110 began to reject blocks without version bit 4 set, while ordinary Bitcoin nodes continued to accept blocks with and without signals. A minority branch of BIP-110 then emerged, but quickly fell behind the main chain.
Low signal rates indicate that it is difficult to maintain a chain of competition without a large number of miners participating. Due to relatively weak mining support, the BIP-110 branch may progress slowly or even stop blocking completely.
This milestone tests whether supporters can advance a controversial consensus change without widespread miner support, potentially separating execution nodes from the main chain and exacerbating controversy over how Bitcoin block space should be used.
BIP-110 seeks temporary restrictions on Bitcoin data
BIP-110 proposes additional consensus restrictions that last for about a year. It limits most new output scripts to 34 bytes, sets the OP_RETURN output limit to 83 bytes, limits certain data push and witness elements to 256 bytes, and temporarily limits several Taproot features. The output of unspent transactions created before activation will not be affected.
Proponents say the restrictions will prevent inscriptions and other non-monetary data that increases storage and bandwidth costs for node operators.
Critics of the proposal, including Strategy Executive Chairman Michael Saylor and Blockstream CEO Adam Back, believe the proposal could split Bitcoin and cause nodes to reject transactions allowed by existing rules of the network.
This proposal uses version bit 4 for miners signaling. Its deployment plan sets blocks 961, 632 to 963, 647 as mandatory signaling windows, during which nodes executing BIP-110 reject blocks that do not carry signals. The specification defines blocks 963, 648 as the beginning of the locked state, and blocks 965, 664 as the point in time at which transaction restrictions take effect.
Backers of BIP-110 also discussed a broader alternative. On August 1, Bitcoin developer Chris Guidare released preliminary code based on proof-of-work change code originally written by Bitcoin Knots maintainer Luke Dashjr. Guidare described the code at the time as a contingency plan for miners to oppose BIP-110, but said no activation date had been set.

Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
BTC