Daily Crypto Briefs 
CASABLANCA, Aug. 15, 2026
Bitcoin’s BIP-110 monitor showed a 973-block rejected standard branch with zero observed bit-4 signals Saturday, clearing the 950-block mark after standing at 909 earlier in the day, as BTC traded near $62,907.
The monitored standard node had reached block 962,604 while the BIP-110-enforcing node remained at 961,635, a 969-height gap. The dashboard labels the standard-chain history a valid rejected fork under the enforcing node’s rules, a narrow but measurable view of two nodes that are following different validation rules.
The update is a material escalation from Daily Crypto Briefs’ 900-block BIP-110 report. The rejected branch added 64 blocks, or about 7.0%, and crossed a new round-number threshold, while the enforcing node did not advance.
The BIP110 Situation Monitor recorded 973 scanned standard-chain headers without version bit 4, the deployment bit named in the BIP-110 specification. It also listed its standard node’s tip hash as 00000000000000000000fcc6ec23de45883d0115a46df8ba1f7be4d543604a5e, matching mempool.space’s public block record when checked.
BTC was near $62,907, roughly 0.1% below its Aug. 15 opening price of $62,979 and about 2.3% below the $64,390 level recorded a month earlier, according to Kraken’s Bitcoin market page. Those market moves do not establish that the monitored divergence caused a price change.
Bitcoin
BTCThe monitor’s status is not a Bitcoin-wide incident declaration. It shows a standard node accepting and extending a history that one BIP-110-enforcing node rejects. No public evidence reviewed for this update showed a general Bitcoin payment outage, a change in ordinary user balances, or broad migration guidance from exchanges, custodians or wallet providers.
Bitcoin BIP-110 Fork Clears 950 Rejected Blocks
The 973-block total measures the standard history the BIP-110 node rejects. It is not identical to the 969-block difference between the two node tips, because the monitored histories can include blocks that are shared at one point but classified differently by the node’s branch accounting.
That distinction matters. A node running a different rule set can reject a growing standard history while conventional Bitcoin nodes continue to accept and build on it. The dashboard’s diverged status reports the observed disagreement between its two nodes, not a finding that all Bitcoin users have split into two networks.
The BIP-110 text calls the proposal a Reduced Data Temporary Softfork. It describes temporary consensus limits on selected output scripts, data pushes, witness items and certain Taproot constructions, while grandfathering UTXOs created before activation.
The enforcing node remained only three blocks above BIP-110’s mandatory-signaling height of 961,632. The standard node continued to extend the public chain to 962,604, a fact independently visible through the explorer. The monitored numbers provide evidence of the dashboard’s two-node split, not evidence that the standard chain has stopped operating.
For holders, the relevant question remains service behavior rather than the headline block count. A custodian or exchange that chose a different history would need controls for deposits, withdrawals and chain selection. No large service had issued such operating instructions in the sources reviewed for this report.
Zero Bit-4 Signals Remain the Immediate BIP-110 Test
The absence of a signal remains the clearest new technical fact. All 973 headers in the monitor’s current window lacked bit 4. The monitor attributes the observed blocks to 16 pool labels, including Foundry USA, AntPool, F2Pool, ViaBTC, SpiderPool and MARA Pool, and showed zero signals for each listed group.
Those labels are dashboard attributions, not governance statements from the pools. Similarly, the zero figure identifies what was present in the inspected headers rather than proving the intentions of every miner, node operator or company that uses Bitcoin.
The proposal sets a no-later-than lock-in height of 963,648 and a proposed activation height of 965,664. As outlined in Daily Crypto Briefs’ earlier BIP-110 activation timeline, those are terms in a proposal, not proof that the standard chain has locked in the rules or that services have adopted them.
Bitcoin consensus changes involve more than a header bit. Software choice, validation rules, hash power, transaction relay and service-provider policies can each affect what users experience. The latest monitor reading supports a more limited conclusion: in this observed 973-block standard-chain window, there were no BIP-110 bit-4 signals.
The standard tip’s growth without a signal puts attention on concrete next events. A bit-4 header, a new block on the enforcing chain or formal guidance from a major service would be more informative than another ordinary block alone. Until then, the dashboard’s branch length is a live technical measurement, not a directive for users to move coins.
Bitcoin Services Still Show No Broad Migration Signal
No public statement reviewed for this article told ordinary BTC holders to alter their custody arrangements because of BIP-110. The standard-chain tip remained publicly available in an independent explorer, and the monitor did not list an outage affecting routine Bitcoin transfers.
That does not reduce the need for accurate language around a fork. A divergent node can be operationally important to the operator running it, while still not changing the balances or payment path seen by a user whose service follows the standard chain. The 973-block branch is therefore a significant new threshold in the monitored data, but not evidence of a universal network split.
The same caution applies to other Bitcoin protocol debates. The quantum-wallet rescue discussion concerns different proposed rules and different risks. It does not create an instruction to move BTC because the BIP-110 monitor’s rejected branch has grown.
The Crypto Fear & Greed Index read 34, or Fear, on Aug. 15. The index is broad Bitcoin-market sentiment, not a measure of BIP-110 adoption, the monitor’s node health or the risk of a service interruption.
Fear & Greed Index
Aug. 15, 2026The next verifiable milestones are limited and specific: a standard-chain bit-4 signal, an enforcing-chain block above 961,635, or public operating guidance from a major Bitcoin service. Until then, what has changed is the measured threshold: a 973-block rejected standard branch, a 969-height gap and zero observed bit-4 signals in the monitor’s current scan.
Stay up to date
Get the latest crypto insights delivered to your inbox
Primary sources and further reading
| Source | Title |
|---|---|
| | BIP110 Situation Monitor: Live |
| | Bitcoin BIPs: BIP-110 Reduced Data Temporary Softfork |
| | mempool.space: Bitcoin block 962,604 |
| | Kraken: Bitcoin price and market data |
| | Alternative.me: Crypto Fear and Greed Index |
Fact-checked by: Daily Crypto Briefs Fact-Check Desk
Related Articles
Frequently Asked Questions
What changed in the latest BIP-110 fork update?
The BIP110 Situation Monitor's rejected standard branch grew from 909 blocks to 973, passing the 950-block threshold. The monitor still showed zero bit-4 signals across the scanned headers and the same BIP-110-enforcing node height of 961,635.
Does a 973-block BIP-110 branch mean Bitcoin has split for all users?
No. The reading shows two monitored nodes following different histories under different validation rules. It does not by itself show broad exchange, wallet, custodian, payment-provider or miner support for the shorter BIP-110 history.
Did any Bitcoin blocks signal BIP-110?
No. The monitor's 973-header scan contained zero bit-4 signals when checked. That is an observation about the headers in its window, not a formal vote or a statement from every miner or node operator.
Do Bitcoin holders need to move BTC because of BIP-110?
No public evidence reviewed for this report showed a general instruction to move normal BTC balances, a broad payment outage or broad service suspensions on the standard Bitcoin chain.