Bitcoin BLAKE2b is a blockchain that follows a branch of Bitcoin's history and uses BLAKE2b proof of work for new blocks. You may see it listed as XBT or BTCB2. Those labels help people discuss it, but a ticker does not identify the chain by itself.
BlakeStack follows this BLAKE2b network. Our dashboard brings together node observations, a sourced pool comparison and one exchange's price feed. You can explore all of those without connecting a wallet.
What changed from Bitcoin
The BLAKE2b change is a hard fork: software must understand the new consensus rules to validate its blocks. The first BLAKE2b block is 961,640, dated 30 August 2026. Its proof-of-work algorithm differs from the SHA256d algorithm used by the BTC chain. The developer documentation describes the transition and the new block-header format.
A shared past does not make the two chains interchangeable today. They can have different blocks, transactions and balances after their paths diverge. The BLAKE2b hard fork is also distinct from the earlier BIP-110 soft-fork proposal; the project FAQ explains that distinction.
For this guide, BTC refers to the SHA256d chain and Bitcoin BLAKE2b refers to the network BlakeStack observes. This naming keeps technical instructions clear without requiring a view on which branch should use the Bitcoin name.
Why XBT and BTCB2 need context
Different services can use different market labels. BlakeStack displays XBT, while the NeoxEX market identifier behind our price feed is BTCB2_USDC. That chart is an XBT/USDC quote from one exchange. It is not a USD conversion or a price averaged across exchanges.
When comparing an explorer, wallet, pool or exchange, check its full network description. A familiar ticker or address format is not enough to establish which ledger the service follows. In particular, do not assume a market labeled XBT elsewhere represents this chain.
Verify the chain before using a service
BlakeStack checks a fixed BLAKE2b checkpoint before accepting node observations. The first BLAKE2b block at height 961,640 has this hash:
0000000000000050c1e5f69672f459293be14f46e5a494e7a8c8541396f18eeb
You can compare it with the independent explorer's checkpoint. Our sources and methodology explains the checks we apply. A checkpoint identifies the chain; observation timestamps tell you how recently our node reported on it.
For a wallet or exchange, also verify that its software and deposit or withdrawal instructions explicitly support the intended network. A chain identifier in an API does not establish that a wallet can sign or validate every transaction format.
What you need to get started
Start with a read-only view. Open the dashboard, check the freshness indicator and look at the latest observed height. Then explore recorded network history to see how hashrate estimates and difficulty change over a selected period.
If you want to run a node, follow the current node operator instructions and verify the release you install. The relevant question is whether the build supports this chain's rules, rather than whether its name contains Bitcoin or Knots.
Mining requires compatible BLAKE2b hardware or software and a supported connection method. Existing SHA256d mining hardware cannot simply be pointed at this chain and produce valid work. The mining documentation explains the node and DATUM gateway requirements; our pool comparison helps you compare published terms.
Existing coins and replay protection
Coins and keys from before a chain split require particular care when spending across both branches. A transaction using an ordinary signature can be valid on both chains, so a payment intended for one ledger may be copied to the other.
The Knots unified-signature documentation describes opt-in SIGHASH_UNIFIED. Its replay protection applies to signatures that use the new format; it is not automatic protection for every transaction. Confirm the capabilities of the wallet you actually use before treating a spend as protected.
Use BlakeStack as an observation tool
The dashboard reports what our configured node observed. Hashrate is an estimate, the mempool is local to that node, and pool terms are editorial records with sources and review dates. Fresh readings make those observations useful; they do not guarantee a pool's future performance or a transaction's acceptance.
For your next step, compare the pool terms, download history as CSV, or read a dated network report. Developers can use the free read-only API. Each resource keeps the source and coverage visible so you can judge the numbers in context.