Author

Topic: Help with encrypted wallet.dat. Corrupted? (Read 1329 times)

sr. member
Activity: 322
Merit: 250
December 09, 2013, 05:35:53 AM
#7
As a follow up I was able to discover the actual passphrase by using the ruby script from this thread https://bitcointalk.org/index.php?topic=85495.300.

Much thanks to all who helped. It was a stressful and frustrating experience - from which I learned a lot. Smiley
Wow! I'm glad you got your coins back!
I was just about to tell you you should try that script.
tjc
full member
Activity: 145
Merit: 100
December 08, 2013, 09:40:16 PM
#6
As a follow up I was able to discover the actual passphrase by using the ruby script from this thread https://bitcointalk.org/index.php?topic=85495.300.

Much thanks to all who helped. It was a stressful and frustrating experience - from which I learned a lot. Smiley
legendary
Activity: 1890
Merit: 1078
Ian Knowles - CIYAM Lead Developer
December 07, 2013, 02:18:20 AM
#5
Loosing those 42 coins has been hard to swallow. At least knowing why will hopefully let me get some sleep for the first time in two days.

Ouch - a very hard way to learn - if you have any idea what your old password was then you might have some luck with a wallet recovery service.

In the meantime get some sleep and try your best to relax (it's much harder to be of much help to yourself when you are overly tired).
tjc
full member
Activity: 145
Merit: 100
December 07, 2013, 02:12:23 AM
#4
[quote/]Sounds like you are just not using the correct (meaning older) passphrase for your backed up wallet.[/quote]

That is what I have finally come to realize. Unfortunately, at that time I would not have grasped the consequence of resetting the passkey (ie re-encrypting the wallet.dat) and not creating a new backup of wallet.dat.

If this is indeed the mistake I made, I have only a vague recollection of doing it and certainly no record of the older passphrase.

Loosing those 42 coins has been hard to swallow. At least knowing why will hopefully let me get some sleep for the first time in two days.
legendary
Activity: 1890
Merit: 1078
Ian Knowles - CIYAM Lead Developer
December 07, 2013, 01:45:19 AM
#3
First encrypted copy would not decrypt with the new passphrase.

Why would you expect a wallet encrypted with an old passphrase to work with a new one?

Sounds like you are just not using the correct (meaning older) passphrase for your backed up wallet.
tjc
full member
Activity: 145
Merit: 100
December 07, 2013, 01:41:49 AM
#2
I think I figured out something that could replicate my scenario.

1) encrypted wallet
2) copy wallet.dat
3) change passphrase
4) did not make new copy of wallet.dat

First encrypted copy would not decrypt with the new passphrase.

Can someone confirm this would occur this way?

Thanks
tjc
full member
Activity: 145
Merit: 100
December 06, 2013, 01:10:32 PM
#1
Can a wallet.dat file be corrupted in a way that it does not throw an error when loading bitcoin-qt but fails to recognize the passphrase?

I created two offline wallets in July. Went to access them and the recorded passphrases are incorrect for both of them. I never printed the private keys so now can't access either wallet. I know I could have typed incorrectly or cut and pasted improperly when I created the pass-phrase and I am definitely working on that possibility.

For this thread I am looking for any insight into other technical problems that may have occurred that make the wallet.dat file unable to recognize the passphrase. I had multiple copies of the wallet.dat stored in multiple locations. They all work in terms of making coins appear (about 42 in total) but as I said they do not recognize my expected passphrase. By the way the passphrase is 20 char random generated by the LastPass password generator.

Any and all ideas are welcomed.

Thanks
Jump to: