I followed goatpig's instructions. I am augmenting them in-line here to make it easier for noobs like myself to understand.Quote
If you want to dump BCH but don't want to bother with the BCH node/don't trust their code, you can get around it with this trick:
1) You know all your prefork coins are also available on the BCH chain, therefor you only need blockchain data up to the fork point to move these coins.
2) You have all this data already in the form of the Bitcoin blockchain pre fork, so why not just use that?
3) You'll want to create a copy of your blockchain data then remove blkXXXXX.dat files up until the fork point . I don't know which file this is, something around 950~960, I'm sure someone will figure out the exact file. Note that if you did not move any coins post fork yet, you do not need to delete anything.
1) You know all your prefork coins are also available on the BCH chain, therefor you only need blockchain data up to the fork point to move these coins.
2) You have all this data already in the form of the Bitcoin blockchain pre fork, so why not just use that?
3) You'll want to create a copy of your blockchain data then remove blkXXXXX.dat files up until the fork point . I don't know which file this is, something around 950~960, I'm sure someone will figure out the exact file. Note that if you did not move any coins post fork yet, you do not need to delete anything.
Important: If you did not move any coins post fork yet, you do not need to delete anything.
But if you do, you need to delete enough for the newest blocks such that your transactions post fork are obscured.
If you use armory on Linux, delete blocks in ~/.bitcoin/blocks
Quote
4) With this done, you want to sync a fresh DB against this blockchain folder. Do not run a node against it, just start ArmoryDB against this folder, then start ArmoryQt, it will pick up on that DB.
Basically, instead of clicking on the armory icon, go to /usr/local/bin to run ArmoryDB and armory manually.
But I found it difficult, what I did instead was to, while Armory was running, go to the Help menu and choose to rescan and rebuilt data base. A pop up will show up asking to confirm that you want to rescan and rebuild the next time armory starts and that it will take a lot of time. Accept.
Restart armory, and use the terminal to shut down bitcoind by running pkill bit. This way armory will remain offline
Quote
5) Once you're synced (it will show you as offline), you can create your transactions. You should pick utxos manually and keep track of them so as to not create conflicting transactions.
You need to be in expert mode. While armory is running, go to the user menu and select expert. Click on your wallet and select to send bitcoin. Enter the bitcoin cash address and the amounts and the fees (fees for the cash network are x10 lower, I used 20 satoshis per byte and it got confirmed really quickly.
Quote
6) Once your tx is ready, make sure to create it as unsigned, even if your private keys are online. You will get a blob of text that you can feed back into the offline tx GUI. There you will get to sign the tx (make sure to pick the BCH miner), and you will get another blob of text. On the right side of that dialog, you will have a button that's called "Copy Raw Tx (Hex)". This is what you are after. This hex string is your signed tx.
The glob of text is a rectangular block. Copy that, and then click on Offline Transactions on the main armory window (I spent a lot of time looking for this on the menu bar and was trying to figure out if Broadcast Raw Transaction was what I wanted, but no it isn't, the button is in the main window).
Paste the block, click sign, choose the signer and in the window where you pasted the glob, there is another button like goatpig said "Copy Raw Tx (Hex)". Click that and you get a long string.
Quote
7) With the signed tx, all you need now is some online service that will broadcast it to the BCH network for you, and voila.
Paste that here: https://blockdozer.com/insight/tx/send
And you are done.
