Topic: Passphrase Problems (Read 1225 times)
Sure enough, file was corrupted. I'm not sure how that happened, but I'm guessing it was my fault (manipulated it with bitcoinqt running or something). File was 100KiB bigger than it needed to be (imported all addresses to new wallet, ran rescan, encrypted with same key, new file is 100KiB smaller, presumably with 100 more addresses (new keypool).
Unfortunately, I have no clue, but I can tell you I sent all of my coins out of it by importing the relevant keys into a new wallet and sending the BTC from there, and bitcoin-qt reflected this change accurately in the old wallet, live. I will do some testing and report back.
This looks like some sort of strange corruption occurred in your wallet; can you provide any more details, for example what you did to get it in this state?
Anytime I enter my passphrase in bitcoin-qt on Windows, it crashes (I can't even run bitcoin-qt on Linux). When I run bitcoind on Windows or Linux and use walletpassphrase or walletpassphrasechange, I get this error:
error: {"code":-1,"message":"CKey::SetSecret() : secret must be 32 bytes"}
The same wallet passphrase works fine on the same wallet with pywallet.
This is the second time I have had passphrase problems (but the first time I have posted about them). Is there some set of passphrase guidlines in order to avoid situations like this?
error: {"code":-1,"message":"CKey::SetSecret() : secret must be 32 bytes"}
The same wallet passphrase works fine on the same wallet with pywallet.
This is the second time I have had passphrase problems (but the first time I have posted about them). Is there some set of passphrase guidlines in order to avoid situations like this?
Jump to: