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 BIP-110 bifurcates behind, with miners 'signal support rate of only 2.53%.
A few chains lack protection, and replay risks increase.
BIP-110 bifurcates behind the Bitcoin main chain by 21 blocks. Previously, the node was forced to reject block 961,632 earlier on August 9.
In the previous cycle, only 51 blocks out of 2,016 blocks signaled support for BIP-110, equivalent to only 2.53% of miners supporting it.
BIP-110 requires a signal via version bit 4 before block 963, 647, and then a forced lock begins at block 963, 648.
A few forks lack automatic replay protection, posing operational risks to holders of transferred BTC.
Bitcoin's BIP-110 activation attempt has generated an active minority fork after forcing the node to reject an unsignaled block at height 961,632. Most miners reportedly continue to extend existing networks, quickly widening the gap between the two competing branches.
As of approximately 01:00 UTC on August 9, the BIP110 Monitor showed that the main chain was at block 961,654 and the mandatory branch was at 961,633. This leaves a small number of chains behind by 21 blocks, while of the first 23 blocks of the new difficulty cycle, zero blocks signal support.
The BIP-110 fork lags behind, with miners signaling support rate of only 2.53%
The split began in block 961,632, marking the opening of the proposal's mandatory signaling window. AntPool dug up an unsignaled block, while Roughnecks generated a competing block that complied with the rules through OCEAN.
Therefore, the node executing BIP-110 rejected AntPool's chunk and followed the alternative branch. At the same time, larger non-executive networks continue to extend Bitcoin under existing consensus rules.
Before the split, support for the proposal was already limited. In the previous 2,016 block cycles, only 51 blocks signaled support, accounting for only 2.53% of the total. Essentially, BIP-110 adopts a modified BIP9 activation process.
According to its early locking rules, 1,109 blocks (or 55%) of the 2,016 blocks are needed to signal support, but miners 'participation is well below this threshold. Since the early threshold was not reached, BIP-110 entered the forced signaling phase in blocks 961, 632.
Since then, execution nodes have begun to reject blocks that do not have version bit 4 set. Mandatory signaling requirements will continue until Block 963,647. According to the proposed rules, a few branches will be forcibly locked in blocks 963, 648. However, the proposed trading restrictions will not take effect immediately.
These rules are scheduled to take effect in Block 965,664 and expire after 52,416 blocks. Therefore, the current fork mainly revolves around signaling requirements and chain selection, and has not yet involved transactions that violate temporary data restrictions proposed by BIP-110.
Lack of protection for minority chains, increasing replay risk
Despite some descriptions on social media, BIP-110 is not a quantum computing security upgrade. Its official name is the "Reduced Data Temporary Soft Fork," reflecting its narrower goal of temporarily restricting arbitrary data embedded in Bitcoin transactions.
The proposal introduces seven consensus rules covering scriptPubKey, OP_RETURN data, witness payload, and several Taproot related structures. However, its "completed" status in the BIP repository does not mean that Bitcoin has adopted the proposal.
In contrast, the designation simply indicates that the specification itself is considered completed. Actual adoption still depends on miners, users, exchanges, custodians, and other economic participants deciding which software and consensus rules they endorse.
Bitcoin Core does not adopt the implementation of BIP-110, and most computing power continues to extend the non-execution chain. As a result, the main network is developing much faster than a few branches.
Since there is only limited computing power to support forking, the block generation time there may be much longer than Bitcoin's standard target of approximately one block every 10 minutes. Therefore, for BTC holders, the most immediate concern is operational rather than mainstream network failures.
A few forks do not provide automatic replay protection until their later activation phases, which increases additional risks when moving tokens. Therefore, a transaction made on one branch may affect the same token on another branch. Developers therefore warned holders not to view the split as a risk-free airdrop opportunity.
