MultiBit: Corrupted wallet file?

[Nunud]

Hi!

Something happened yesterday to one of my wallets... After freezing, MultiBit wouldn't quit, so i forced it to quit... It's like Crtl Alt Sup on windows I guess.

And then when I relaunching it, one of my wallet wouldn't open. MultiBit says "Error 1"...

The file is still there, but it's unusable.

It's not that bad, since that wallet was almost empty, but I'd like to know a way around this, in case it happens to a "real" wallet...

Did anyone of you guys encounter this Error 1 thing? 

[1714117755]

1714117755

[1714117755]

1714117755

[1714117755]

1714117755

[jim618]

You can raise a bug on the MultiBit github issues page here:

https://github.com/jim618/multibit/issues

If you attach your log files to the bug report (in your installation directory/log, called multibit_debug.log and multibit_console.log) I will have a look.

Do you have a backup of your wallet or an export of your private keys you can use ?


I am currently working on some enhancements to the 'infrastructure ' in MultiBit, which includes an improved wallet format but that is probably a month away from release.

I have in the past extracted private keys at the byte level from MultiBit wallets (a how-to is described here : https://bitcointalk.org/index.php?topic=43616.msg909038#msg909038  ) so make sure you keep the problematic wallet.

[Nunud]

Hi!

Thanks for the quick reply...

The thing is I'm not certain it's specifically a MultiBit bug... It happened after I lost my internet connexion during synchronisation with the network.

Plus you have to register at github to report an issue...

Like I said, the damage is not very serious. It's just that it would be good to know what to do to prevent this sort of thing from happening...

I did have a backup, but since it's two days old, it's only relevant to the wallets I didn't touch since...

Is it OK if I send you the log files in a PM here instead of github?

[jim618]

Sure, send me the logs via PM.

If you have backups you should be able to use them to get all the BTC for any private keys you had at backup time (it will not know about new private keys / receiving addresses that you created since your backup time).