6 min read

The Bitcoin Blake2B chain split: BIP-110 and the fork of 8 August 2026

On 8 August 2026 a group of Bitcoin nodes began enforcing a rule that was supported by the minority of the network. They split off at the next block, waited three weeks for eight blocks, and then changed their proof of work to keep going. The result is a separate chain that calls itself Bitcoin and trades as BTCB2. This is the short reference to the split; the journal post of 21 October tells the full story.

Why did Bitcoin and Bitcoin Blake2B split?

Because BIP-110, a temporary limit on the data Bitcoin transactions can carry, made miner signalling mandatory from block 961,632. Only 2.53% of blocks in the last voluntary period signalled. When the enforcing nodes, running Bitcoin Knots, rejected the first block that did not signal, they left the network. The last shared block is 961,631, mined at 19:33 UTC on 8 August 2026; the minority's own block 961,632 followed at 20:12 UTC. After eight SHA-256 blocks it hard-forked to BLAKE2b proof of work at block 961,640 on 30 August. Bitcoin kept its name and BTC; the minority chain calls itself Bitcoin too, sets no ticker, and is listed as Bitcoin Blake2B, BTCB2. Every BTC balance at the split exists on both chains, 1:1.

Last shared block961,631, 8 August 2026, 19:33 UTC
First Bitcoin Blake2B block961,632, 20:12 UTC, a block that signalled BIP-110; Bitcoin's own 961,632 (AntPool) did not
Rule changeMandatory BIP-110 signalling from 961,632; SHA-256d until 961,639, then a hard fork to BLAKE2b from 961,640 (30 August 2026, Bitcoin Knots 29.4.1, Knots PR #359)
Data rulesBIP-110 limits and an 800,000-weight block limit until 1 September 2027
Balances1:1; every BTC balance as of block 961,631 carried over. Replay protection is opt-in only
TickersBitcoin (BTC) on the majority chain; Bitcoin Blake2B (BTCB2, also BIP110 and XBT on some venues) on the minority chain

Why it split: a vote that became a requirement

BIP-110, the Reduced Data Temporary Softfork, set out to limit how much arbitrary data a transaction may carry: output scripts over 34 bytes (83 for OP_RETURN), data pushes over 256 bytes and several Taproot features would be invalid for about a year. Its supporters, led in public by Bitcoin Knots maintainer Luke Dashjr, regard inscriptions and similar data as spam. Its opponents regard them as transactions that pay the fee like any other. Knots shipped the rules as an opt-in from version 29.3 in May 2026.

The dispute itself would not have split the chain. The activation rule did. Miners were asked to signal with version bit 4, and 55% of a 2,016-block period would have locked the rules in. Unlike an ordinary deployment, which times out when miners do not signal, BIP-110 made signalling compulsory from block 961,632: the enforcing nodes would reject any block without the bit. In the last voluntary period 51 of 2,016 blocks carried it, 2.53%, reportedly all from the OCEAN pool. The mandatory clause took effect against about 97% of the hashrate.

The split, block by block

Block 961,631, mined at 19:33:48 UTC on 8 August 2026, is the last block both chains share. The next block on Bitcoin came from AntPool and did not signal. Bitcoin Core nodes, and Knots nodes not enforcing BIP-110, accepted it; the enforcing nodes rejected it and waited. At 20:12:12 UTC a signalling block arrived, mined through OCEAN, and from then on two different blocks stood at height 961,632. The BIP was marked Closed on 9 August, "following a chain split with stalled mining".

The minority chain had inherited Bitcoin's full difficulty with a sliver of its hashrate, and nothing in BIP-110 allowed for that, because a soft fork assumes the majority is on its side. It mined eight SHA-256 blocks in twenty days, the last of them, 961,639, on 28 August.

30 August: the hard fork to BLAKE2b

The way out was to stop competing for SHA-256 miners. Knots pull request #359 replaced double SHA-256 with BLAKE2b, the algorithm of the Sia network, whose purpose-built machines had little else to mine. It also introduced a new 164-byte block header and cut the difficulty by a factor of 222. Block 961,640, the first BLAKE2b block, was mined at 06:14 UTC on 30 August; the production release, Bitcoin Knots 29.4.1, followed on 2 September. With it the BIP-110 data rules switched on at the change of proof of work rather than by signalling, together with a temporary block limit of 800,000 weight units, about a fifth of Bitcoin's. Both apply until 1 September 2027.

This is the second step that made the split permanent. Until block 961,640 the two chains differed only in which blocks their nodes accepted. From it, no SHA-256 machine can mine the minority chain, and no BLAKE2b machine can mine Bitcoin.

Who kept which name

Bitcoin kept the name, the ticker BTC and every exchange listing. The minority chain claims the name as well: the Knots release notes call it "Bitcoin" and call the majority chain an altcoin, and its project site, bitcoin-blake2b.org, sets no ticker. The markets settled on other labels. NonKYC and LiveCoinWatch use BTCB2, other venues BIP110 or XBT. The site lists the chain as Bitcoin Blake2B, the name its markets use, as it listed Bitcoin Cash in 2017 without ruling on which branch inherited the name. That question is argued in Bitcoin took two upgrade paths in 2017.

How balances carried over

Every address that held bitcoin at block 961,631 holds the same amount on Bitcoin Blake2B, 1:1. Addresses, network ports and transaction formats are the same as Bitcoin's, and replay protection is opt-in only, so a plain transaction signed for one chain is valid on the other unless the sender splits the coins first. No premine or developer fund is documented; the 21 million cap and the halving schedule are unchanged.

The supply is Bitcoin's whole ledger at the split, 20,067,600 coins, plus 3.125 for every block mined since. Since 16 November the asset page computes it at each build from the chain's height, read from the mempool.guide explorer, and derives the market capitalisation from that figure. At block 982,169, the tip on 16 November, the formula gives 20,131,781 coins. The count includes every lost and dormant bitcoin copied at the split, coins whose owners may never touch this chain; the asset page labels it that way. On 21 October, when the journal post was written, the site showed no market cap.

What changed since 21 October

The journal post left one decision open: what would follow the 45-day lock on block rewards that Knots 29.4.2 had imposed from block 973,440, aimed at pools that do not build their own block templates. Four proposals were open. The one adopted is the 180-day rolling lock, Knots pull request #468, released in Knots 29.4.3 on 28 October; the other three, a 45-day rolling lock, a one-year lock and permanent BIP-110 rules with a 280-day lock, remain open. Rewards from block 979,919, the first block after the 45-day window, cannot be spent for 25,920 blocks, about 180 days, and the rule runs until the BIP-110 rules expire in September 2027. Block 979,919 was mined at 23:49 UTC on 31 October. The same release stopped sending blocks above 961,631 to peers that do not advertise BLAKE2b support.

Bitcoin Knots 29.5, released on 6 November 2026, keeps both locks and adds bug fixes. It is the node software bitcoin-blake2b.org now names for the network. Its release notes warn that miners who do not run their own DATUM Gateway "should expect to never get paid", and describe making the lock contingent on that as a possibility; the rule in the released code is the 180-day lock.

The chain keeps producing blocks. Its tip on 16 November was block 982,169, mined at 00:31 UTC, about 6,100 blocks ahead of Bitcoin's 976,040, a lead built in the days after the difficulty cut. Price, volume, market cap and hashrate are on the Bitcoin Blake2B asset page.

Why it counts as a cryptocurrency

The site counts an asset as a cryptocurrency when it has its own blockchain and its own consensus. Bitcoin Blake2B met both tests at 20:12 UTC on 8 August, when its first block was one no Bitcoin node would accept: from that moment its nodes enforced rules Bitcoin's nodes do not. The switch to BLAKE2b made the separation visible to anyone with a miner, but it was already complete. Both Bitcoin and Bitcoin Blake2B are listed; the distinction between a rule change and a lasting split is set out in Hard fork vs chain split.

Sources

Related

Seven chain splits, side by side — every split on the price charts, with dates, blocks and names.

BIP-110: how a soft fork became a new cryptocurrency — the full story, markets and pools included.

The Bitcoin Cash chain split — the 2017 minority fork that kept SHA-256 and wrote in replay protection.

The Bitcoin Diamond chain split — another Bitcoin fork with a new proof of work, in November 2017.