Daily Crypto Briefs 
CASABLANCA, August 8, 2026
Bitcoin crossed BIP-110’s mandatory-signaling start at block 961,632 on Saturday, but the first three observed main-chain blocks did not carry the proposal’s bit-4 signal, underscoring that the document’s proposed rule was not visibly being enforced network-wide as BTC traded near $65,015.
mempool.space showed Bitcoin at block 961,634 at about 20:30 UTC. The BIP-110 specification names 961,632 as the first block in a 2,016-block mandatory-signaling period, during which its proposed reduced_data deployment requires bit 4.
Blocks 961,632, 961,633 and 961,634, mined by AntPool, F2Pool and OCEAN respectively, had version fields whose bit 4 was unset in the public block data reviewed for this report. The latest of those blocks therefore did not exhibit the signal described in the BIP.
That is a material change from earlier Saturday, when Bitcoin was 12 blocks below the same threshold. It does not establish that BIP-110 is active, that Bitcoin has forked, or that ordinary user funds need action. It shows that the chain has reached the proposal’s stated window while producing blocks that would not satisfy the document’s proposed signaling requirement.
Bitcoin was up about 0.13% over 24 hours, with market capitalization near $1.30 trillion and 24-hour volume near $12.37 billion in the market snapshot reviewed for this report; CoinMarketCap’s Bitcoin page provides a current public market reference.
Bitcoin
BTCBitcoin BIP-110 Mandatory Signaling Has Begun
The narrow factual point is the block height. BIP-110 states that mandatory signaling spans blocks 961,632 through 963,647, and says the deployment’s bit is included in vbrequired during that period.
It also says blocks without bit 4 in that range are invalid under the proposal’s deployment rules. Bitcoin’s observed main chain nevertheless continued through the start height and three subsequent block records did not show the bit, a distinction that is important for headlines calling this an enacted Bitcoin rule.
The BIP remains a specification. A proposal in the BIPs repository, even one labeled Complete, does not by itself demonstrate network-wide deployment or make the current Bitcoin network enforce its rules. The article’s own schedule puts lock-in no later than block 963,648 and activation at 965,664.
The underlying policy debate concerns arbitrary data on Bitcoin. BIP-110 calls itself a “Reduced Data Temporary Softfork” and proposes limits on specified output scripts, data pushes and Taproot constructs, with a stated one-year active duration. It also says UTXOs created before activation are exempt from its new rules.
Three Main-Chain Blocks Lack the BIP-110 Bit-4 Signal
The observed result is more specific than a general claim about miner support. AntPool’s block 961,632 had version 536895488, F2Pool’s 961,633 had version 537133056 and OCEAN’s 961,634 had version 632168448. In each case, the bit that BIP-110 assigns to its deployment was not set.
Those version fields are an observable data point, not a complete governance tally. Mining pools build blocks, while node operators choose the software and validation rules they run. A pool’s block version alone cannot settle whether a proposed consensus change has broad economic or technical support.
Foundry had previously described a hashrate-weighted client vote around the proposal, as Daily Crypto Briefs reported when the pool set out that process. The current blocks add an on-chain development to that earlier reporting: the BIP’s compulsory range is no longer a countdown, but there is no observed bit-4 signal in its opening blocks.
No public chain evidence reviewed for this article showed failed Bitcoin transfers, a split in the main chain, an activation notice from Bitcoin Core, or any instruction for holders to move normal Bitcoin balances. Claims that the proposal has already changed Bitcoin’s transaction-validity rules would go beyond the facts established here.
Block 963,648 Is the Next BIP-110 Milestone
The next height named by the specification is 963,648. BIP-110 says lock-in occurs no later than that height, followed by a proposed ACTIVE state at 965,664. Those are schedule parameters in the BIP, not confirmations that the wider network will follow them.
The proposal’s temporary rules would be more consequential for new transactions than for existing coins. It says pre-activation UTXOs are grandfathered, while its listed restrictions could affect certain data-heavy output formats and uncommon Taproot paths after an activation. That separation is why the height crossing alone is not a blanket warning for Bitcoin holders.
The episode is distinct from Bitcoin’s longer-term security discussions, including a $15 million quantum-readiness consortium. BIP-110 is focused instead on proposed limits for data placement and a contentious activation design.
Fear & Greed Index
August 8, 2026Alternative.me’s Crypto Fear and Greed Index stood at 30, classified as Fear. The next useful checks are the blocks approaching 963,648, their version fields, notices from miners and node-software maintainers, and whether any claimed activation is supported by observable chain behavior rather than the BIP timetable alone.
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,634 |
| | 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 at block 961,632?
No activation was confirmed in this report. Bitcoin crossed the height that BIP-110 names as the start of mandatory signaling, but the first three observed blocks lacked the proposal's bit-4 signal. The BIP itself puts activation at height 965,664 after a lock-in stage.
What does bit 4 mean in Bitcoin BIP-110?
BIP-110 assigns bit 4 to its reduced_data deployment. Its specification says miners must signal that bit during the proposed mandatory-signaling range from blocks 961,632 through 963,647.
Why do blocks without bit 4 matter?
Under BIP-110's proposed deployment rules, a block without bit 4 in the mandatory window would be invalid. Their appearance on the observed main chain is evidence that the proposal's rule was not visibly enforced network-wide in this check, not evidence of a completed activation.
What would BIP-110 change if it activates?
The proposal would temporarily restrict specified data-carrying transaction formats, some Taproot constructions and OP_RETURN payloads for new UTXOs. It says UTXOs created before activation would be grandfathered.
What is the next BIP-110 date or block to watch?
The next specified chain-height milestone is block 963,648, where BIP-110 says it would be locked in no later than that height. The proposed activation height is 965,664, though neither step should be assumed until it is actually observed and supported by deployed software.