Farside Investors’ new BIP-110 signaling alert makes disputes over Bitcoin discretionary data time-limited, giving exchanges, wallets, miners, pools, and node operators a concrete August window to plan during low miner signaling.
A July 3 Farside post reported a new BIP-110 signal block and listed seven signal blocks for the current period. According to Farside’s Q&A, the X account is automatically posted every time a BIP-110 signal block is generated.
Miner support remains minimal. BGeometrics’ daily API obtained on July 3 through July 2 shows 38 BIP-110 signaling blocks (0.42%) out of a total of 9,066 blocks since May 1.
In API’s most recent seven-day period from June 26 to July 2, the count was 8 out of 1,000 blocks, or 0.8%.
The activation design creates a deadline even if current miner support remains low. BIP-110 has minor thresholds, mandatory signaling fallbacks, and defined activation paths.
Public feeds move these mechanisms from forum discussions to infrastructure planning before the August period arrives.
Public alert brings small-scale support into the picture
BIP-110 is far from lock-in by miners while still producing enough signals to create a public record.
Current signaling data shows the campaign is well below lock-in. 38 out of 9,066 blocks from May 1st to July 2nd, or 0.42%. 8 out of 1,000 blocks, or 0.8%, in the latest 7-day API window. 1 of 143 blocks on July 1, or 0.70%. 2 out of 131 blocks on July 2, or 1.53%. Miner lock-in requires 1,109 of 2,016 blocks, or 55%, during the difficulty adjustment period.
The July 3rd Farside Alert’s 7 block period count is best treated as a snapshot unless combined with the number of blocks already elapsed within that retargeting period. With a lock-in threshold of 1,109 blocks, the seven signals require an additional 1,102 additional signal blocks before the period ends.
This gap discourages short-term miner activation. It also gives alerts a practical role. You’ll be able to compare every new signal to the 55% threshold and against the required signals calendar.
BGeometrics said in a June 10 background note that its daily dataset had zero signaling blocks from May 1 to around May 20, followed by low activity around May 21. He noted that the observed volumes are consistent with individual miners and small operations, with no visible commitments from major pools, and that Bitcoin Core does not support BIP-110.
When you move a large pool, the data changes quickly. BGeometrics pointed to Foundry USA and Antpool as types of pool decisions that could move daily signaling from low single digits to a more meaningful range within days.
Until then, miners’ lock-in routes will remain remote, but public alert feeds will provide visibility into the campaign.
If you are an exchange, wallet, pool, or node operator, decide whether to wait for a larger signal or build your procedure while the signal is still small. Each alert becomes part of a public record that can be tracked by customers, counterparties, and market infrastructure teams.
August window turns support data into operational risk
The BIP text uses version bit 4 to define the deployment as Reduce_data. A miner-driven lock-in requires 1,109 of 2,016 blocks, or 55%, to send a signal during the difficulty adjustment period.
The same specification defines a mandatory signaling period from blocks 961,632 to 963,647, with lock-in up to a height of 963,648 and activated one retargeting period after the height of 965,664.
The BIP-110 site shows this as a mandatory lock-in period in August, followed by approximately two weeks before activation, and then approximately one year of active restrictions. The BIP text describes an active period of 52,416 blocks before the rule expires.
For business owners, these mechanisms are more important than the ideological debate itself. During mandatory signaling, the BIP states that any block that does not signal bit 4 will be rejected as invalid by the enforcement node.
When the deployment becomes active, the enforcement node applies the new consensus limit for the active period.
Exchanges must have deposit, withdrawal, confirmation, and chain risk policies due to the controversial activation path. Wallet teams need a compatibility check between Taproot and Miniscript. This is because the BIP text states that if the proposal is validated and admits to a scenario where the chances of funds being frozen or lost are theoretically very low, changes will be required to the Miniscript compiler.
Mining pools require a clear version bit policy. Node operators need to know whether their software is enforcing BIP-110 rules and how this affects the effectiveness of blocks during mandatory signaling windows.
These decisions can be made while treating activation as uncertain. Public alerts and consensus debates about fixing block heights could create operational demand before support appears significant.
igcurrencynews has already covered broader fork risk configurations, including Bitcoin having fewer than 10,000 blocks until June’s BIP-110 deadline and early node support questions regarding anti-spam proposals.
Live publication alerts are now at the top of activation designs, moving the audience from developers and policy makers to infrastructure teams monitoring operational thresholds.
Even if the signaling is small, the preparation cost increases. If support remains near current levels, BIP-110 remains a loud but weak activation campaign toward a mandatory signaling window.
Once the major pools start signaling, market valuations will change rapidly as the path to 1,109 blocks per period is no longer theoretical. If an exchange, wallet, or large node operator publicly rejects or prepares to reject the proposal, those statements could become as important as the block header, as a contentious soft fork depends on economic arrangements.
For now, the numbers indicate a major calendar issue for smaller campaigns. BGeometrics’ latest daily data ended on July 2nd, with support still well below the miners’ threshold.
Farside’s July 3 alert indicates the signal remains visible. The most obvious change is an identifiable large pool behavior or concrete readiness statement from the infrastructure that needs to respond to the outcome.
(Tag translation) Bitcoin
