Explain It Like I’m 5
Bitcoin’s blocks are like a shared notebook meant for recording payments. Some people have started gluing pictures and collectibles into it, and BIP-110 is a proposed rule that says “money notes only, for one year.” The catch: miners get paid extra for the pictures, so almost none of them want the rule.
Key Takeaways (TL;DR)
- BIP-110 is a proposed one-year rule change that would sharply limit how much non-payment data (images, tokens, collectibles like Ordinals and Runes) can be stuffed into Bitcoin transactions.
- Miner support is effectively zero. Signaling has never topped roughly 1%, no major pool backs it, and Michael Saylor and Adam Back both oppose it.
- The clock runs out in early August. At current support, expect a quiet failure or a small minority chain split, not a network-wide change.
Every few years, Bitcoin fights over what block space is for. BIP-110 is this cycle’s version, and your pool’s signaling stance, fee revenue, and payout continuity all sit downstream of how it resolves.
What BIP-110 Proposes
BIP-110, the Reduced Data Temporary Soft Fork, would tighten the paths used to store non-financial data on Bitcoin for one year. The unusual part is activation: instead of the traditional 95% miner approval, it uses a user-activated soft fork with a 55% signaling threshold, so nodes running the software enforce the rule whether miners agree or not.
The Argument on Both Sides
Supporters say data storage crowds out payments, burdens node operators, and drifts Bitcoin from money toward a database. Luke Dashjr put it bluntly: “If BIP110 fails, Bitcoin fails with it.” Backers cite BIP-148 in 2017, when user pressure helped force SegWit through despite miner resistance.
Opponents say the cure is worse than the illness, and in some cases, believe that the fees for embedding data into blocks are already sufficiently curbing any “spam” issues. Michael Saylor argued it “turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions.” There is also a plain economic problem: inscriptions pay real fees, and post-halving, few pools will vote to shrink their own revenue.
Where Things Stand Right Now
As of mid-July 2026, miner signaling sits near zero, with F2Pool refusing outright and node adoption in the low single digits. The timeline: a voluntary lock-in deadline at block 961,542 in early August, mandatory signaling from block 961,632, and activation projected near September. At current support, expect a quiet failure or a small minority chain split; either way, the chain most miners and exchanges follow continues uninterrupted.
How BIP-110 Could Still Pass: The Game Theory
A UASF doesn’t need miners to like it. It needs miners to fear being orphaned. If enough exchanges, custodians, and economic nodes ran BIP-110 software, non-signaling blocks would be rejected by the money side of the network, and mining them becomes unprofitable.
That creates a tipping-point game. No pool wants to signal first, but if one major pool flips, orphan risk shifts onto the holdouts, and 55% can arrive fast. That is roughly how BIP-148 pressured miners into SegWit in 2017. Today, economic adoption sits in the low single digits, so the threat isn’t credible yet. Watch node counts, not tweets.
What Miners Should Do Before the August Window
Don’t panic, but be deliberate. Know what your pool signals, because your hashrate is a vote whether you cast it consciously or not, and if a minority chain splits off, hold off transacting until replay risk is clear.
Consensus fights come and go. Uptime and payouts are what compound. For an owner-operator that tracks protocol risk, runs 99%+ uptime, and picks up the phone when Bitcoin gets weird, contact BlockOps today at marketing@blockopsmining.com for pricing and availability.
Frequently Asked Questions
Will BIP-110 activate in August 2026?
Almost certainly not on the main chain. It needs 55% miner signaling and has never exceeded about 1%.
What happens to my miners if a chain split occurs?
If your pool follows the majority chain, effectively nothing. The risk sits with anyone on the minority chain.
Does my hosting provider decide what my hashrate signals?
No, your pool does. But a good host flags events like this and helps you switch pools fast; BlockOps handles pool configuration as part of turnkey setup.