Using Armory on the BCH chain

[HCP]

Should I sweep or import the old wallet in to electron cash using one of the private key export types in Armory? (will sweeping prevent me claiming any other forked coins like bitcoin gold going forward?)

As long as you had BTC on those private keys when "XYZ" fork happened, you will be able to claim "XYZ" coins, regardless of what you do with "ABC" or "LMNOP" coins

Any idea which of the private key types are needed?

You need the "Private Key (Plain Base58)" keys... These are also known as "WIF" (Wallet Import Format)... they should start with a "5", an "L" or a "K". I think Armory uses "uncompressed" keys... so they're most likely going to start with a "5".

[hopebit]

I'd replace 0.96 with the latest version (0.96.3.992 as of right now) unless you have specific reasons for using specific versions, but yes, that should work.

I actually put a TAG=<whatever version> at the beginning, and then $TAG where needed.
What I wanted to know was:
- why the two lines "git submodule init" and  "git submodule update" are repeated twice in the instructions, isn't one time sufficient, and where is the best position to put them in the script
- previous post by goatpig seemed to suggest that the line: "git tag -v v0.96" goes before "git checkout v0.96" so I wanted to make certain, if recommended way is different from instructions on the web site, what is the suggested order of the instructions, and possibly remove the redundant ones

why build Armory?

I thought you should never trust precompiled binaries and if you care about your coins, you should always build from source?

[PsyMan2000]

Thanks HCP

So I take it that means I can sweep the same ex BTC wallet in to multiple forked coins but just never use the wallet again for BTC

Much appreciated

The mud in the water is slowly clearing 

PsyMan

[droark]

why build Armory?

I thought you should never trust precompiled binaries and if you care about your coins, you should always build from source?

Oh no, it's fine! I just wanted to make sure you had an actual desire to compile and weren't just getting in over your head. I think the directions are fine as long as the correct tag is used. The git submodule thing, AFAIK, is more of an insurance policy whenever switching branches/tags. The FCGI code hasn't really changed since it was introduced but other submodules could change between versions if they're ever introduced.

[Armory non geek]

What is the easiest way to claim post fork BCC from an Armory wallet?  I have moved the coins post fork.  Is it as simple as running armory with a complete BCC node and then sending using the BCC signer?

Yes. That said, I highly recommend keeping the Armory database separate from the Core DB, otherwise you'll have problems. This link explains how to set up the paths, which you'll need for both the Armory DB and the Bcash chain.

copy 3 quotes by PeZ from Dec 20

<I always ran bitcoin-qt and Armory separately, and I don't mess with the Armory settings by using a shortcut...
"D:\Program Files (x86)\Armory\ArmoryQt.exe" --datadir="D:\ArmoryData" --satoshi-datadir="D:\BitcoinData"
I renamed the database folder in ArmoryData to database.old to save it.
Substitute Qt with DB if you are following the instructions.
You don't want Bitcoind running if you are following the first page instructions.>

<This is what I do/did. I had previously emptied my BTC from my main wallet. Some BCH got stuck as change when I transferred it away, so I installed Bitcoin ABC in a separate directory.Uncheck the box that lets Armory run bitcoin core. It will find it, if it is running - as long as your firewall is not blocking it.
Keep separate directories for Bitcoin ABC data and Bitcoin Core data and copy the Armory wallet to another directory, but remove the database directory for when you use it with Bitcoin ABC.
If you want to run Bitcoin, do it with a shortcut e.g.
"D:\Program Files\Bitcoin\bitcoin-qt.exe" -datadir="D:\BitcoinData" -disablewallet
When synced, run Armory with the shortcut that I mention in the previous post.
Follow the directions on the first page.
Not sure if this is the easiest method, but it worked. I am using Windoze, but other OS's should have something similar.>

<With both Bitcoin Core and Bitcoin ABC, I unchecked RBF, used 1 S/B fee and copied the Hex data and used http://blockdozer.com/insight/tx/send to submit the transaction. I don't know if it is required, but I would empty the wallet of BTC before messing with the BCH contents.

Yes, when you use Bitcoin ABC you would see the BCH contents, but my wallet was completely empty of BTC.?>

---

Then quote from JoJo69 from January 19

<OK, my report, as promised.

The ABC rollback to 0.16.1 did the trick!

I did have to rebuild the Armory DB.

I have added the lines to the bitcoin.conf file since, but that was not the issue in this case.   So, to summarize for the benefit of others.

>move all BTC out of any wallets you wish to claim BCH from

