Author

Topic: Can't Import Private Keys from Bitcoin Core (Read 549 times)

newbie
Activity: 27
Merit: 0
September 23, 2017, 09:51:33 AM
#8
Thanks for your help, guys - I guess no one can import private keys from Core until support for compressed private keys is added?
sr. member
Activity: 471
Merit: 252
September 23, 2017, 09:39:16 AM
#7
could this be why Armory isn't seeing any balance on those addresses?

Yup, this is the issue. You need to wait until goatpig adds support to Compressed PrivKeys. He told me in another thread that he would add it probably in 0.97 ;-)
HCP
legendary
Activity: 2086
Merit: 4361
September 23, 2017, 09:24:35 AM
#6
Is your Bitcoin Core fully synced and is your Armory wallet properly synced with Bitcoin Core?

Does Armory show "Connected" in the bottom right of the Armory window with the correct number of blocks? Current block height is 486,629
newbie
Activity: 27
Merit: 0
September 23, 2017, 09:13:02 AM
#5
Thanks for the help - I've run the listunspent command, and it's not an issue with change addresses. The Armory wallet is showing an empty balance, despite having imported the keys from Core.  Huh
HCP
legendary
Activity: 2086
Merit: 4361
September 23, 2017, 08:51:51 AM
#4
I converted the private keys into hex format using bitaddress.org, and imported them successfully into an Armory wallet. I've rescanned the transaction history, but the wallet is appearing empty. The Core wallet only had two keys to export; am I missing some invisible change addresses or something (I've made multiple transactions in and out of the Core wallet)?
Quite possibly you are missing the change addresses... you can find all your unspent outputs by using the "listunspent" command in Bitcoin Core.

You'll see all the addresses that contain coins... including change Wink
newbie
Activity: 27
Merit: 0
September 23, 2017, 07:54:04 AM
#3
Also worth noting: when I imported the private keys into Armory, the corresponding public keys were different than in Core (something to do with compressed/uncompressed Wallet Import Files generating different public keys) - could this be why Armory isn't seeing any balance on those addresses?
newbie
Activity: 27
Merit: 0
September 23, 2017, 07:52:15 AM
#2
I converted the private keys into hex format using bitaddress.org, and imported them successfully into an Armory wallet. I've rescanned the transaction history, but the wallet is appearing empty. The Core wallet only had two keys to export; am I missing some invisible change addresses or something (I've made multiple transactions in and out of the Core wallet)?
newbie
Activity: 27
Merit: 0
September 23, 2017, 04:30:38 AM
#1
I've got a list of private keys from Bitcoin Core 0.13.1, but when I try to import them to Armory, I get the message "The private key you have entered is actually not valid for the elliptic curve used by Bitcoin."

All my private keys start with either an "L" or a "K", so it looks like they're in Base58 Wallet Import Format, associated with compressed public keys.

How can I import these into Armory?

Thanks!
Jump to: