Daily Crypto Briefs 
CASABLANCA, August 9, 2026
Bitcoin’s observed main chain reached 83 blocks without BIP-110’s bit-4 signal after the proposal’s stated mandatory-signaling window opened, with block 961,714 recorded at 08:56 UTC Sunday as BTC traded near $64,777.
The latest mempool.space block record shows the chain had advanced from height 961,632 through 961,714. A review of the public version fields across all 83 blocks found bit 4 unset each time, while the BIP-110 specification says that bit is mandatory in its proposed window.
The number is a material escalation from Daily Crypto Briefs’ report late Saturday, when the observed run stood at 11 non-signaling blocks. What changed is the span of chain evidence, not Bitcoin’s consensus rules: the observed run has grown by 72 blocks, and the data still does not show BIP-110 activation or a competing main chain.
Bitcoin was down about 0.28% over 24 hours in the market snapshot used for this report, with a market capitalization near $1.30 trillion and 24-hour volume near $12.41 billion. CoinMarketCap’s Bitcoin market page provides a public reference for current market data.
The proposal says that, during mandatory signaling, its deployment bit is included in vbrequired. In plain terms, BIP-110’s written process calls for miners to mark blocks with bit 4 over the stated range, but that described condition was not present in any of the 83 observed version fields.
BIP-110’s Mandatory Window Now Has 83 Non-Signaling Blocks
BIP-110 is a proposed Reduced Data Temporary Softfork. It would place temporary limits on several data-carrying transaction formats for new UTXOs, including specified output scripts, data pushes and Taproot constructions.
Its mandatory-signaling range runs from block 961,632 through 963,647. The specification assigns bit 4 to the reduced_data deployment and says blocks without that bit are invalid during the proposed range.
The live-chain observation is narrower than a claim that Bitcoin has adopted or rejected the proposal. A BIP document, even one listed as Complete in the repository, does not itself change the rules validated by the economic nodes running the network.
The gap between the document and the observed blocks is now more than an opening-block anomaly. The 83-block sample covers blocks mined by multiple pools and shows no visible bit-4 signal in the version fields, although a version bit on its own is not a full measure of miner or node support.
The count is also not a loss figure or a network-outage metric. It is a reproducible block-header check: anyone can compare the public records from the starting height with the current block record and test whether the bit is set. That direct evidence is more useful than treating the BIP’s calendar parameters as a completed change.
Missing Bit 4 Does Not Establish a Bitcoin Fork
The public records establish what was placed in the reviewed block headers. They do not show a network split, determine every node operator’s software, or prove that a proposed activation path has been deployed beyond the chain snapshot.
No public evidence reviewed for this update showed failed ordinary Bitcoin transfers, a competing main-chain tip, or an activation announcement from Bitcoin Core. Bitcoin holders therefore have no chain-level instruction to move standard balances based on this 83-block observation.
BIP-110 says UTXOs created before activation would be grandfathered. Its discussion of potential edge cases concerns particular pre-signed Taproot constructions, rather than a general impairment of existing BTC holdings.
That distinction also separates BIP-110 from the earlier Foundry client-vote coverage. A pool’s stated signaling process and a block’s observed version are related but different evidence, while actual consensus enforcement depends on the rules participants choose to validate.
The proposed change is also separate from Bitcoin’s longer-term cryptography work, including the $15 million quantum-readiness consortium. BIP-110 concerns a temporary restriction on data placement, not the security of existing private keys.
Bitcoin Block 963,648 Is the Next BIP-110 Checkpoint
BIP-110 sets a 55% threshold, or 1,109 blocks in a 2,016-block period, and names block 963,648 as the height by which its process says lock-in occurs no later than. It then names block 965,664 for its proposed ACTIVE state.
Those heights are timetable parameters in the proposal, not confirmations that the network will follow them. The current observation sits 1,934 blocks from the stated lock-in height, leaving block-by-block data, software releases and operator notices more useful than a calendar assumption.
The Crypto Fear and Greed Index read 31, classified as Fear, in the snapshot reviewed for this report. The next substantive checks are whether later blocks begin signaling bit 4, whether any client enforces matching rules and whether a claimed lock-in can be confirmed from public chain behavior.
Stay up to date
Get the latest crypto insights delivered to your inbox
Primary sources and further reading
| Source | Title |
|---|---|
| | Bitcoin BIPs: BIP-110 Reduced Data Temporary Softfork |
| | mempool.space: Bitcoin block 961,714 |
| | CoinMarketCap: Bitcoin market data |
| | Alternative.me: Crypto Fear and Greed Index |
Fact-checked by: Daily Crypto Briefs Fact-Check Desk
Related Articles
Frequently Asked Questions
Did Bitcoin activate BIP-110 after its mandatory-signaling window opened?
No. The observed main chain had 83 blocks after BIP-110's stated start height with bit 4 unset. The observation does not establish activation or a Bitcoin fork, and BIP-110's own proposed schedule names later lock-in and activation stages.
What does the 83-block BIP-110 non-signaling run show?
It shows that every block reviewed from heights 961,632 through 961,714 lacked the deployment bit BIP-110 assigns to reduced_data. That is direct chain evidence that the proposal's stated mandatory signaling was not visibly enforced across the observed main chain at the time checked.
Do Bitcoin holders need to move funds because of BIP-110?
No public chain evidence reviewed for this report showed a split, failed ordinary Bitcoin transfers or an instruction for holders to move normal balances. BIP-110 also says UTXOs created before any activation would be grandfathered.
Which BIP-110 height comes next?
BIP-110 names block 963,648 as its no-later-than lock-in height and 965,664 as its proposed activation height. They are specification parameters, not proof that the Bitcoin network has adopted the proposal.