>back up your BTC blockchain, ABC uses the same default install paths (borderline malicious behavior IMO but there it is.

>back up your Armory DB

>install Bitcoin ABC v0.16.1, NOT v0.16.2 !  Allow it to fully sync.  Without an old pre-fork blockchain backup or some kind of pruned backup this will take a couple days at least.

>install Armory 0.96.3.922    RC3

>deal with your pathing to point your Armory bookmark to your new BCash blockchain

>Armory file  settings  uncheck "let Armory run Bitcoin Core/bitcoind in the background"

>close armory

>delete armory\databases

>verify Bitcoin ABC is running and fully synced

>launch Armory and let it build your new DB.  This will take some hours, be patient.  It may seem hung on 99% 2 seconds remaining or something like that for a loooong time, just let it run.

>when it is finally done it should show your expected BCH balances (you moved your BTC already right?) and report "connected" in purple in the lower right corner

>set Armory to "expert" mode   user   expert

>click "send bitcoins" and make up your transaction as usual remember to uncheck "enable RBF" in the lower right

>click through and SELECT THE BCH SIGNER AS DETAILED IN THE OP OF THIS THREAD!!!

>click to broadcast, that's it...worked for me

If I screwed any of this writeup let me know guys and I will edit

Thank you all so much for the help!!>



Then from January 21:

<I found the binaries at https://download.bitcoinabc.org/0.16.1/
will link in above post>

---



I recognize that much of my questions have been addressed in the prior discussions of this thread.
I have copied many of them above to hopefully have a relatively complete listing for my questions:


____

Thank you to all the developers for all your collective efforts over the past 6 months, and the continued development of this thread.

I continue wrapping my head through the various posts of this thread and continue to remain unclear.


One Win 10 x  64 desktop computer (with two hard drives) dedicated to Armory wallets
0.96.3992 with BC Core 0.15.1 all fully sync'd to the default locations on the C drive.

--- Based on the various questions and comments through this thread,
Is it necessary to install and sync an added 0.15.1 to the Data Drive?
or does one install and sync Bitcoin Unlimited or other database to the Data Drive?

Does it remain necessary to manually delete the database blocks
immediately below block 478559 from the newly installed database (on the 2nd Data Drive)?

Does one then redirect the Path of the existing 0.96.3992 (already on the C drive)
to address the the newly installed database on the data drive. Or, does one install
a new 0.96.3992 directly to the Data Drive (if so how does one distinguish between
each of their respective icons on the monitor screen)?   

----

signers will always be an off line laptop. 


Thank you all for the development of these work around procedures
and for your suggestions re my inquiries, as I desire to correctly and securely
effect this separation of BCH from the legacy BTC.

[jojo69]

I think I get the essence of your question non geek.

First thing, I am assuming that you are now in this thread because you and your friend successfully accessed your wallets and moved the BTC.  Congratulations!  I know that was a bit of a struggle.

It is not necessary to install a second instance of Armory, you just need to point your existing install to a fully synced and running ABC or BU node with the arguments in your shortcut.

No, you do not install an added Core, yes you install a BCH node ABC or BU.

I was not comfortable myself performing the pruning on the chain to save time so I just let my ABC install download its whole chain so I can't help you there, it took almost 3 days I think.

[PsyMan2000]

A big thanks to all who helped me split my BCH, I ended up importing the private keys from my old Armory wallet in to a new blockchain.info wallet in the end and then sending to coinfloor to sell.

electron cash turned out to be a bit of a nightmare (wrong password issues when trying to send the BCH after importing the keys and stuck syncronising) using blockchain.info did mean importing the addresses/keys one by one but a bit of copy/paste gymnastics and it was all done.

I couldn't have done it without the advise in this thread so thanks all. I have learned more about wallets doing this than I ever did back in the mining days LOL

PsyMan

[rebelxxx]

Not sure if its for any help, but I just want to say that after procrastinating for several months I finally accessed my BCH.
I want thank this thread for all help.

I chose to send BTC to new wallet.
Export the private keys (base58 i think?) and then delete all the text and spaces except for the keys starting with 5.
Electron cash wallet, where i chose wallet/p keys/sweep , and paste the list of private keys.
After that I had to send the BCH to one of the adresses on Electron wallet, allthough I could maybe have just sent them straight to the nano S.
Anyways installed BCH app in chrome and in ledger manager and after that sent the BCH from electron to an adress on the ledger nano s .

Waiting for confirmations at the moment but it do seem like it worked.
So glad this is finally done and now I just need decide what to actually do with the bch..

[alomar]

Not sure if its for any help, but I just want to say that after procrastinating for several months I finally accessed my BCH.
I want thank this thread for all help.

I chose to send BTC to new wallet.
Export the private keys (base58 i think?) and then delete all the text and spaces except for the keys starting with 5.
Electron cash wallet, where i chose wallet/p keys/sweep , and paste the list of private keys.
After that I had to send the BCH to one of the adresses on Electron wallet, allthough I could maybe have just sent them straight to the nano S.
Anyways installed BCH app in chrome and in ledger manager and after that sent the BCH from electron to an adress on the ledger nano s .

Waiting for confirmations at the moment but it do seem like it worked.
So glad this is finally done and now I just need decide what to actually do with the bch..

thanks for this.  seems like a potentially easier, more streamlined approach to claiming BCH.  as long as you send the BCH immediately to it's final destination, i guess.  let us know that it definitively worked!

[sbj175]

I'm not having any luck importing Armory private keys into BitcoinABC. I picked some keys corresponding to addresses with no balance just to test that I could in fact import them into BitcoinABC, but it is returning an "invalid encoding" error. Supposedly, Bitcoin Core, and therefore BitcoinABC, requires WIF formatted private keys, which I thought these were. When exporting from my Armory wallet, I chose the "Plain Base58" option - is that not what WIF format is?

[gangtraet]

As I remember, there is a prefix ending with a : which you should manually remove.  Also, if there are spaces in the keys, they need to be removed.

[sbj175]

There were no spaces and no ":" chars. All keys started with 5 and looked like I would expect for a base 58 encoding.

[alomar]

There were no spaces and no ":" chars. All keys started with 5 and looked like I would expect for a base 58 encoding.

i'm having the same issue trying to claim BTG.  Base58 private key not accepted by Coinomi.  are the Base58 private keys in Armory in the WIF?

edit:  nvm, working

[jojo69]

what was the issue alomar?

[alomar]

what was the issue alomar?

none, the Base58 keys translate perfectly fine in Coinomi.  i must've made a typo manually entering.  figured out how to copy/paste, which worked.  amazing how you can get typed errors even when it looks perfectly fine.

[HCP]

amazing how you can get typed errors even when it looks perfectly fine.

This... Spent a good 10 minutes yesterday getting JSON errors while trying to sign a transaction manually for someone who needed to "rescue" some tokens sent to a MultiSig address...

Took me that long, after checking it character by character FOUR times, to spot that I had "}]" written as "]}"

Copy/paste FTW!

[justmyname]

So. I have moved all my BTC off of my ARMORY wallet. I'm trying to extract the BCH from the ARMORY wallet. I'm using Trezor as my heart can't take anymore of this. 

Should I 1st make an attempt of putting ARMORY into advanced mode and signing for the BCH.

Or should I download the BCH ABC wallet. Remove completely Bitcoin core including hidden files. Then install the BCH ABC and somehow point Armory to the ABC node?

[jojo69]

So. I have moved all my BTC off of my ARMORY wallet. I'm trying to extract the BCH from the ARMORY wallet. I'm using Trezor as my heart can't take anymore of this. 

Should I 1st make an attempt of putting ARMORY into advanced mode and signing for the BCH.

Or should I download the BCH ABC wallet. Remove completely Bitcoin core including hidden files. Then install the BCH ABC and somehow point Armory to the ABC node?

you have to run Armory on top of a synced and running ABC node, review this thread some.

[justmyname]

So. I have moved all my BTC off of my ARMORY wallet. I'm trying to extract the BCH from the ARMORY wallet. I'm using Trezor as my heart can't take anymore of this. 

Should I 1st make an attempt of putting ARMORY into advanced mode and signing for the BCH.

Or should I download the BCH ABC wallet. Remove completely Bitcoin core including hidden files. Then install the BCH ABC and somehow point Armory to the ABC node?

you have to run Armory on top of a synced and running ABC node, review this thread some.

Do I have to remove the regular Bitcoin Core wallet first? When I try to install the ABC wallet it says data corrupted do you want to re synch? That means it's probably trying to use the BTC block chain?   

[Holliday]

So. I have moved all my BTC off of my ARMORY wallet. I'm trying to extract the BCH from the ARMORY wallet. I'm using Trezor as my heart can't take anymore of this.  

Should I 1st make an attempt of putting ARMORY into advanced mode and signing for the BCH.

Or should I download the BCH ABC wallet. Remove completely Bitcoin core including hidden files. Then install the BCH ABC and somehow point Armory to the ABC node?

you have to run Armory on top of a synced and running ABC node, review this thread some.

Do I have to remove the regular Bitcoin Core wallet first? When I try to install the ABC wallet it says data corrupted do you want to re synch? That means it's probably trying to use the BTC block chain?  

If you are feeling frisky enough, you can use a config file to place (access) the block chain (either of them) in a non-default location.