Title: Key question on a core 0.14.2 wallet Post by: philipma1957 on August 02, 2017, 01:19:34 AM I have a mac mini running a 0.14.2 wallet and I want to find keys and export an address on the wallet I was searching on private keys .. found this. I bolded what I want to do will it work for 0.14.2 core on a mac running 10.10.5 os Im on mac os. Also - where does Bitcoin-Qt save the main wallet.dat file that it uses? (Im a fairly new Mac user too so still working out where the app files are etc) Go to /Library/Application Support/Bitcoin to find bitcoin's data. wallet.dat lives there. To dump a private key, do thus: 1.) From Menu, click Help > Debug Window 2.) Click on Console 3.) type dumpprivkey [bitcoin address] Quote I keep hearing really good things about Armoury ... so do you justsend your coins from Bitcoin-qt to yourself in your new Armoury wallet? T. Or you could import the private key you just dumped into Armory. I assume Armory has an import key command. this still true for a mac say with 0.14.2 core I could use a way to get one address's key's as I think i need them Title: Re: Key question on a core 0.14.2 wallet Post by: HCP on August 02, 2017, 03:12:31 AM Have you tried simply going into Bitcoin Core debug window and using the "dumpprivkey" command? ???
I see no reason why it wouldn't work... it is part of Bitcoin Core which is fairly standard across all the OS platforms... Title: Re: Key question on a core 0.14.2 wallet Post by: philipma1957 on August 02, 2017, 03:18:56 AM Have you tried simply going into Bitcoin Core debug window and using the "dumpprivkey" command? ??? I see no reason why it wouldn't work... it is part of Bitcoin Core which is fairly standard across all the OS platforms... at this point I have not done a thing except do research as I may want to spilt the bcc from the btc. I do not want to rush to do it as doing it correctly is very important. Title: Re: Key question on a core 0.14.2 wallet Post by: HCP on August 02, 2017, 03:37:58 AM Fair enough...
If you have Bitcoin Core, you can download and install the BitcoinABC software (it uses the same wallet.dat format at the present time), rather than exporting (and potentially exposing) private keys. There are some necessary precautions that you will want to use tho, as by default it attempts to use the Bitcoin Core datadir's so it could "corrupt" your Bitcoin Core install, by messing with the block files... Prior to the fork, I simply copied my entire Bitcoin Core datadir folder... and called it "BitcoinABC"... I start the BitcoinABC client with the -datadir="E:\BitcoinABC" argument and (after it actually found some ABC nodes to connect to) it is syncing nicely with the ABC chain... with it's own copy of wallet.dat. Unfortunately, I'm not sure if creating a copy of the datadir and blocks will work post-fork, as there are blocks that are "invalid" on the BCC chain... which may cause ABC to choke? It's possible that a reindex will just remove the "invalid" blocks after Block #478558... and then it will resync from there... but I can't guarantee that. Also, it is recommended that you actually create a new wallet for Core, send all your BTC there... then use a copy of the OLD pre-fork wallet.dat with ABC... that way, should the ABC software leak your wallet file and/or keys, only your BCC is at risk, because all your BTC are already in a different wallet/addresses. |