I have run into the same problem trying to import private keys from Multibit and Blockchain.info
Other topics:
http://bitcoin.stackexchange.com/questions/24632/import-private-keys-from-multibit-into-armory
https://bitcointalk.org/index.php?topic=680355.0
The ones from Multibit that fail start with an L or K.
The single one from Multibit that succeeds starts with a 5 and is probably the oldest address I have.
The ones from Blockchain.info all fail and don't start with a L or K or 5.
I could use the software from https://github.com/pointbiz/bitaddress.org to convert the compressed private key to an uncompressed one, but that would render my funds unusable. An uncompressed private key has an uncompressed public address. My funds are at the compressed public address. On the uncompressed address my funds are zero: I tested this by importing the uncompressed private key in Armory and waited for the scan to complete.
Importing the hex-version of the private address reveals yet another public address. Could be an error from bitaddress.org ?
P.S.: There is some sort of a memory-problem in Armory: Almost all of 16GB physical memory was being taken after the rescan. Returned to normal after shutting down Armory. Another private key import gave the same problem again.
When I enter the private keys from Blockchain.info in the bitaddress.org-software I get an error saying it is not a valid private key.
I was under the impression that the combination "public address / private key" was universal in Bitcoinland. That the same keys could be used in all clients. This is not the case however.
I could transfer the funds to a new address generated in Armory. However, there is a possibility that Bitcoins will still be send to the old addresses.
Will Armory be able to import compressed private keys in the new version?
Other topics:
http://bitcoin.stackexchange.com/questions/24632/import-private-keys-from-multibit-into-armory
https://bitcointalk.org/index.php?topic=680355.0
"Private keys associated with compressed public keys are 52 characters and start with a capital L or K."
The ones from Multibit that fail start with an L or K.
The single one from Multibit that succeeds starts with a 5 and is probably the oldest address I have.
The ones from Blockchain.info all fail and don't start with a L or K or 5.
I could use the software from https://github.com/pointbiz/bitaddress.org to convert the compressed private key to an uncompressed one, but that would render my funds unusable. An uncompressed private key has an uncompressed public address. My funds are at the compressed public address. On the uncompressed address my funds are zero: I tested this by importing the uncompressed private key in Armory and waited for the scan to complete.
Importing the hex-version of the private address reveals yet another public address. Could be an error from bitaddress.org ?
P.S.: There is some sort of a memory-problem in Armory: Almost all of 16GB physical memory was being taken after the rescan. Returned to normal after shutting down Armory. Another private key import gave the same problem again.
When I enter the private keys from Blockchain.info in the bitaddress.org-software I get an error saying it is not a valid private key.
I was under the impression that the combination "public address / private key" was universal in Bitcoinland. That the same keys could be used in all clients. This is not the case however.
I could transfer the funds to a new address generated in Armory. However, there is a possibility that Bitcoins will still be send to the old addresses.
Will Armory be able to import compressed private keys in the new version?