rBQ3oC6fnrRZauvHBDdT1u7sDkYrS57mL2

rBQ3oC6fnrRZauvHBDdT1u7sDkYrS57mL2

1.Close Electrum, then backup electrum.dat

2.open the file in a hex-editor

3.Find 'console-history' in the file. It should look something like this :
...   0ed8', 'console-history': [u"importprivkey('5KJvsngHeMpm884wtkJNzQGaCErckhHJBGFsvd3VyK5qMZXj3hS')", u"dumpprivkey('1JwSSubhmg6iPtRjtyqhUYYH7bZg3Lfy1T')"], 'num_zer  ...


4.Carefully remove all fields involving 'importprivkey', e.g. the above history after correction should look like:

...   0ed8', 'console-history': [u"dumpprivkey('1JwSSubhmg6iPtRjtyqhUYYH7bZg3Lfy1T')"], 'num_zer  ...

- Alternatively you may clear entire history like this:

...   0ed8', 'console-history': [], 'num_zer  ...

5.Save electrum.dat.

Note: If you want to import any private keys, I suggest that you use import button in settings panel.

If you import a private key into an Electrum wallet, and also assign a password for that wallet to be encrypted, because of a bug, that private key probably will not be safe yet.

You could either import a private key through the setting panel, or do that from the console.
The problem is that if you have used the console, the history of console which is saved in your 'electrum.dat' file, will reveal entered commands in PLAIN TEXT !!!

So anybody with access to your electrum.dat file could get those imported private keys in PLAIN TEXT, although there is an encrypted version of that key saved in the file as well.


Note: By 'import from console' I mean something like this:
     >>importprivkey('5KJvsngHeMpm884wtkJNzQGaCErckhHJBGFsvd3VyK5qMZXj3hS')
     this command would be saved in 'electrum.dat'