Bitcoin is heading toward a messy-looking August 2026 upgrade window, with a proposed soft fork and a separate hard fork initiative both landing in roughly the same period. That does not mean a split is guaranteed. It does mean holders, miners, and exchanges should stop pretending this is just background noise.
- BIP-110: a proposed soft fork with mandatory signaling and split risk if coordination fails
- eCash: Paul Sztorc’s separate hard fork plan, targeted around block 964, 000
- Real-world stakes: replay protection, hashrate, exchange support, and liquidity will decide what matters
- Big picture: this is as much about Bitcoin governance and market confidence as it is about code
According to Bitcoin.com News, developer Paul Sztorc is pushing a hard fork initiative branded “eCash” that targets activation around block height 964, 000, roughly Aug. 21, 2026 UTC depending on block times. At the same time, a proposed soft fork called BIP-110 is being discussed for an August signaling period, and critics say it carries the risk of an unintended chain split during activation.
That does not mean Bitcoin is about to blow itself apart. It has lived through plenty of developer drama and worse political weather. But when two competing upgrade paths crowd the same window, the boring plumbing becomes the headline: who upgrades, who doesn’t, who mines what, and which chain the market decides is the real one.
What BIP-110 is trying to do
BIP-110, as described by Cryptonews.net, is the Reduced Data Temporary Softfork, a temporary protocol change authored by Dathon Ohm. The proposal would restrict certain kinds of arbitrary data storage in Bitcoin transactions for about one year.
That includes limits on some transaction outputs, OP_RETURN data, large data pushes and witness items, and some Taproot-related usage. Inputs spending UTXOs created before activation would remain exempt.
In plain English: this is a fight over what Bitcoin blockspace is for. One camp wants to tighten the rules and cut what it sees as spam or needless data bloat. Another camp sees any protocol-level filtering of paid blockspace as a slippery slope toward censorship or overreach. Same Bitcoin, different religion.
Cryptonews.net said mandatory signaling for BIP-110 would begin at block 961, 632 and run through block 963, 647, with activation after that. The proposal uses version bit 4 and can activate early if 55% of miners signal within a retarget period, or 1, 109 of 2, 016 blocks.
Current support, according to Cryptonews.net, is very thin: as of June 22, only 0.31% of the network was signaling, equal to about 5.37 EH/s out of roughly 940 EH/s of aggregate hashrate. That is not consensus. That is a proposal still looking for a pulse.
Why a “soft fork” can still get ugly
A soft fork is supposed to be backward compatible. Old nodes can still accept the new blocks, which is why soft forks are usually less disruptive than hard forks. But the word “supposed” does a lot of work there.
If miners and nodes do not coordinate cleanly, enforcement can still fracture consensus. In BIP-110’s case, the concern is that nodes running the upgraded rules could reject non-signaling blocks during the mandatory period, creating a split in practice even if the proposal is technically classified as a soft fork.
That is the real danger: not a neat textbook definition, but a network that starts disagreeing about valid blocks. Bitcoin does not care about branding. If the chain diverges, the chain diverges.
A long-running argument over whether BIP-110 is a hard fork, not soft fork only adds more fuel to the fire, because if participants cannot even agree on the category, good luck trusting the rollout to be graceful.
What Paul Sztorc’s eCash plan adds to the pressure
The other moving part is eCash, the hard fork plan associated with Paul Sztorc. According to Bitcoin.com News, it is targeted around block 964, 000 and would create a new chain using Bitcoin’s SHA-256d proof-of-work algorithm, with a one-time difficulty reset and a 1:1 airdrop to BTC holders based on the fork block.
That last part is the bait, of course. “Free coins” always sound magical until people remember the part where a new asset still needs miners, wallets, users, and exchange support. A hard fork can create a chain in the code sense. It cannot force a market to respect it.
The proposal’s timing matters because it lands in the same general August window as BIP-110. Those are two different fights, but they can collide in the real world. One is about Bitcoin policy and transaction data rules. The other is a separate hard fork attempt with its own chain and incentives. Together, they create a longer stretch of uncertainty than either event would on its own.
What actually happens if Bitcoin splits
If a fork produces two live chains, the impact is not just theoretical. Bitcoin’s unspent transaction outputs, or UTXOs, are the “coin chunks” that make up balances. At a fork point, those balances are typically duplicated across both ledgers.
That means self-custody users may be able to sign transactions on both chains if they control their private keys. But that does not automatically make both assets usable or valuable. It only means the keys give you access to the coins on both sides of the split.
What makes a forked asset viable is much less glamorous:
Replay protection matters first. Without it, a transaction broadcast on one chain could also be valid on the other, which can cause accidental double-spends across chains. That is how a routine transfer turns into a headache nobody asked for.
Hashrate matters too. If miners do not support a chain, it becomes weaker, slower, and easier to attack.
Liquidity is the final gatekeeper. A forked coin may exist on paper, but if exchanges do not list it, traders do not want it, and custodians do not support it, the market can treat it like a souvenir instead of money.
If you want a quick sense of how these networks are tracked across markets and chains, a useful external reference is the Comprehensive Overview of Metrics Tracked on Each Chain, which is exactly the kind of dashboard that reminds people liquidity and usage are not vibes, they are numbers.
Why exchanges and custodians matter more than people like to admit
For self-custody users, a fork can be manageable with the right precautions. For centralized exchange customers, the picture is messier. A centralized exchange controls the keys, decides whether to support a forked asset, and determines whether users can actually access the split coins.
That is why exchange policy becomes almost as important as protocol design. A chain can be technically alive and commercially irrelevant if the big venues refuse to touch it. It is one of those awkward truths crypto likes to pretend it has outgrown, right up until everyone needs a withdrawal page to behave.
This also explains why the next major upgrade window is being watched so closely. It is not just a code review problem. It is a custody problem, a settlement problem, and a confidence problem.
The timing and signaling calendar is being tracked closely too, with an August timeline putting Bitcoin BIP-110 signaling and Paul in the same frame, which is exactly the kind of scheduling coincidence that gives operators indigestion.
The deeper argument: what is Bitcoin for?
Underneath the technical details, BIP-110 is really a battle over Bitcoin’s identity. One side wants a cleaner settlement layer with tighter limits on arbitrary data. The other side sees that as an attempt to police what people can do with blockspace that they pay for.
That debate has been around for years because Bitcoin was never going to be a blank canvas for everyone’s preferred use case. Some people want it to stay narrow and conservative. Others want it to remain open enough for broader experimentation, even if that means more network stress and more ugly arguments.
The hard fork side raises a different question: if enough people want a new chain badly enough, does that chain deserve to live? Maybe. But “deserve” is the wrong word in markets. What matters is whether it attracts miners, users, and liquidity without pretending a logo alone can create legitimacy.
There is also a practical layer to this debate that gets lost in the tribal shouting. If Bitcoin starts treating ordinary transaction data as a policy battlefield, people are going to keep accusing one another of hidden agendas, and frankly, some of those accusations are not exactly pulled from thin air. Developers can call it stewardship; skeptics call it social engineering with better fonts.
What readers should watch next
The biggest near-term signals are practical, not philosophical.
Watch whether BIP-110 support meaningfully increases from its reported 0.31% signaling level. Watch whether eCash gets any real traction beyond a headline-friendly fork idea. Watch exchange guidance, wallet support, and miner behavior. And watch whether anyone bothers to add replay protection early enough to prevent a mess.
Bitcoin can survive disagreement. What hurts the market is confusion, especially when it hits custody and liquidity at the same time. The code may be open-source, but the costs of a badly handled fork are very real.
Even the snarky corners of the ecosystem are paying attention, including Bitcoin Dev Martin Habovštiak Mocks BIP-110 with 66-KB experiments that underline just how silly some of the data debates can look when reduced to memes and stunt blocks.
Key questions and takeaways
-
Will Bitcoin definitely split in 2026?
No. A split is possible, but the current BIP-110 signaling level reported by Cryptonews.net is extremely low, and eCash is a separate hard fork proposal that still needs real support to matter. -
Why is BIP-110 controversial?
Because it would temporarily restrict certain forms of arbitrary data storage in Bitcoin transactions. Supporters see cleanup and spam reduction; critics see protocol-level filtering and a precedent they do not trust. -
What is the difference between a soft fork and a hard fork?
A soft fork is backward compatible, so old nodes can still follow the new rules. A hard fork is not backward compatible, which means nodes that do not upgrade can end up on a different chain. -
What happens to BTC holders if a split occurs?
In general, self-custody users who control their private keys may be able to access balances on both chains, but actual usability depends on replay protection, miner support, exchange policies, and market demand. -
Why should exchanges care so much?
Because exchanges decide whether users can access, trade, or even safely deposit forked assets. If the big venues stay cautious, a forked coin can have a chain but no meaningful market. -
What should Bitcoin holders watch now?
Wallet and exchange guidance, miner signaling, replay protection plans, and whether either proposal gains enough support to move from theory into reality.
Bitcoin’s next upgrade drama is not just about technical elegance or ideological purity. It is about whether the ecosystem can handle competing rules without turning a governance debate into a liquidity headache. That is where the real test begins.
Further reading
For more context on the fork debate and where it could go next:
