Pywallet 2.2: manage your wallet [Update required]

[bumblebee33]

You should do a --recover of your damaged partition. I also accidentally formatted my only backup with wallets. Once the wallets are recovered with recover software like Recuva,... they seem to get damaged in some way. I am still not finished recovering them completely, but --recover is the first step.

What I used is:

pywallet.py --recover --recov_size 931Gio --recov_device f: --recov_outputdir d:\recovered


It will ask you then to put in a new password (for the finished encrypted wallet.dat). That is where I found a bug. Whatever password I chose, at the end I am able to get my coins to show up, but I cannot send them because the password I chose when starting the --recover does not get accepted. First I thought I misspelled something and started the whole process again. Each time it takes about 6 hours... But even when I was absolutely correct with my password, it still would not accept the password at the specific wallet for decryption.

Is there another step I can do?

I also tried the --dumpwallet command with the recovered wallet, but I am not able to find the correct address that was used on the wallet I am trying to recover.

pywallet.py --dumpwallet --datadir d:\recovered --wallet wallet.dat --otherversion=34 > dump.txt

(I have tried otherversions 34 - 37)


That lists all key pairs, but none of them is the correct one I am looking for. What am I doing wrong? Obviously the right keys must be in the recovered wallet, as I am able to see the correct balance once I am doing the -rescan command. But when I am specifically looking for the address and it's private key, I am unsuccessful.


Can somebody point me to the right path?

[madmartyk]

Have you tried importing the private keys back into a blank wallet?  That has worked 95% of the time I have done it.

[Okilo]

Hey, I dropped my laptop which caused the hard drive to be unpartitioned. It spent a week scanning and I was able to recover several wallet.dat files, but when I load them into the correct folder, it tells me "wallet.dat corrupt, salvage failed." Running with -rescan or -salvagewallet returns the same error.

It's very important to note that I also recovered some files called wallet.h, wallet_tests.cpp, walletdb.cpp, walletmodel.cpp, walletview.cpp, walletframe.h, and walletstack.h. It's almost as if the recovery split some C functions off of wither the qt program or wallet.dat itself. I'm not sure.

I'm getting an "Error in dump page" error when I try to dump the contents of my wallet. Bitcoin is not open. Here is the log. Can anyone help? I will tip. Thanks:

C:\>cd Python27

C:\Python27>pywallet.py --web
WARNING:root:pycrypto or libssl not found, decryption may be slow
'ecdsa' package is not installed, pywallet won't be able to sign/verify messages

2014-05-02 13:09:52-0400 [-] Log opened.
2014-05-02 13:09:52-0400 [-] Starting server: 2014-05-02 13:09:52.214000
2014-05-02 13:09:52-0400 [-] Site starting on 8989
2014-05-02 13:09:52-0400 [-] Starting factory <twisted.web.server.Site instance
at 0x026C83C8>
2014-05-02 13:09:55-0400 [HTTPChannel,0,127.0.0.1] 127.0.0.1 - - [02/May/2014:17
:09:54 +0000] "GET / HTTP/1.1" 200 231720 "-" "Mozilla/5.0 (Windows NT 6.1; WOW6
4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.131 Safari/537.36"
2014-05-02 13:09:55-0400 [HTTPChannel,0,127.0.0.1] 127.0.0.1 - - [02/May/2014:17
:09:55 +0000] "GET /favicon.ico HTTP/1.1" 200 14 "-" "Mozilla/5.0 (Windows NT 6.
1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.131 Safari/537
.36"
2014-05-02 13:10:00-0400 [HTTPChannel,0,127.0.0.1] Wallet Dir: C:\Users\BlahBlah\AppData\Roaming\Bitcoin
2014-05-02 13:10:00-0400 [HTTPChannel,0,127.0.0.1] Wallet Name: wallet.dat
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this
again.
2014-05-02 13:10:00-0400 [HTTPChannel,0,127.0.0.1] Unhandled Error
        Traceback (most recent call last):
          File "C:\Python27\lib\site-packages\twisted\web\http.py", line 826, in
 requestReceived
            self.process()
          File "C:\Python27\lib\site-packages\twisted\web\server.py", line 189,
