Saylor Says BIP-110 Cannot Reach Its Threshold
Michael Saylor posted new numbers on BIP-110 today. He says the proposal is falling further behind.
At block 961,022, BIP-110 has only 38 signals. That is 2.70% of blocks checked.
Saylor said the 55% voluntary threshold needed for early lock-in is now impossible to hit this period.
What Happens At Block 961,632
Saylor pointed to a key date coming up fast. At block 961,632, BIP-110 nodes will start rejecting non-signaling blocks.
This means the rule changes from optional to forced. Nodes running BIP-110 will treat blocks without the signal as invalid.
Saylor argues this creates a split. Miners who do not signal keep building normal Bitcoin blocks. Enforcing nodes reject those same blocks.
Why Michael Saylor Wants Backers To Stand Down
Saylor's message was direct. He said Bitcoin will keep running normally unless major miners change course.
He believes BIP-110 will either stall out or turn into an irrelevant side chain. Neither outcome helps the proposal's supporters, in his view.
Because of this, Saylor called on BIP-110's backers to stop pushing it forward.
The Numbers Behind The Claim
|
Block Height |
Signals |
Blocks Checked |
Signal Rate |
|
960,561 (Aug 1) |
24 |
946 |
2.54% |
|
960,723 (Aug 2) |
28 |
1,108 |
2.53% |
|
961,022 (Aug 4) |
38 |
not disclosed |
2.70% |
The trend has stayed flat near 2.5% to 2.7% for days. BIP-110 needs 1,109 signaling blocks out of 2,016 to lock in voluntarily, which is roughly 55%.
At the current pace, even a full run of remaining blocks could not close that gap.
Background On The BIP-110 Fight
BIP-110 is formally called the Reduced Data Temporary Softfork. It is a one-year proposal meant to limit certain non-financial data on Bitcoin's blockchain.
Supporters say it would cut down on spam-like data storage and protect node resources. Critics say it blocks transactions that are currently valid and fee-paying.
Saylor has opposed the plan since mid-July. He first laid out 110 reasons against it, arguing that changing consensus rules to fight spam sets a risky precedent.
He also flagged that most early signals traced back to a single DATUM miner sharing rewards through OCEAN, not a broad group of pools.
What Comes Next For BIP-110 Backers
If the current period ends without reaching 55%, the rules shift. Starting at block 961,632, enforcing nodes require the signal and reject blocks without it through block 963,647.
That is the mandatory-signaling window Saylor is warning about. It does not mean Bitcoin itself forks by default. It means only nodes running BIP-110 software would reject unsigned blocks, while the rest of the network keeps operating as usual.
The gap between these two groups is what worries Saylor most.
