Bitcoin eCash Fork August 2026: Do You Get Free Coins?

Bitcoin is trading near $65,000 as of August 8, up about 1.3% over the past 24 hours after breaking higher on Friday's weak July jobs report (payrolls at -23,000 versus roughly +80,000 expected). That move has nothing to do with forks. But the bitcoin eCash fork planned for August 2026 is the search term climbing this week, and it's worth separating from a second, unrelated event landing in the same window: a mandatory signaling period for a proposal called BIP-110. Only one of these two things has any real path to affecting Bitcoin's price or security. The other is a side event that mostly matters to people who hold BTC outside an exchange.

eCash, designed by researcher Paul Sztorc, is a hard fork of Bitcoin's codebase, not a change to Bitcoin itself. Think of it like Bitcoin Cash or Bitcoin SV back in 2017: someone copies Bitcoin's transaction history up to a specific block, launches a new chain with different rules, and gives anyone who held BTC at that snapshot moment an equal balance of the new coin. The snapshot is expected around block 964,000, roughly August 21. Sztorc has pushed back on claims this is "theft," pointing out the fork doesn't move or spend a single BTC — it just copies the ledger. That's technically true, but the project is controversial for a specific reason: it effectively reassigns roughly 500,000 dormant, Satoshi-era coins that have never moved, which strikes plenty of long-time Bitcoiners as bad etiquette even if it's not theft in a legal sense.

If you hold BTC in self-custody — your own wallet, keys you control — at the snapshot block, you'll be able to claim an equal amount of the new eCash coin (ticker XEC, which collides with an unrelated existing token also called eCash, adding to the confusion). If you hold BTC on an exchange, the answer depends entirely on whether that exchange chooses to support the fork, and most large exchanges have historically declined to support Sztorc-style forks with thin trading interest. Expect most venues to sit this one out, which means most exchange users simply won't receive anything, regardless of how much BTC they hold.

The bigger risk sits with self-custody holders, and it's the part most coverage skips: eCash has no replay protection on the Bitcoin side. That's the technical detail that actually matters here. Without it, a transaction you broadcast on the Bitcoin network around the snapshot can, in some cases, be replayed on the new eCash chain too, unintentionally spending or reassigning coins you thought you were keeping separate. Practically, that means anyone who wants the airdrop should avoid moving BTC in the days immediately around August 21 until eCash wallets and block explorers confirm how to split the coins safely. That's a real, actionable risk. It's also a narrow one — it affects your eCash claim, not your actual bitcoin holdings.

The event that could theoretically touch Bitcoin itself is unrelated to eCash entirely. BIP-110 is a proposed rule change, and it enters a mandatory signaling window around block 961,632 — roughly August 9 — that runs through a lock-in deadline near block 963,648 (about August 23), with activation, if it locks in, around block 965,664 in early September. During this window, nodes running Bitcoin Knots — a minority client that enforces the new rule — start rejecting blocks that don't signal support for it.

The activation math currently makes lock-in look dead: signaling sits near 2.6%, far short of the 55% threshold needed. But "unlikely to activate" isn't the same as "no risk." Mining pools are genuinely split on how to handle the window: OCEAN is signaling in full, F2Pool has refused outright, AntPool has stayed silent, and Foundry USA is running its own hashrate-weighted vote among its miners. That split matters more than usual right now because hashprice — what miners actually earn per unit of computing power — sits around $32 per petahash/day, at or below many miners' roughly $35 breakeven cost. When margins are that thin, any friction between signaling and non-signaling blocks, including a stretch of rejected or orphaned blocks, is more costly to absorb than it would be in a healthier market.

Realistically, no — not in the base case. eCash is opt-in, low-stakes for anyone who isn't self-custodying carelessly around the snapshot, and has shown no measurable effect on BTC price in market data so far. BIP-110's signaling numbers make a genuine contentious split extremely unlikely this cycle. The scenario that would actually disrupt Bitcoin is narrower: a large non-signaling pool mining a long run of blocks that Knots-enforcing nodes reject, causing a visible reorg or brief chain divergence that spooks an exchange into pausing deposits. Current signaling data doesn't support that as the likely outcome, but it's the one to watch for between now and the August 23 lock-in deadline, not the eCash snapshot two days later.

For most holders, the practical to-do list is short: if you want the eCash airdrop, keep BTC in a wallet you control, not an exchange, and avoid transacting in the days immediately around the snapshot until you understand how to claim safely. If you don't care about eCash, there's nothing to do — the Bitcoin network you're using doesn't change. The BIP-110 window is worth watching if you're tracking Bitcoin's governance fights, but it isn't a reason to move funds or expect volatility beyond what miner-margin stress can already produce on its own.