Bitcoin Core Qt-Forks of BCH/BTG/Segwit

[eb9109]

Hello, as bitcoin has been forking BCH and BTG, I wondered if you could give general advice as to best cope with these forks. I have bitcoin qt wallets holding my bitcoin and also a bitcoin cash qt wallet each with separate blockchains on my HD. So now the BCH and BTG forks have established is it safe to do the following:-
1)Send coinbase the btc in my wallet.
2)Move my BTC wallet/dat file to my also synced BCH wallet, then rescan it, to reveal my BCH.
3)Send the BCH to the original wallet address that I first synced as my independant BCH wallet address, and thus separate the BCH from my btc by rescanning with its returned original BCH wallet/dat file.
4) Rescan my BTC wallet with my original wallet address (that I will then have removed from my BCH wallet as I rescan to its original address) and continue to use my original BTC wallet address(as I work online with this address and will need to rescan for BTG and segitBTC2x ie)

Will this process safely separate the two currencies ?

Would this same process be applicable to the BTG fork should it prove to be valid and stable ?
I would send my bitcoin to coinbase before the segwit fork date and thus the emerging BTC or BTC2 whichever coinbase identifies would theoretically duplicate and be separated by coinbase and give me two different balances of bitcoin after that November day(?)
As I would have moved my bitcoin after the BCH and BTG forks then presumably the process (1-4 above) would work for both currencies even if performed after the Segwit fork as I hold the keys to my original blockchain address.

Also, I appreciate that BTG has yet to prove itself. However I am anticipating that to have become clear by the time of the segwit fork in early November, which will need another copy of the blockchain and another rescan with my original private keys(wallet/dat file)

Hoping you can advise me on this process outlined above for how to best handle these forks.

Thanks

[1714813169]

1714813169

[1714813169]

1714813169

[1714813169]

1714813169

[jackg]

This is a fairly uselsee idea. You need to change addresses/wallets eiter before or after the fork.

