# Luke Dashjr accelerates his Bitcoin hard fork in an attempt to reach September 1

> Luke Dashjr has already merged the Bitcoin Knots BLAKE2b hard fork code: we review his group's progress toward activating the new chain
> By José Maldonado · Bitcoin · 2026-08-19

Luke Dashjr has [**announced**](https://x.com/LukeDashjr/status/2089059943374557292) that he has already merged the code of his Bitcoin hard fork into the branch `[**__base_29_blake2**](https://github.com/bitcoinknots/bitcoin/tree/__base_29_blake2)` of the GitHub repository of [**Bitcoin Knots**](https://github.com/bitcoinknots), taking a concrete step toward the creation of a new altcoin derived from Bitcoin that his group has been preparing for weeks.

The new fork will change the proof-of-work algorithm from SHA-256d to BLAKE2b, and although the stated goal remains to activate it on September 1, 2026, no final client or specific activation height has yet been published, which leaves serious doubts as to whether that schedule will be met as announced.

## A failure that opened the door to a chain of its own

The decision that gives life to this new Bitcoin hard fork stems from the resounding failure of BIP-110, the temporary soft fork promoted by Luke Dashjr that sought to restrict the amount of arbitrary data (Ordinals inscriptions, text and images) that can be stored in Bitcoin transactions.

Recall that this BIP was drafted by the pseudonymous developer Dathon Ohm, with contributions from Dashjr himself, and that the change required 55% miner signaling to activate. But when block 961,632 arrived on August 8, 2026 and the mandatory signaling period began, barely 2% of the miner set supported the change, a chain-split was generated, a full-blown hard fork that left the BIP-110 chain paralyzed for days.

In fact, the block difference between the two chains has already exceeded 1,500 blocks, with the Bitcoin mainnet at block 963,136 and BIP-110 at block 961,636, a clear acknowledgment of the scant support BIP-110 has received.

![](https://content.observatorioblockchain.com/wp-content/uploads/2026/08/Captura-de-pantalla_20260819_020909.png)

In fact, most blocks have been produced by the small mining group [**Roughnecks**](https://x.com/Roughnecks110) through the DATUM system of the OCEAN pool. Surprisingly, OCEAN, created by Luke Dashjr, has decided to stay on the sidelines, at least for now, of BIP-110 mining, and in fact has set aside Luke Dashjr and Mechanical (its CTO) from their positions within the pool. This whole situation is clearly reflected in the more than 400,000 accumulated unconfirmed transfers, the zero participation of exchanges, the absence of a verifiable market, among other elements within the community itself.

**[Ethereum studies Bitcoin's UTXO model to become lighter](https://observatorioblockchain.com/en/ethereum/ethereum-estudia-utxo-de-bitcoin-para-hacerse-mas-ligero/)**

## From debate to the technical roadmap

But far from giving up, BIP-110 supporters went in a matter of days from arguing to dividing up the work. In a Bitcoin Knots development meeting held on August 10 on the [**official Discord,**](https://discord.com/invite/scKhfvBnp) three essential lines of work for the hard fork were assigned. Dashjr took on the redesign of the block header and the changes to proof of work.

On the other hand, a developer identified as “Kyle” took charge of replay protection, a critical point because BIP-110 did not include it and funds could be duplicated across chains. And Chris Guida, who weeks earlier had updated the PoW change plan Dashjr wrote in 2017 on the current codebase, took on the adaptation of the RDTS (Reduced Data Temporary Softfork) itself.

The group also set as priorities a deliberately broad difficulty reset, since the minority chain inherited Bitcoin's full difficulty and that is why it stalled, and a larger nonce space for miners, in addition to evaluating improvements such as 64-bit block timestamps and fixes for temporary attacks.

With these changes, Dashjr seeks to rewrite the fast block history of the BIP-110 chain relative to the Bitcoin mainnet chain, even with little computing power, which makes sense considering that there are no enormous networks mining the Blake2b algorithm.

## The choice of the Blake2b algorithm: a cryptographic “lottery” on Testnet4

But perhaps one of the most striking and shameful moves was how the new algorithm was chosen. To “prevent miners or hardware manufacturers from getting ahead by preparing specialized equipment,” Dashjr designed a commit-reveal process: first he published the SHA-256 hash of a table associating the last character of the hash of a future block with a candidate algorithm (among them: BLAKE2b-256, SHA3x, BLAKE2s, Scrypt, BLAKE3x2 and Eaglesong), and on August 11, 2026, at 14:00 UTC, the next Testnet4 block determined the winner. The following day the result was confirmed: BLAKE2b.

But this has been harshly criticized for one reason: Testnet4 is a Bitcoin test network, a network with low computing power, to the point that a current computer can manipulate the network and fabricate blocks at will. And everything points to that being the case, according to a recent [**analysis by Peter Todd.**](https://x.com/peterktodd/status/2087194653019746734)

**[A Trezor breach exposes the home addresses of thousands of cryptocurrency owners](https://observatorioblockchain.com/en/cybersecurity/una-brecha-de-trezor-expone-miles-de-direcciones-de-usuarios/)**

## Incompetence and malice

Todd argues that Dashjr decided to use Testnet4 out of incompetence and malice. The former, because of how easy it is to manipulate a block on that network. And the latter, because Dashjr's intention is to choose a specific PoW and have an advantage as a miner over it.

This theory gains particular strength when we see that figures close to Dashjr and his fork, such as [**@BitcoinSith**](https://x.com/BitcoinSith), already have in their possession newly acquired Blake2b mining machinery, just over a week after having “decided” to use Blake2B as the new mining algorithm. Something that draws the community's attention, when the usual lead time to access this equipment is about 2 to 3 weeks.

![](https://content.observatorioblockchain.com/wp-content/uploads/2026/08/Captura-de-pantalla_20260819_014830.png)

## When?

In any case, the reference date for this new Bitcoin hard fork remains **September 1, 2026**, the same day BIP-110 would have activated its rules according to the original schedule, and it was the deadline Dashjr himself suggested when asked about the launch of the separate coin.

The documentation from [**Start9**](https://start9.com/), which maintains Knots packages for its operating system, is more cautious: it stresses that as of mid-August there was no released client or announced activation height, and recommends treating September 1 as “a stated intention, not a schedule.”

However, two weeks before that date, at least two pieces are still pending: a version of Bitcoin Knots with the fork enabled on mainnet and the publication of the text of the “headline” that will validate the founding block, along with the specific activation height that today remains disabled by default in the code.

**[Hackers exploit a critical macOS flaw to control Macs and mine Monero](https://observatorioblockchain.com/en/cybersecurity/hackers-explotan-un-fallo-critico-de-macos-para-minar-monero/)**

But if the plan is fulfilled, the chain will inherit Bitcoin's full history up to the split point and abandon SHA-256d, remaining permanently separated as an independent network with its own mining economy.

That implies rebuilding from scratch the ecosystem Bitcoin takes for granted: mining software, pools that understand the new header, explorers, wallets and, above all, exchanges and liquidity, which it currently lacks entirely. Only September 1 will tell whether that bet is viable or whether the merged code remains as another consensus experiment with no network behind it.
