There's a BUG in Version 0.8.1-beta Bitcoin QT. It will lock up if you add an externally generated address into the wallet when you go to associate its private key to it. It works but it locks up and if it does not crash you have to kill it taskmanager and restart.
Anyone know where I can report this?
Topic: Can't dump private key from unlocked encyrpted wallet. (Read 459 times)
Nevermind - it seems to be working now. Maybe I had the debug widow scrolled too high and missed the method call back result. I see it now.
I got this sinking felling I lost my private key of my very first bitcoin address that has a small balance of bitcoins in it.
Need some help to make sure I have a private key still.
Here's what I have done:
1) My pool sent some bitcoins to me just fine a day ago at my only public wallet address.
2) I am tinkering with vanity addresses and generated a cool one.
2a) I was able to unlock my encrypted wallet to import the new vanity address fine
2b) After some syntax snafu's I was able to finally associate the vanity address private key to that new vanity address (I presume the label is what lets bitcoin client's debug console associate the private key to address)
2c) I dumped the private key for the new vanity address to confirm that it was all good and it is.
2d) I relocked the wallet then tried to dump the first bitcoin address's private key - BUT NO JOY
2e) I unlocked it all again and repeated 2d - again NO JOY - nadda - no key
2f) Relocked my wallet
Client still shows proper balance in wallet
Am I missing the boat here? I am assuming that each bitcoin address uses its own unique private-public key pair and each address has its own private key. Did my importing a new address and private key wipe out my other private key and its pool of pre-reserved keys such that they are invalidated?
Need some help to make sure I have a private key still.
Here's what I have done:
1) My pool sent some bitcoins to me just fine a day ago at my only public wallet address.
2) I am tinkering with vanity addresses and generated a cool one.
2a) I was able to unlock my encrypted wallet to import the new vanity address fine
2b) After some syntax snafu's I was able to finally associate the vanity address private key to that new vanity address (I presume the label is what lets bitcoin client's debug console associate the private key to address)
2c) I dumped the private key for the new vanity address to confirm that it was all good and it is.
2d) I relocked the wallet then tried to dump the first bitcoin address's private key - BUT NO JOY
2e) I unlocked it all again and repeated 2d - again NO JOY - nadda - no key
2f) Relocked my wallet
Client still shows proper balance in wallet
Am I missing the boat here? I am assuming that each bitcoin address uses its own unique private-public key pair and each address has its own private key. Did my importing a new address and private key wipe out my other private key and its pool of pre-reserved keys such that they are invalidated?
Jump to: