Bitcoin Improvement Proposal 110 can no longer reach its 55% voluntary miner threshold during the current difficulty period, according to blockchain signaling data and an Aug. 1 analysis from Strategy Executive Chairman Michael Saylor.
Summary
- 28 signaling blocks appeared among 1,108, leaving BIP-110 at 2.53% support as of Aug. 2.
- Saylor said all 24 initial signals came from DATUM miners sharing rewards through OCEAN’s system.
- Mandatory signaling starts at block 961,632, when enforcing nodes reject every non-signaling block as invalid.
Strategy’s official website identifies Saylor as the company’s executive chairman. At block 960,561, Saylor counted 24 signaling blocks among 946, equal to 2.54%. He said every signal came from miners using DATUM while sharing rewards through OCEAN, with none identified outside that system. By 11:13 UTC on Aug. 2, the public BIP-110 monitor had advanced to block 960,723 and counted 28 signals among 1,108 blocks, or 2.53%. Only 908 blocks remained.
BIP-110 cannot reach voluntary lock-in
The proposal needs 1,109 signaling blocks within one 2,016-block difficulty period to lock in voluntarily. Even if every remaining block in the current period signals, the total could reach only 936. Saylor therefore said the threshold was “mathematically unreachable” and argued that the observed count was “not miner consensus.”
The latest monitor supports that arithmetic. However, it does not independently establish Saylor’s attribution of every signaling miner. His pool claim applied to the 24 blocks examined at block 960,561. The monitor confirms that the overall rate remained almost unchanged after four additional signals appeared.
BIP-110 would restrict Bitcoin transaction data
BIP-110, formally called the Reduced Data Temporary Softfork, proposes seven temporary consensus restrictions. These include limiting most new output scripts to 34 bytes, capping OP_RETURN outputs at 83 bytes, restricting certain data pushes to 256 bytes and temporarily limiting several Taproot features. Outputs created before activation would remain exempt.
Supporters say the one-year rules would reduce arbitrary data storage and keep Bitcoin focused on monetary activity. Critics, including Saylor and Blockstream co-founder Adam Back, argue that consensus rules should not determine which currently valid transaction structures deserve block space. As previously reported, Saylor said fee markets and individual node policies offer a safer response to disputed data use.
Saylor questions OCEAN and DATUM’s role
Saylor also alleged that OCEAN made BIP-110 signaling the default on an existing endpoint. He called the initiative a “vertically integrated marketing campaign for Knots and OCEAN/DATUM.” That description represents his interpretation rather than a finding by an independent technical body.
The official BIP-110 installation guide directs users toward Bitcoin Knots and includes instructions for pointing rented hashpower at a DATUM node. OCEAN’s DATUM documentation says miners create block templates through their local nodes, while the pool coordinates reward splits instead of constructing mining work. Those documents confirm the technical relationship, but they do not independently establish Saylor’s claim about promotional intent.
Mandatory signaling becomes the next test
The current voluntary period ends at block 961,631. From block 961,632 through 963,647, software enforcing BIP-110 is designed to reject every block that does not signal bit 4. The proposal would then lock in at block 963,648 and activate at block 965,664, when its transaction restrictions would begin for 52,416 blocks.
Saylor warned that any 100% signaling reading during the mandatory window would reflect the software rule rather than a fresh vote of support. Foundry USA Pool has separately asked its mining customers to vote on whether the pool should signal, with its voting window scheduled to close near block 961,632. No verified result was publicly available by Aug. 2.
The next decisive evidence will come from major mining pools, exchanges, wallets and node operators before the mandatory period starts. Low voluntary signaling does not automatically cancel BIP-110 because its deployment includes mandatory signaling. However, enforcing nodes could follow a minority chain if most hashpower continues mining non-signaling blocks. Saylor and Back warned that enforcing the proposal without broad agreement could divide the network.
