Bitcoin BIP-110 fork deadline nears with zero miner support
In brief
- BIP-110 would cap OP_RETURN and block arbitrary data chunks above 256 bytes for one year
- Miner signaling at zero; node adoption in low single digits, mainly Bitcoin Knots
- Michael Saylor and Adam Back argue consensus change over spam creates dangerous precedent
- Signaling period runs through early August with voluntary lock-in at block 961,542
Miner and Node Adoption Stalled
Miner signaling support has never risen above approximately 1% in any period and stands at zero in the current one. No major mining pools have backed the proposal. Among the nodes that store and relay the chain, adoption sits in the low single digits, carried almost entirely by Bitcoin Knots software. The numbers paint a picture of a proposal that hasn't won over Bitcoin's infrastructure operators.
BIP-110 uses a user-activated soft fork mechanism with a 55% miner-signaling threshold rather than the traditional 95%. This lower bar was designed to enable activation without overwhelming consensus. Yet even that threshold appears unreachable.
The Consensus-Risk Argument
Michael Saylor and Adam Back have emerged as the proposal's most vocal critics. Saylor argued that BIP-110 turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions. His concern cuts to the heart of the opposition: setting a precedent where technical disputes become fork triggers.
"there are 110 things more dangerous to Bitcoin than spam. BIP 110 turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions. That precedent is the danger." — Michael Saylor, Strategy founder
Adam Back, the Blockstream co-founder whose hashcash design is cited in the Bitcoin white paper, made a similar case.
What Happens at Lock-In
The current signaling period runs from block 957,600 to 959,615, with a voluntary lock-in deadline at block 961,542 expected in early August. If locked in, nodes running BIP-110 software would begin rejecting any block that does not signal support, with activation projected near September.
In practice, a rule enforced by a few percent of nodes and almost no miners does not change Bitcoin for everyone but would split off a minority chain. The broader network would continue under the existing ruleset, unaffected by the fork attempt.
The underlying dispute is real. Blocks have carried more non-financial data since an October change, and reasonable people see that as a drift from Bitcoin as money toward Bitcoin as a database. But whether that drift justifies a contentious fork—especially one lacking miner consensus—remains the central tension as the deadline approaches.
Frequently asked questions
What is BIP-110 and what would it do?
BIP-110, the Reduced Data Temporary Soft Fork, proposes to tighten data paths on Bitcoin for one year. It would cap OP_RETURN at the old small size, block most arbitrary data chunks above 256 bytes, and restrict script formats used mainly for data storage. The goal is to reduce non-financial data bloat in blocks.
Why do critics like Michael Saylor oppose BIP-110?
Saylor argues that BIP-110 turns a technical spam dispute into a consensus change that would invalidate currently valid, fee-paying transactions. His concern is that setting this precedent—forking over a technical disagreement—poses greater risk to Bitcoin than the spam problem itself.
What happens if BIP-110 activates with zero miner support?
A rule enforced by a few percent of nodes and almost no miners would not change Bitcoin for everyone but would split off a minority chain. The broader network would continue under existing rules, unaffected by the fork attempt.