in process
            self.render(resrc)
          File "C:\Python27\lib\site-packages\twisted\web\server.py", line 238,
in render
            body = resrc.render(self)
          File "C:\Python27\lib\site-packages\twisted\web\resource.py", line 250
, in render
            return m(request)
        --- <exception caught here> ---
          File "C:\Python27\pywallet.py", line 3664, in render_GET
            read_wallet(json_db, create_env(wdir), wname, True, True, "", bal, v
ersion)
          File "C:\Python27\pywallet.py", line 2442, in read_wallet
            db = open_wallet(db_env, walletfile, writable=FillPool)
          File "C:\Python27\pywallet.py", line 2006, in open_wallet
            sys.exit(1)
        exceptions.SystemExit: 1

2014-05-02 13:10:00-0400 [HTTPChannel,0,127.0.0.1] 127.0.0.1 - - [02/May/2014:17
:09:59 +0000] "GET /DumpWallet?dir=C:\\Users\\Blah%Blah\\AppData\\Roami
ng\\Bitcoin&name=wallet.dat&bal=false&version=0 HTTP/1.1" 200 18 "http://localho
st:8989/" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like G
ecko) Chrome/34.0.1847.131 Safari/537.36"

[madmartyk]

The easist way I have found is to extract everything to a .txt file and then reimport the keys.  I can go into more detail on what to do if you like.  I have helped recover a few wallets for myself and other people.  Haven't had any issues yet.

[Okilo]

PM'd you.

[fturco]

In Bitcoin Qt > File > Receiving addresses I have an extra address that I never used and that I don't want to use, and since I can't remove it with the GUI I'm trying to do that with Pywallet.

This is what I tried:

• Copied the Bitcoin address in question
• Closed Bitcoin Qt
• Went to Pywallet > Delete, put the address in the field Keys and selected the "Bitcoin address" option
• Clicked "Delete"

I obtained the following message from Pywallet:

key:CENSORED has been successfully deleted from /home/fturco/.bitcoin/wallet.dat, resulting in 0 deleted item

Please notice "0 deleted item". In fact when I restart Bitcoin-Qt the address in question is still there. What can I do?

[prof7bit]

question about "hexsec" and "secret"

