- This is still Bitcoin. The history, coins, and keys through the fork are the same ledger. Running a node is how anyone can participate and verify for themselves. Bitcoin with the BLAKE2b algorithm keeps Bitcoin as money only by rejecting use of the network for arbitrary data storage.
- You do not need to move coins to keep them. Coins you already have remain spendable. If you spend the same coins on both chains, that payment can be copied across; see the FAQ.
- Staying on Core is a different chain. Bitcoin Core and older Bitcoin Knots still use the legacy SHA256d algorithm. You need a Knots version with the BLAKE2b change, from bitcoinknots.org when it is published.
- BIP-110 is not the hardfork. BIP-110 was a softfork, in alignment with the vast majority of node policy, and it was later rejected. A hardfork is a break away from abuse of the Bitcoin network. This hardfork is the switch to the BLAKE2b algorithm.
- Data limits are temporary. BLAKE2b is not. Limits on arbitrary data storage, and the ~300 kB block cap, last until 1 September 2027, 00:00 UTC (previous block's median time past). Continuing those limits after that date is a later choice for node operators. The BLAKE2b algorithm does not revert to SHA256d.
- The headline must match. The first new-style block includes a short agreed phrase,
blake2b_headline. Your node must be set to the same phrase or it will reject that block. - Pruned nodes can get stuck if they delete old blocks to save space and then switch late. You may have to download the chain again.
- Low mining power at first is expected. Difficulty will fall to match. The alternative was leaving SHA256d pools able to keep a chain that uses the network for arbitrary data storage, which every node operator on that chain must store at their own expense and, most importantly, risk.
The FAQ covers objections and edge cases without burying the main point.