We choose Bitcoin BLAKE2b because we want Bitcoin's users and miners to retain meaningful control. We oppose SHA256d pool arrangements that turn miners into suppliers of computing power while pool operators decide which transactions go into their work.

Our case is about who holds power over mining. The change to BLAKE2b gives this branch a different mining hardware base. We see that as a chance to rebuild miner independence. Keeping that independence still requires independent nodes, miners and template builders.

Before you install a node, connect a miner or use a wallet, check which network the instructions support. The chains share an earlier history, so familiar names and addresses can be misleading.

Use this checklist to confirm the network. For the broader background, start with What is Bitcoin BLAKE2b?.

The choice we want miners to have

A block template is the proposed content of a block, including the transactions a miner will work on. Our preference is simple: miners should choose that content through their own nodes, while pools coordinate shared rewards.

Discussing DATUM on 18 May 2026, before the BLAKE2b fork, Matthew Kratter described that freedom:

You can decide on the composition of your blocks

— Matthew Kratter, The Bitcoin Infinity Show #203, 1:10:47–1:11:54.

He was discussing mining on the SHA256d network. We apply the same standard to the BLAKE2b network we support: verify who builds your template, rather than assuming a different algorithm or a friendly pool name settles the question. Our pool guide explains the checks.

Start with the full network name

BlakeStack follows Bitcoin BLAKE2b, displayed here as XBT. Some services use BTCB2. The BTC chain uses SHA256d proof of work.

A ticker is only a label. Check the service's network description and its current documentation. If an exchange says “XBT,” ask which chain its deposits and withdrawals actually use.

BIP-110 is not another name for this hard fork. The project FAQ distinguishes the earlier soft-fork proposal from the later BLAKE2b proof-of-work change. A guide that treats the two as identical needs checking.

Check your node against a post-fork block

The chains share history before the split. A shared genesis block, a familiar network name or the same port number cannot distinguish them.

Compare a known post-fork checkpoint instead. BlakeStack checks the first BLAKE2b block, at height 961,640, against this hash:

0000000000000050c1e5f69672f459293be14f46e5a494e7a8c8541396f18eeb

Compare it with the independent explorer's record. If you run a node, you can ask it for that block's hash:

bitcoin-cli getblockhash 961640

A match confirms that checkpoint. Also check the node's sync state and recent blocks against a source following the same chain. A matching old checkpoint alone does not show that your node is up to date.

Use the current node operator instructions to choose a compatible release. The name “Bitcoin” or “Knots” on a download is not enough; the build must understand this chain's rules.

Check the wallet or exchange explicitly

Before using a service, find answers to these questions:

  • Does its documentation explicitly support Bitcoin BLAKE2b?
  • Does the exact wallet version support the network and transaction format you need?
  • Does the exchange credit deposits and send withdrawals on that same chain?
  • Where does it explain what to do with coins held before the split?

An address can look familiar on both chains. Its appearance does not prove that the receiving service supports the network you intend to use.

For coins that exist on both branches, check the wallet's replay-protection behavior before spending. The developer documentation explains that ordinary signatures can replay and that protection applies only to signatures using the opt-in format. Do not assume every wallet transaction is protected.

Check the miner and pool together

Your miner must support BLAKE2b. A standard SHA256d miner cannot produce valid BLAKE2b work simply by changing the pool address.

Follow the pool's instructions for the exact miner, firmware, gateway and payout-address format. Check accepted work after connecting, and confirm which wallet and network will receive payouts. The network mining guide describes the node and DATUM gateway requirements.

Once compatibility is clear, use our mining-pool guide and pool comparison to check fees, payouts and backup connections.

Resolve conflicting information before continuing

If a guide, wallet or pool disagrees with the network's current documentation, ask the operator to explain the mismatch. A missing network description is also a reason to check further.

Keep the service's instructions, software version and the date of your check together. Recheck after a software update or a change to deposit, withdrawal or mining instructions. Our sources and methodology explains the checks BlakeStack applies to its own network data.