Why This Matters
Bitcoin has never forced a consensus change through with this little miner buy-in. That is about to be tested.
A proposal called BIP-110 — the Reduced Data Temporary Soft Fork — is closing in on an activation deadline in the first half of August 2026. It would impose a one-year restriction on arbitrary data embedding in transactions, targeting the methods used for Ordinals inscriptions, oversized OP_RETURN payloads, BRC-20 tokens, and repurposed Taproot data storage.
The mechanism is what makes this different from past upgrades. Its authors set the miner signaling bar at 55% of blocks in a two-week difficulty period — well below the traditional 95% threshold used for changes like SegWit and Taproot. Even that lowered bar has gone almost entirely unmet.
The Numbers Don't Lie
As of late July, the last fully completed signaling period closed at roughly 1.29%. The current period is tracking a bit higher, near 3%, but still nowhere close to the 55% required for a clean activation.
That gap matters because BIP-110 does not simply expire quietly if miners ignore it. The proposal borrows its enforcement logic from the 2017 UASF playbook — the user-activated soft fork approach that forced SegWit through over miner objections. Roughly 1,790 blocks remain before block 961,632, the height at which nodes running BIP-110 software begin rejecting blocks that fail to signal, regardless of whether 55% of hashpower ever agreed to the change. At Bitcoin's average ten-minute block pace, that height is expected to arrive around August 9, 2026.
In practical terms: a minority of node operators can choose to enforce a rule the overwhelming majority of miners have not endorsed. If enough of the network follows suit while a meaningful share of hashrate keeps mining the old rules, Bitcoin ends up with two competing chains.
Who's Raising the Alarm
The pushback has come from people with long records inside Bitcoin's technical community, not from data-storage partisans defending inscriptions.
Adam Back and Jameson Lopp have both warned that the activation parameters are reckless, arguing the 55% threshold was set low enough to guarantee a forced outcome rather than reflect genuine consensus. Their concern isn't really about OP_RETURN limits — it's about the precedent of activating a soft fork through minority enforcement when the overwhelming majority of signaling data says no.
Michael Saylor weighed in as well, calling the proposal iatrogenic — a term borrowed from medicine for treatments whose side effects cause more harm than the condition they were meant to cure. His argument: the "spam" problem BIP-110 targets is a smaller threat to Bitcoin than the governance shortcut being used to fix it.
Supporters of BIP-110 counter that the current signaling numbers understate quiet miner sympathy, since publicly opposing the proposal carries less social cost than staying silent. But three consecutive difficulty periods below 3% signaling is difficult to spin as a groundswell.
Echoes of 2017
Bitcoin has been through a version of this fight before. The 2017 Blocksize Wars pitted large mining pools, who wanted bigger blocks, against a broader coalition of node operators and developers who eventually forced SegWit through via a genuine UASF threat — one backed by wide, organic economic-node support built over many months of public debate.
BIP-110's authors are borrowing that same enforcement mechanism, but skipping most of the process that gave it legitimacy in 2017. There was no multi-year public comment period, no broad signaling campaign that built organic consensus, and no clear coalition of exchanges and custodians publicly committing to enforce the rule. What made UASF work in 2017 was that it reflected consensus that already existed among node operators; miners eventually signaled because refusing to would have orphaned their blocks off the economically relevant chain. Whether that same dynamic holds this time, with signaling this low this close to the deadline, is the open question.
What Happens at the Deadline
There are three broad outcomes once block 961,632 arrives.
Miner signaling could still spike in the final period and clear 55%, activating BIP-110 cleanly — the least likely scenario given the trend so far. Node operators running the software could enforce the rule anyway with insufficient miner buy-in, risking exactly the chain split Back and Lopp have warned about. Or the proposal's authors and remaining supporters could stand down before the deadline, letting BIP-110 quietly fail — the outcome many long-time developers are now pushing for.
Exchanges, custodians, and node operators are the parties who actually decide which chain "wins" in a split scenario, by choosing which software they run and which chain they credit as real. That decision-making process, more than the code itself, is what's worth watching over the next two weeks.
Bitcoin Gate Take
This is a governance stress test, not a technical one — the code works fine, the question is whether a small group can force a rule change the network broadly didn't ask for. Watch signaling percentages daily through the first half of August, and watch what major exchanges say about which chain they'll recognize if a split occurs. For long-term holders, the practical move is doing nothing rash: don't move funds based on rumors, and wait for exchanges and node operators to signal clear consensus before treating either side of a potential split as canonical.