Quote from: E&G on February 21, 2013, 01:16:54 AM

Quote from: etotheipi on February 21, 2013, 01:07:49 AM

Quote from: E&G on February 21, 2013, 01:03:59 AM

Quote from: etotheipi on February 21, 2013, 12:56:09 AM

Quote from: E&G on February 21, 2013, 12:52:56 AM

sorry i missed the memo, is there an easy conversion tool for importing old wallet.dat files into armory?

the only way i know of currently is dumping keys with pywallet and then importing, but this seems like a pain especially with a very large wallet.

That actually won't work either, because the current wallet format of Armory (and underlying library code) doesn't accommodate compressed public keys. Trying to import them will just cause errors. As I keep mentioning the new wallet format: it will handle compressed public keys -- in fact it will use them by default. But until then, the support isn't there.

For now you're just going to have to send the funds through the blockchain to get it to the new wallet. I recognize not everyone finds this solution satisfactory (they'd like to take some addresses with them), but it's the best I can do for you until the new wallets are complete (which unfortunately have become slightly lower priority in favor of upgrading Armory's resource management).

thanks for the quick reply... but what do public keys have to do with anything?

dumping a list of private keys and importing those private keys into armory won't work?

Since a bitcoin address is the hash of the public key, if you use a compressed public key you get a different address than using the same, uncompressed public key. As such, the same private key can be associated with two different addresses (one for compressed and uncompressed). Right now, Armory would compute the wrong address, even if it could uncompress the keys.

hmm... didn't this behaviour change in the satoshi client at some point?

i.e. are you assuming that my wallet.dat is using compressed public keys when in fact it could be from an era before that was the default?

i wouldn't know how to check

It switched over in satoshi client version 0.6. That was a about a year ago.