If you're dealing with Forkcoins, you should be worrying! I've claimed a lot of Forkcoins, but I never trusted the software on my system, and I never claimed any of them before emptying the real Bitcoin from the keys. You won't be the first to lose their Bitcoin while claiming crummies in Forks, and you won't be the last.

I have claimed various forkcoins more than once, and all my Bitcoin stash is still preserved.

P.S. In any response I would prefer to find hints about any glitches in the proposed scheme rather than emotional reactions.


History doesn't matter once the stash has been moved to new SEED.


What, for example?

Again something.

Step 1 results in  transaction that is invalid on  Blake2b chain.

Step 2 results in  transaction that is invalid on  SHA256 chain.

Tell me who could grab either of them. Please don't refer to trivial errors like setting SIGHASH_NONE flag or something similar. I wasn't born yesterday.

Just send them to yourself first, if you are worried about anything. Then, in the worst case, you will lose only transaction fees.

Anyway, I already sold all of my BIP-110 coins, but I still keep receiving a bunch of BIP-110 satoshis here and there, because of replayed transactions. When I will stop getting them, then it would mean, that enough people splitted their coins correctly.

This is an overreaction of a solution...
You have coins in cold storage, and you still want to sell for $300, there are pretty simple solutions for this, first move your coins to a new address A in a new wallet you're in control of , the clean environment for this is the best start, then spend the coins from this to a new address  B in that wallet with either
-  dust you have received from someone or from an exchange that does not exist on blake2b (Binance withdrawals seem to not be present on Blake2b, for example)
-  create an output that violates the Blake2b rules, either with op_return or by sending some dust to a P2PK output

Check this wallet on the blake2b chain, at this point you're in control of all the addresses, so you can easily see: have the bitcoin coins moved on Bitcoin from A to B and have they not moved on Blake2b because of the invalid tx? If this is true, then it's simple, move the Bitcoins from B back in storage, move the blakecoins on that chain from A to wherever you want to sell them.

Also, check the spread when selling as you might sell at 10%, and also don't try to  buy BTC on neoxa , the sprad for usdc to BTC is again insane and the fees the same, so you're going to lose 25% out of an already dumping price.

Which exchange did you use to sell it? I can't find a single reliable exchange listing it

nonkyc.io . As the name implies you don’t need to complete KYC to trade there.

The price of Blake2b BTC has been steadily declining. It is now trading at approximately three quarters below its price during the first few days. I doubt you could get the better price anywhere else, and I also don’t think this shit will recover in the near future.

Look at the Blake2B icon

This fork coin will need to design and use its own icon.
Using the old icon of Bitcoin makes Blake2B coin is more like a scam coin.
B Cash tried this method and failed years ago.

To newcomers: make sure when you buy bitcoin you are buying bitcoin!
Has Bitcoin.com stopped presenting Bitcoin Cash as the real Bitcoin?

History of Bitcoin logo
https://www.logodesign.org/the-history-of-the-bitcoin-logo/
https://bitcoinmagazine.com/culture/the-history-and-symbolism-behind-bitcoins-logo

I updated the Github repo with two Python programs, which are intended to run on an online and offline computer respectively.

The offline version is pointed at a wallet on your computer, exports addresses, and then you feed those by USB file into the online version which checks for UTXOs, and then finally bringing them back to the offline device so that the software can automatically sign a transaction with SIGHASH_UNIFIED and make a signed transaction hex you can broadcast.

No more running complex scripts