If you send back the original address, the other client has your private keys and can still use them thus your coins can still be stolen (especially if the address has had a large amount in it before, they're more likey to want to wait for that same amount to reenter the address and quickly sweep it into theirs).

[bob123]

To safely split your coins you have to not reuse addresses/private keys/wallets.
You can split them safely by follow this steps:

• Create a new BTC Wallet
• Send your bitcoins to your new wallet
• Import your (old) BTC wallet(priv keys / word phrase) into your BCH wallet
• Create a new BCH wallet
• Send your imported BCH to your new BCH wallet

Now you have 2 new wallets (BTC/BCH) and 1 old wallet (BTC). From this point you are now safe since your coins are held on different HD Wallets.
I would also recommend to NOT use coinbase. Rather create desktop wallets.

[eb9109]

Bob and Jack...thanks for the advices....ie do it all on my own HD with new wallets....

So... by `new wallet` do you mean `create new wallet address` in Qt wallet, or make a totally seperate instance of Qt syncing to a totally seperate version of the blockchain on my HD?(I can copy and rescan the one`s I have for instance....so then there would be four of them on my HD, is that what you mean?)

My BCC wallet has currently a different address to my Btc address and is syncing to a seperate version of the blockchain on my HD...so when I import keys or dat...it will momentarily have the same address as my btc wallet right? Then I send to my unique BCC address....on its own seperate copy of the blockchain....and then the BCC is safely seperated.

Then once seperated....is it safe to continue using my original Btc address? Or will I need to use the one I send to that will hold the btc during this process? I`ve heard it said NOT to use from then on...why would that be necessary?

This process will be needed for each fork....BCC, BTG...and BTC2x?? But can be done after they fork and prove stable ?

Thanks again....

[cellard]

Bob and Jack...thanks for the advices....ie do it all on my own HD with new wallets....

So... by `new wallet` do you mean `create new wallet address` in Qt wallet, or make a totally seperate instance of Qt syncing to a totally seperate version of the blockchain on my HD?(I can copy and rescan the one`s I have for instance....so then there would be four of them on my HD, is that what you mean?)

My BCC wallet has currently a different address to my Btc address and is syncing to a seperate version of the blockchain on my HD...so when I import keys or dat...it will momentarily have the same address as my btc wallet right? Then I send to my unique BCC address....on its own seperate copy of the blockchain....and then the BCC is safely seperated.

Then once seperated....is it safe to continue using my original Btc address? Or will I need to use the one I send to that will hold the btc during this process? I`ve heard it said NOT to use from then on...why would that be necessary?

This process will be needed for each fork....BCC, BTG...and BTC2x?? But can be done after they fork and prove stable ?

Thanks again....

Im not sure i've understood your message, seems like you are confused. Let's make it simple with a step by step list:

-Make a backup of your Bitcoin Core wallet.dat file
-Close your client and rename the wallet.dat file to something else (wallet1.dat) then open it again so a new wallet.dat is created
-Create receiving addresses for your bitcoins, copy them on a txt file, close your client.
-Rename this wallet.dat to something else (wallet2.dat) and rename wallet1.dat back into wallet.dat to access it
-Proceed to send all of your coins to the addresses that you've saved in a txt file that belong to the now named wallet2.dat
-Once your wallet is empty, you are now safe to move this empty wallet into whatever fork's coins you want to access (let's say, the Bitcoin ABC client for Bitcoin Cash, the btc1 client for B2X...)
-Don't forget to rename wallet2.dat back to wallet.dat so you can access your actual BTC
-Once you have synced the fork's client, your coins will show up, and now you can send them to an exchange because the addresses will not be matching with the legacy chain. I recommend dumping them for more BTC.

Even if a fork claims to have replay protection, always empty your wallet first by moving your coins to avoid matching addresses and wait for a while to confirm everything is working, then you can transact as usual.

[jackg]

Bob and Jack...thanks for the advices....ie do it all on my own HD with new wallets....

So... by `new wallet` do you mean `create new wallet address` in Qt wallet, or make a totally seperate instance of Qt syncing to a totally seperate version of the blockchain on my HD?(I can copy and rescan the one`s I have for instance....so then there would be four of them on my HD, is that what you mean?)

Make an entire new wallet, this'll be done automatically i you change the nameof the wallet.dat file to wallet.bak.dat

My BCC wallet has currently a different address to my Btc address and is syncing to a seperate version of the blockchain on my HD...so when I import keys or dat...it will momentarily have the same address as my btc wallet right? Then I send to my unique BCC address....on its own seperate copy of the blockchain....and then the BCC is safely seperated.

If you have any BCC send it to the address your BCC will be in (your original wallet) and move your btc wallet.bak.dat (the original wallet file) there once those addresses have been enptied into your new bitcoin wallet.
You have to use separate blockchain as there is a blockchain for:
[Bitcoin Blockchain pre Aug2016 + Bitcoin Cash blockchain]
[Bitcoin Blockchain pre BCG fork + BCG blockchain]
[Bitcoin Blockchain pre B2X fork + B2X blockchain] - this blockchain does not yet exist.
If you don't use different datadirs then each respective wallet software will not function and will get stuck on trying to work out the blockchain error.

Then once seperated....is it safe to continue using my original Btc address? Or will I need to use the one I send to that will hold the btc during this process? I`ve heard it said NOT to use from then on...why would that be necessary?

NO. DO NOT DO THIS!
You might be able to do it with bitcoin ABC as no one has detected a problem with that software as of yet with leaking the wallet.dat file rom itself.However, I wouldn't recommend it.

This process will be needed for each fork....BCC, BTG...and BTC2x?? But can be done after they fork and prove stable ?

Yes. Providing they all have functioning blockchains (at least one node is running and broadcasting the data). There should be mining power pointed towards it as ViaBTC and Hashnest were at it last time. Some ETH miner will probably get on bitcoin gold (as eth also uses mainly GPUs and it seems the oldest to use GPUs and produce a good income).

Even if a fork claims to have replay protection, always empty your wallet first by moving your coins to avoid matching addresses and wait for a while to confirm everything is working, then you can transact as usual.

In the event that there is no/faulty replay protection. Do absolutely nothing and see if the problem gets fixed. Most likely if you're hoping to dump the coins and there is no replay protection, the price will be so small it's not worthwhile dumping as the price will be really smal as people will just want to try and transact as much btc as possible and completely forget about the other chain.
If you are in a hurry to cash in then of course follow cellard's advice.

[eb9109]

Ok yes, thanks Cellard and jackg, I think I understand it...what you described is helpfull as I only need 2 versions of the blockchain to achieve it.....and is otherwise what I was thinking.

The fact I cannot use my original address afterwards I find slightly worrying as I use it in so many sites....but hopefully they can update address and all then use my new btc address.... hopefully

So if I wait until after the Btcx2 fork, do I `dig` each new forks currency from the same original bitcoin address? Or does the new currency value follow where the original bitcoin balance is .... for example:

... if I use btc address 1, send it to btc address 2, then `dig` btc address 1 for BCC from BCC blockchain(as described)....when I then do the same to BTG would I `dig` from Btc address 1? As I`m thinking that the fork will hold value that was present at the time of the fork...in your explanation we move my balance of Btc to my fresh address, which shows that the balance is held on the blockchain at the time of the fork and doesn`t necessarily follow the actual balance...unless as you warned someone were to `dig` btc address 2 before I had `dug` Btc address 1.

Thanks for understanding my caution.

[cellard]

Ok yes, thanks Cellard and jackg, I think I understand it...what you described is helpfull as I only need 2 versions of the blockchain to achieve it.....and is otherwise what I was thinking.

The fact I cannot use my original address afterwards I find slightly worrying as I use it in so many sites....but hopefully they can update address and all then use my new btc address.... hopefully

So if I wait until after the Btcx2 fork, do I `dig` each new forks currency from the same original bitcoin address? Or does the new currency value follow where the original bitcoin balance is .... for example:

... if I use btc address 1, send it to btc address 2, then `dig` btc address 1 for BCC from BCC blockchain(as described)....when I then do the same to BTG would I `dig` from Btc address 1? As I`m thinking that the fork will hold value that was present at the time of the fork...in your explanation we move my balance of Btc to my fresh address, which shows that the balance is held on the blockchain at the time of the fork and doesn`t necessarily follow the actual balance...unless as you warned someone were to `dig` btc address 2 before I had `dug` Btc address 1.

Thanks for understanding my caution.

Yes, another reason hardforks are a pain in the ass is that since you have to move around your cold storage into new addresses, if you have receiving addresses that other people have to send you period payments, you will need to tell them to update to a new address in the wallet you are using. For example, everyone in signature campaigns will need to tell managers to change their addresses after the fork if you want to access the coins on the other chain (because you will need to move all of your BTC to new BTC addresses before doing so)

You will receive whatever BTC you have in a particular address at the time of the fork.

BTCAddress1 has 0.24 BTC

B2XAddress1 has 0.24 BTC

Both are the same address, but BTC means BTC chain, B2X means segwit2x chain.

The point of moving BTCAddress1 into a new BTCAddress2 is to avoid replay attack due matching addresses on both chains. Just do this before anything else and you will be OK.

[HCP]

It isn't "HardForks" in general that are the problem. It is the lack of replay protection. None of this would be necessary if replay protection is implemented... But from what I gather, the 2X is deliberately NOT implementing replay protection in an effort to become the "majority" chain without wallet software and service providers needing to update anything.

I predict a large number of "technically unaware" Bitcoin users losing a lot of coins following this fork...