Bitcoin outlook, 2026-08-20

Two weeks after BIP-110 failed to lock in, its supporters have not stood down; they have escalated. The soft fork's mandatory signaling collapsed at under 3 percent of blocks in early August, and the minority chain that rejected non-signaling blocks froze almost immediately. The response, covered in our earlier pieces, was a slogan: fire the miners. The past ten days turned the slogan into code.

The sequence is concrete. In early August, developer Chris Guida rebased Luke Dashjr's 2017 proof of work hard fork code onto Bitcoin Knots, describing it as code to keep in the back pocket; the rebased code leaves mainnet activation unscheduled but resets difficulty so the first block after a switch would be roughly a million times easier to find. On August 11, Dashjr ran a public draw for the replacement algorithm, committing in advance to whatever a coming Testnet4 block hash selected; it produced BLAKE2b. On August 15 he opened pull request 359 in Bitcoin Knots, a hard fork draft that replaces SHA-256d with BLAKE2b, reshapes the block header, and aims for compatibility with hardware from several manufacturers. Supporters are targeting September 1 for the switch, and proposals circulating among them would keep the data restrictions in force into 2028, roughly two years instead of the original year.

Strip away the branding and this is what a proof of work change means. Every ASIC securing Bitcoin today would be useless on the new branch, by design; that is the point. What cannot be copied is harder to replace. A fork can carry over the transaction history and every unspent coin, but it cannot carry over the users, the exchanges, the capital and the market that make Bitcoin worth securing. A new miner base would have to be built, and before that an economic value large enough to pay for its own security. Bitcoin Gold tried exactly this in 2017, changing the proof of work to be friendly to graphics cards; it was 51 percent attacked in 2018 and again in 2020, because a chain anyone can mine with rented hardware is a chain anyone can rent an attack on.

There is also a governance lesson, and it cuts both ways. BIP-110's supporters are right that miners do not govern Bitcoin alone; the failed lock-in does not make miners sovereign. But node operators do not govern alone either. A node can reject any block it wants; that refusal is its guarantee. When almost nobody follows it and it responds by changing the mining algorithm, the difficulty schedule and the block header, it has not taken control of Bitcoin. It has created another network. To keep image data off what they consider the real Bitcoin, the proposal now on the table rewrites the deepest layers of the system its authors set out to protect.

For now, nothing is adopted. Guida's rebase is an explicit contingency, pull request 359 is an open and unfinished draft, no exchange or index has committed anything to the new chain, and Bitcoin's own rules continue exactly as before. History's verdict on proof of work forks has not been kind, but it is not a forecast's place to decide this one; the market will, by choosing where capital, hashrate and users go.

That market, meanwhile, is looking elsewhere. Bitcoin extended its recovery to a third day, trading above $72,000 on Thursday after a high of $72,427 on Coinbase, roughly 16 percent above last week's low of $62,468. Our three horizon views are unchanged; a fork debate with no economic weight behind it remains, for the forecast, what it was two weeks ago: a governance story at the edge of a market that has moved on.

This is general market commentary, not investment advice or a recommendation to buy or sell any asset.