BIP-110 nears activation with 2.45% miner support

Bitcoin is approaching block 961,632, the point at which nodes running software that enforces BIP-110 will begin rejecting blocks that do not signal for the proposal. Monitoring data shows 41 of 1,674 counted blocks, or about 2.45%, are signaling for BIP-110 as the mandatory signaling window approaches on Aug. 8.

BIP-110, formally called the Reduced Data Temporary Softfork, would limit the size of certain data fields in transactions for about one year. The change is distributed mainly through the Bitcoin Knots implementation; Bitcoin Core has not adopted the proposal. Ordinary bitcoin transfers and Lightning Network payments are designed to continue under the proposal, and existing balances would not require migration.

The proposal uses a miner signaling threshold of 55% for lock-in. The BIP-110 rules instruct enforcing nodes to reject nonsignaling blocks after block 961,632, which can create two competing transaction histories if most mining power does not signal. At current signaling levels, nodes enforcing BIP-110 could begin building a smaller chain composed only of signaling blocks while the majority of hashpower remains on the existing rule set.

Major mining pools including Foundry, Antpool, F2pool and Viabtc have not signaled support. F2pool co-founder Chun Wang wrote on X: “Every morning I wake up, open the X app, search for ‘BIP-110,’ and block a few people with the term in their names before breakfast.” The proposal’s creator and developer uses the name Dathon Ohm.

A small number of service providers have announced contingency measures. The Australian exchange Hardblock warned it may pause trading, deposits and withdrawals around the expected activation window. Lightning tooling provider Amboss flagged early August as a potential fork risk period. Australian exchange Bitaroo said it would freeze deposits and withdrawals if network conditions require it. Major international exchanges and large custodians have not issued public commitments to list or support any forked asset.

If a minority chain forms, it would start with little hashpower and could produce confirmations more slowly until mining difficulty adjusts downward. Technical duplication of balances across chains would not create automatic liquidity or wallets, exchange listings, custody support, developers, and buyers. Practical obstacles for anyone chasing a forked token include replay risks, unstable wallet support and private-key exposure.

The first enforcement checkpoint is block 961,632. Block 963,648 is the final possible lock-in point under the proposal’s mandatory route, and block 965,664 would mark the start of full data limits on any chain that secures lock-in. Strategy founder Michael Saylor urged backers to “stand down.” For users who keep funds with major exchanges or standard wallets, no action is currently required.