consider this dump of an unencrypted wallet: (don't worry, I won't store bitcoins at these keys, I'm just experimenting)

Code:

    {
        "addr": "1EJP1Q1JEQdWtR5PEopCRZdE1F8dgk9Wwp", 
        "compressed": false, 
        "hexsec": "c703063648fd19d64de086064692dd17", 
        "private": "308201130201010420c703063648fd19d64de086064692dd17bd31ef4ebc8b8caa043d1fc7347d6a23a081a53081a2020101302c06072a8648ce3d0101022100fffffffffffffffffffffffffffffffffffffffffffffffffffffffefffffc2f300604010004010704410479be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798483ada7726a3c4655da4fbfc0e1108a8fd17b448a68554199c47d08ffb10d4b8022100fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364141020101a1440342000400481a16f118b4efe54b4783f857a9d45c8b5aec6cf03f7bc177ecc1d2faea443d4e94475ac9312cdfde1a30b4e953356c7e93312eabd92ddb070cdcfb981ee5", 
        "pubkey": "0400481a16f118b4efe54b4783f857a9d45c8b5aec6cf03f7bc177ecc1d2faea443d4e94475ac9312cdfde1a30b4e953356c7e93312eabd92ddb070cdcfb981ee5", 
        "reserve": 1, 
        "sec": "5KKw55iWFRmy614626Fo6ckzS7vxNcfhZJHvvo84W3cAzwfRjVo", 
        "secret": "c703063648fd19d64de086064692dd17"
    }

Why are "secret" and "hexsec" only 16 bytes?


This is the same key after loading the wallet with bitcoin 0.9 and encrypting it (and decrypting again with pywallet)

Code:

    {
        "addr": "1EJP1Q1JEQdWtR5PEopCRZdE1F8dgk9Wwp", 
        "compressed": false, 
        "encrypted_privkey": "cb9f081748ed5d42d010b10baa84748535e5588908e6cc70a28c44c550277ecdcaaf0d5e36cc9f919a0cf3471d2832d8", 
        "hexsec": "c703063648fd19d64de086064692dd17bd31ef4ebc8b8caa043d1fc7347d6a23", 
        "pubkey": "0400481a16f118b4efe54b4783f857a9d45c8b5aec6cf03f7bc177ecc1d2faea443d4e94475ac9312cdfde1a30b4e953356c7e93312eabd92ddb070cdcfb981ee5", 
        "reserve": 1, 
        "sec": "5KKw55iWFRmy614626Fo6ckzS7vxNcfhZJHvvo84W3cAzwfRjVo", 
        "secret": "c703063648fd19d64de086064692dd17bd31ef4ebc8b8caa043d1fc7347d6a23"
    }

It almost looks like the first version was just cut off in the middle.

Another question: Is there any documentation about the various elements of the json that is produced with pywallet?

* For example what is the meaning of the "pool" array, its repeating all the addresses but without their keys but seems to contain additional info, what is the rationale behind structuring it that way and not just put all info about a key into one object?
* what is the empty ckey array at the beginning of the dump?

[x8008]

Can someone please help me out, I got Ubuntu on a virtual machine installed and I got pywallet setup and it's working. I got my wallet.dat file and pywallet.py wallet on the desktop of the virtual machine and nothing else, what command do I need to run in order for it to display the priv key? This wallet is from shibecoin

[Muhammed Zakir]

Hello Jack Jack! This Pywallet is great. I really like it. Thanks for making it.
Kindly,
       Muhammed Zakhir

[jackjack]

Hi everybody
Even though I think most posts are now moot I'll answer them ASAP. It may help other people later.

For people noticing bugs: I still have a new version about to be released (2 weeks? 2 months? I don't know)
Also you'll be able to fill out bug reports soon.

[riclas]

Hi, i'm having trouble importing my backup keys to my main wallet. I get the following output: http://pastebin.com/ii6SfsWr

Can someone help me please?

[frank123m]

Hello.

I got a wallet that cannot dump by pywallet.

test wallet(a SHACoin wallet):

https://mega.co.nz/#!tQQiARBA!fvXQ2J0p97LRu1KpVZd9UKTMQYsWSXTq96PA_Z_TCX0

error message:

Code:

Traceback (most recent call last):
  File "./pywallet.py", line 2061, in parse_wallet
    d['txIn'].append(parse_TxIn(vds))
  File "./pywallet.py", line 2028, in parse_TxIn
    d['prevout_n'] = vds.read_uint32()
  File "./pywallet.py", line 1944, in read_uint32
    def read_uint32(self): return self._read_num('<I')
  File "./pywallet.py", line 1983, in _read_num
    (i,) = struct.unpack_from(format, self.input, self.read_cursor)
error: unpack_from requires a buffer of at least 4 bytes
test@ubuntu:~/pywallet$

please help, thx.

[Muhammed Zakir]

Hi, i'm having trouble importing my backup keys to my main wallet. I get the following output: http://pastebin.com/ii6SfsWr

Can someone help me please?

Why don't you import using below command which is used commonly instead of using pywallet?

Code:

importprivkey bitcoinaddressprivatekey

You can only import 1 key at a time.

kindly,
        MZ

[madmartyk]

Hello.

I got a wallet that cannot dump by pywallet.

test wallet(a SHACoin wallet):

https://mega.co.nz/#!tQQiARBA!fvXQ2J0p97LRu1KpVZd9UKTMQYsWSXTq96PA_Z_TCX0

error message:

Code:

Traceback (most recent call last):
  File "./pywallet.py", line 2061, in parse_wallet
    d['txIn'].append(parse_TxIn(vds))
  File "./pywallet.py", line 2028, in parse_TxIn
    d['prevout_n'] = vds.read_uint32()
  File "./pywallet.py", line 1944, in read_uint32
    def read_uint32(self): return self._read_num('<I')
  File "./pywallet.py", line 1983, in _read_num
    (i,) = struct.unpack_from(format, self.input, self.read_cursor)
error: unpack_from requires a buffer of at least 4 bytes
test@ubuntu:~/pywallet$

please help, thx.

Found 141 possible unencrypted keys
Keys are extracting now.

[riclas]

Hi, i'm having trouble importing my backup keys to my main wallet. I get the following output: http://pastebin.com/ii6SfsWr

Can someone help me please?

Why don't you import using below command which is used commonly instead of using pywallet?

Code:

importprivkey bitcoinaddressprivatekey

You can only import 1 key at a time.

kindly,
        MZ

Because I did the backup with pywallet, so I assumed it would be easy to import it back with pywallet :\

I want to get my labels back too, all the info that is on the backup.

[frank123m]

Hello.

I got a wallet that cannot dump by pywallet.

test wallet(a SHACoin wallet):

https://mega.co.nz/#!tQQiARBA!fvXQ2J0p97LRu1KpVZd9UKTMQYsWSXTq96PA_Z_TCX0

error message:

Code:

Traceback (most recent call last):
  File "./pywallet.py", line 2061, in parse_wallet
    d['txIn'].append(parse_TxIn(vds))
  File "./pywallet.py", line 2028, in parse_TxIn
    d['prevout_n'] = vds.read_uint32()
  File "./pywallet.py", line 1944, in read_uint32
    def read_uint32(self): return self._read_num('<I')
  File "./pywallet.py", line 1983, in _read_num
    (i,) = struct.unpack_from(format, self.input, self.read_cursor)
error: unpack_from requires a buffer of at least 4 bytes
test@ubuntu:~/pywallet$

please help, thx.

Found 141 possible unencrypted keys
Keys are extracting now.

sounds good. so your pywallet works? or you use other method?
i can use it dump btc wallet and find keys, but shacoin cannot. it stopped with those errors.
can you show me how to find those keys with a shacoin wallet? thx.

[jackjack]

Hi, i'm having trouble importing my backup keys to my main wallet. I get the following output: http://pastebin.com/ii6SfsWr

Can someone help me please?

Why don't you import using below command which is used commonly instead of using pywallet?

Code:

importprivkey bitcoinaddressprivatekey

You can only import 1 key at a time.

kindly,
        MZ

Because I did the backup with pywallet, so I assumed it would be easy to import it back with pywallet :\

I want to get my labels back too, all the info that is on the backup.

Pastebin seems down so I can't see your error messages but I know what you want is possible
I'll look at that as soon as pastebin is up again

Ok Pastebin works again.
It looks like your put the data in the "import transaction" form. Either you made a mistake or there's a big bug in pywallet.

I see that your file is "keys.json" but the key export format of Pywallet is not json so maybe you didn't use the correct method.
You must export your keys with the "Dump your keys" form. That will make a file full of "1privkey;label".
Then you just have to import this file with the "Import keys" form.

If I'm right and that your keys are in json format (probably from a wallet dump), just send me a small part of it with all the private keys modified (deleted/emptied/whatever). I'll make you a script to transform keys.json into a usable file.

[riclas]

ah yes, then that is what happened. I did a full wallet dump to json thinking that i could import it all later. I now realize the "import transactions" option is not what i though. Maybe you could add an option to pywallet to import keys from a full wallet dump?

i'll send you a part of the file in PM. thank you.

[jackjack]

ah yes, then that is what happened. I did a full wallet dump to json thinking that i could import it all later. I now realize the "import transactions" option is not what i though. Maybe you could add an option to pywallet to import keys from a full wallet dump?

i'll send you a part of the file in PM. thank you.

Yeah, I'll add that to the new version

I did this, try it out and tell me how it goes
Download it into translate.py, then run

Code:

python translate.py wallet.json

That will make a wallet.json.pywalletexport that will (hopefully) be accepted

[riclas]

first there is something wrong with the first if expression. it always prints the usage when i input the command you gave me.
i don't know python to fix it, but i removed the if and ran the script. what it did was create a .csv of the public addresses and labels, not the private addresses, which are the ones i require...