cold wallet (without moving btc) I haven't see any tutorial for this.
otherwise, if you spend btc in the main network, moving to an address that you are in control of, this can't be recorded in this new blockchain/btc hard fork.
simple as that it should be a basic way to move bitcoin.

just import the old key/ old address that has spent btc in a blake2b wallet --> you can move this to the exchange and spend your new coin.
1 confirmation in the main network is enough this is just a normal transaction in the standard network, after you spend your coins these can't be spent again in a fork chain.

Guys, I did it. I successfully swept my Blake2B BTC and sold it all for BTC at around $670 per coin.

Tomorrow, I will post a guide, I stayed up all night doing this and I'm too tired to do anything right now.

If you do that, you won't be able to redeem the forkcoins since that chain will consider the grandfathered coins moved, from my understanding. You have to move the Blake2B BTC first to a new address you control, and use SIGHASH_UNIFIED (0x21), not regular sighashes. This particular sighash ONLY works on BIPcoin.

The best way to sweep is by signing a transaction on an airgapped device, or even better with TailsOS, using Python. Import your seed phrase into an offline device's wallet (e.g. Electrum), go to Wallet -> Information, and copy the zpub. You will need this to gether the unspent UTXOs.

On the offline device, install cryptography module for Python so that you can run the scripts:


Use the Electrum console to export all of your private keys with balance to a text file (the signing script I will attach below will need it)

Run this in the console:


I used thetmp folder because it gets cleared on reboot usually and it's easier for me than writing placeholders in the tutorial.

(electrum_helpers.py on Github)

If you have more/less addresses you can adjust per_batch.

Now transfer the JSON to an online device and place and the script build_manifest.py to an online device so that we can scan mempool.guide (a Blake2B mempool) for coins unspent before the fork.


(build_manifest.py on Github)

This creates a folder fork_data with a file manifest.json containing the unspent UTXOs.

Now take it back to the offline device and run this command in Electrum console:


keys.txt contains your funded private keys. Keep it offline.

Next, get an address you will send the funds to. It can be one within your own wallet, or even one that you are spending from. But it should belong to you. You can send it to an exchange or something, but I recommend sending it to yourself first.


(offline_sweep.py on Github)

signed_review folder will contain a series of raw transactions tx_*.hex, sized to fit inside Blake2B coin's blockchain. Now you can go to mempool.guide or some other explorer, and broadcast it there. Do not broadcast it to a Bitcoin explorer - it will not work anyway because SIGHASH_UNIFIED is invalid in Bitcoin.

When the tx is confirmed, repeat the offline_sweep process for transferring the funds to your account at Nonkyc.io, then sell them for BTC. I would not use some other exchange unless someone can vouch for it.

Then delete all files on your offline device and reboot it.

Scripts require Python 3.10+

I know, and this step is not strictly necessary, but it gave me peace of mind last night.

My method does not involve using random software. Only Electrum is required. Python is also needed, but chances are if you're using Electrum you probably have Python to run the scripts as well.

I have only tested this on bech32 addresses. If there is interest, I can make a version of the sweeper that supports legacy addresses (1).

Edit: Done, see the OP


No, that's a shitcoin on Robinhood chain.

Without SIGHASH_UNIFIED, the only way to move your forked coins with replay protection is to buy a small amount of B2BTC somewhere and use that in your transaction, or ask someone for it. It's not entirely ideal.

Avoid running any random code found on unknown links on anything that even involves your secret keys, even if it is "offline method". And one is SIGHASH_UNIFIED. There is no official record of such SIGHASH in Bitcoin rules and I think this is big warning sign for me.
Saving all of your active secret keys to text file (keys.txt) and also running untrusted Python code on them offline or online is how people will lose their coins anyway. If code is not good and unsafe they can steal keys when you later try to set them back online.
Simple rule, if “guide” asks you to share secret keys + run program you have downloaded + share with some trading site you never heard of (Nonkyc.io). That is clear sign of scam. It is better to wait for site (wallet or trading site) which officially handles split.

Not bad for shitcoin - but honestly until/unless some simpler, risk-free method comes along, I wouldn't think of playing with my cold storage. Still, the idea of ​​earning something free on the side was never something to be dismissed, although of all the BTC forks, I think I only claim one and I still regret not selling it when it was worth a few thousand $.

So far, for security reason and safety of fund, I only read guides to move bitcoins to a new wallet, wait for confirmation, and use the empty Bitcoin wallet with private keys to claim fork coins.

Claiming this Blake2B BTC fork coin goes against this basic security principle, it's too risky.

But why Blake2B BTC do something opposite than other forked coins did?
Is it a security trap from them to steal real BTC?

https://99bitcoins.com/cryptocurrency/bitcoin/bitcoin-forks/

https://coinguides.org/how-to-claim-forked-coins-safely/

Interesting, but time consuming.

I think you could achieve the same result in less time with Shrike wallet.

The relevant workflow could be the following:

1. Move your Bitcoin to  new address/wallet ^{associated with fresh SEED} , making the replay protected transaction using Sparrow ^{or any other wallet}. To do this, just combine your UTXOs with UTXO resulting from  transaction that is already replay protected ^{check on mempool.guide}. You may get it from  exchange ^{for example}.

2. Wait for at least 6 confirmations on SHA256 chain, go to Shrike, find your Blake2b coins, and send them to exchange.

Any critiques?