BIP-110 sets August signaling window as miner support lags

Farside Investors began posting a live feed of BIP-110 signaling blocks and set an X account to post automatically when a signaling block appears. The alerts establish a mandatory-signaling window in August for exchanges, wallet providers, mining pools and node operators. Miner signaling has remained low, roughly 0.4–0.8% of blocks since May 1.

Daily data compiled by BGeometrics through July 2 shows 38 BIP-110 signaling blocks out of 9,066 total blocks since May 1, or 0.42%. Over the seven-day sample ending July 2 the rate was 8 of 1,000 blocks, or 0.8%. Single-day snapshots include 1 of 143 blocks on July 1 (0.70%) and 2 of 131 blocks on July 2 (1.53%). Farside’s July 3 alert reported a new signaling block and listed seven signaling blocks in the current retarget period.

The BIP specifies deployment as reduced_data using version bit 4. Miner-driven lock-in requires 1,109 of 2,016 blocks, or 55%, to signal during a difficulty adjustment period. The proposal defines a mandatory-signaling range from block height 961,632 to 963,647, with mandatory lock-in no later than 963,648 and activation one retarget period later at height 965,664. If the deployment becomes active, the BIP enforces new consensus restrictions for 52,416 blocks before the rules expire.

Under the BIP, enforcing nodes would treat blocks that do not signal bit 4 as invalid during the mandatory-signaling window. Exchanges need policies for deposits, withdrawals and confirmation counts if the chain faces contested validation rules. Wallet developers should check Taproot and Miniscript compatibility; the BIP text notes required changes to the Miniscript compiler and describes narrow scenarios in which funds could be frozen or lost. Mining pools must set clear version-bit policies and node operators must decide whether their software will enforce BIP-110 rules and how that affects block validity.

BGeometrics’ dataset shows no signaling from May 1 through about May 20, followed by low activity beginning around May 21. Observed signals appear consistent with individual miners or smaller operations, with no visible commitment from major pools. At current rates, hundreds of additional signaling blocks would be required to reach the 1,109 threshold within a single retarget period. A decision by a large pool such as Foundry USA or Antpool could change daily signaling volumes within days.

The public alert feed provides a running record of signaling blocks that infrastructure teams can track against the mandatory-signaling calendar. As of the July 3 feed, signals continue to appear but totals remain far below the miner threshold. Concentrated signaling by a large pool or explicit readiness or rejection statements from exchanges, wallets or node operators would alter the pathway defined in the BIP.