One sentence is making the rounds in chats and feeds: in about 40 days Bitcoin will split because "some miners do it one way and others differently" — keyword BIP-110. The date is roughly right. The mechanism in that sentence is wrong. And that exact mix-up turns a governance question into a doomsday rumor.
Let's separate it soberly.
What BIP-110 actually is
BIP-110 (initially "BIP-444," then renumbered) is a temporary soft fork that would restrict arbitrary non-monetary data in Bitcoin transactions for about a year — aimed at Ordinals, Runes and inscriptions. Concretely: transaction outputs larger than 34 bytes would become invalid, except OP_RETURN, capped at 83 bytes; large data pushes at 256 bytes. Normal Bitcoin payments and the Lightning Network stay unaffected, according to its proponents.
Key for defusing the panic: UTXOs created before activation are grandfathered — permanently exempt. Existing funds are therefore unaffected, regardless of wallet software.
The timing — that part is right
The mandatory phase begins at block height 961,632, projected around August 7, 2026. From that block, nodes enforcing BIP-110 reject blocks that violate the new rules. From late June, that's roughly 40 days — hence the "40 to 50 days" in the rumor.
The core: it's not miner-vs-miner
Here's the actual error. BIP-110 is a UASF — a user-activated soft fork — using a modified mechanism with only 55% miner signaling instead of the traditional 95%. That low bar is the point of contention.
But miners aren't "split." They're simply, almost unanimously, not participating. As of late June, signaling sits at about 0.3% of hashrate — at times zero. One large pool actively signals against. No significant mining pool backs the proposal.
That shifts the whole picture: the split risk isn't miner-vs-miner but a minority of nodes vs the miner majority. If miners keep producing normal, rule-breaking blocks — which they are — then the BIP-110-enforcing nodes are the ones rejecting the heaviest chain, potentially forking themselves off. A UASF only bites if the rejecting nodes are ones miners economically depend on. That leverage is largely missing here.
What realistically happens
So a clean 50/50 split is the least likely scenario. With no pool support and single-digit node adoption, the realistic paths are: BIP-110 simply doesn't activate — or a small node minority self-forks, with a brief spell of uncertainty and volatility.
Fairness requires the other side: prominent developers like Adam Back and Jameson Lopp warn that the 55% bar raises chain-split risk in principle, and Back additionally flags the risk that certain outputs could become unspendable. Proponents, in turn, invoke the 2017 SegWit activation as precedent that user-activated pressure can work against miner resistance, and the sovereignty of node operators. Both camps argue seriously — the question is the facts, not the volume.
The honest 2017 disanalogy
The comparison to the 2017 block-size war comes up constantly but has a decisive break: back then, SegWit had broad community support. BIP-110 doesn't. And economics explains the miners' silence: Ordinals and Runes are real fee revenue. No one volunteers to cut their own income — which makes the zero signaling coherent.
The situation is uncertain enough that even experienced voices abstain: Jimmy Song stated publicly he's neither for nor against, because he can't sufficiently judge the consequences of either path.
Don't conflate: the second August event
A separate event falls into the same window: an eCash hard fork around block 964,000 in August — a new chain with a 1:1 airdrop to BTC holders. It has nothing to do with BIP-110 but gets mentioned in the same breath and adds confusion.
A methodical bottom line
Separate evidence from interpretation. Evidence: the mechanism (UASF, 55%), the date (~August 7), and the practically absent miner signaling (~0%). Existing funds are protected by grandfathering; normal payments and Lightning are unaffected. Interpretation: the probability of a real split — low given zero miner backing; more realistic is "doesn't activate" or a short-lived minority self-fork.
What to watch into August: whether a single large pool flips — that would change the math — and whether the backers adjust the parameters or push forward regardless. The real story isn't "Bitcoin splits in August," it's a governance test: node-runners vs miners, data spam vs data freedom. Measure the mechanism, not the panic.
FAQ
Will Bitcoin split on August 7? A clean split is unlikely. With miner signaling near 0%, the realistic scenarios are a failed activation or a short-lived minority self-fork with some volatility — not a 50/50 break.
Are my bitcoin at risk? UTXOs created before activation are permanently exempt; normal payments and Lightning are unaffected. The biggest cited user risk (unspendable outputs) is disputed and largely defused by grandfathering.
What's the fight really about? Governance: node operators vs miners, data spam vs data freedom, and whether a low 55% threshold (instead of 95%) is a legitimate way to push through a rule change.
This post is an analytical read, not investment advice. Study the Past — Improve your Future. 🥋