help, recovering from wallet.dat

[etotheipi]

I might take a shot at this, since I have a very similar encryption scheme in the client I'm about to release.  It's a pretty healthy bounty, too

The only thing I don't know for sure, is where to find the nDeriveIterations value.  I'm sure it's stored in the wallet file somewhere...

[mcorlett]

The only thing I don't know for sure, is where to find the nDeriveIterations value.  I'm sure it's stored in the wallet file somewhere...

That's right. It defaults to 25000, if I'm not mistaken.

Good luck!

[etotheipi]

25,000 is the minimum.  The client tests the speed of your system and determines how much computation can be done in ... 0.1s?  If it's 40,000 SHA512 hashes, it uses that.  If it's 10,000, it uses 25,000.  i.e.  max(computeSysSpeed(), 25,000)

So that value must be stored in the wallet file somewhere, I just don't know where...

mcorlett... if you figure this out, I think I have all the other pieces it would take me a couple hours to put together a script that would take nDeriveIter and the passphrase, and spit out a list of pub/priv keypairs... maybe we could negotiate a splitting of the bounty for this? 

[tlhonmey]

When and if you get your coins back, the first thing to do with the new wallet file is to run the client with the parameter -keypool=10000.  This will change the number of pre-generated addresses from the pitifully small 100 that it is by default, to a large enough quantity that your backup copy should be good for at least a year or two.  10k addresses puts the wallet size at about 70Mb, which is large, but not unbearably so, and the inconvenience is far less than that of losing coins.  It may take a half hour or so to generate them, depending on how fast your machine is, but after that it will run as normal.