Topic: Pywallet 2.2: manage your wallet [Update required] - page 29. (Read 208227 times)

What do you mean? You mixed 5 and S? I didn't even realize  both were used


To try what?

I did now, no joy.

I also had trouble earlier importing the key as Satoshi left 5 and upper case s in the base58 code - a strange design flaw...

Thanks anyway - I guess I need to find another way to try this.

Did you put your passphrase in the Passphrase tab?

If not:
 - Close Bitcoin
 - Delete the address you added
 - Put your passphrase in the tab
 - Import again


Yes, I know, It should refuse to import if the passphrase isn't correct, but I'm a bit busy currently and as it doesn't corrupt the wallet it's not top priority

I imported a private key into my encrypted backed-up wallet using pywallet and now I get 'transaction creation failed' when trying to send - it does add the balance of the paper wallet to my balance.

It did ask for my password when doing the transaction - is it decrypting a non-encrypted private key?

You have some ideas about what the passphrase could be? Or you used something like 2i9Dz$£*"$Aç")=zàé°0"$µZ€¤^?

In the first case, put that in a py file and run it: http://pastebin.com/raw.php?i=KyTQWPqs (tweaked Joric's pywallet)
It will ask forever for your passphrase and will tell you instantly if it's correct

Hi JackJack,

you are right, I could'nt access the file because it was on C:. It works on D: and could make a dump.

But now I don't know what I am supposed to do. I have a lots of "scriptPubKey": and "encrypted_privkey", or "pubkey":, is it helpful  to recover my password ?

Another thing to note if you want to recover your unencrypted wallet. DO NOT USE THE HARD DRIVE that used to contain it. This usually means, don't even use the computer it's connected to. Otherwise, you might inadvertently overwrite any unencrypted private keys that you are trying to recover.

Then either :

• Bitcoin client is locking your wallet (check that it's closed)
• Your wallet is corrupted
• You need to be administrator to open a file in C: . Not likely but I'm no specialist of Windows so maybe

Yes, the path is good, I've put the wallet here because pywallet couldn't find it with the default path

Dump is to show the content of your wallet, that's a good thing to start with that
Looks like you told pywallet that your wallet.dat is in c:\, are you sure of that? Normally it's somewhere in some windows directories and moreover, pywallet should fill the form with this place by default

Once you can dump your wallet, I'll make you a custom pywallet to test out passphrases

I tried a dump (don't know what it means), and it didn't work, I had this message : "Error in dump page"
And in the windows command :
Maybe I am no smart enough for this...


.......
28 "http://localhost:8989/" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537
.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31"
2013-04-24 23:08:49+0200 [HTTPChannel,0,127.0.0.1] Wallet Dir: C:\
2013-04-24 23:08:49+0200 [HTTPChannel,0,127.0.0.1] Wallet Name: wallet.dat
2013-04-24 23:08:49+0200 [HTTPChannel,0,127.0.0.1] Unhandled Error
        Traceback (most recent call last):
          File "c:\python27\lib\site-packages\twisted\web\http.py", line 790, in
 requestReceived
            self.process()
          File "c:\python27\lib\site-packages\twisted\web\server.py", line 192,
in process
            self.render(resrc)
          File "c:\python27\lib\site-packages\twisted\web\server.py", line 241,
in render
            body = resrc.render(self)
          File "c:\python27\lib\site-packages\twisted\web\resource.py", line 250
, in render
            return m(request)
        --- ---
          File "d:\docs\downloads\pywallet.py", line 3264, in render_GET
            read_wallet(json_db, create_env(wdir), wname, True, True, "", None,
version)
          File "d:\docs\downloads\pywallet.py", line 1231, in create_env
            r = db_env.open(db_dir, (DB_CREATE|DB_INIT_LOCK|DB_INIT_LOG|DB_INIT_
MPOOL|DB_INIT_TXN|DB_THREAD|DB_RECOVER))
        bsddb.db.DBPermissionsError: (1, 'Operation not permitted -- C:\\__db.00
1: Operation not permitted')

2013-04-24 23:08:49+0200 [HTTPChannel,0,127.0.0.1] 127.0.0.1 - - [24/Apr/2013:21
:08:49 +0000] "GET /DumpWallet?dir=C:\\&name=wallet.dat&version=0 HTTP/1.1" 200
18 "http://localhost:8989/" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537
.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31"

ok, but now I don't understand how I can reset or hack my old passphrase ..... 

ok cool, I succeed to access the webui, I couldn't install because I used the 64bit version of Python (sorry for my english)

Run it through the command line:

• Hit Windows+R, enter 'cmd'
• Then type 'c:\python27\python.exe path\to\pywallet.py --web' (you won't need the web ui but it's to show what dependencies are missing)
• Report results here

PS:
In case you want to use the web ui later:

• Download and install PWI (pywallet windows installer), link at the bottom of http://pywallet.tk
• That will put 4 files in the folder you provided (pywallet.bat, pywallet.py, update, and install)
• Run install.bat again (because a link to a dependency changed) and install the program
• Run pywallet.bat

Thanks for your answer. Do you know if I can find a tutorial ? I tried to install Python + Pywallet, but I can't launch pywallet.py, I have a window appearing for 1ms and desappearing (sorry for my bad english)

If you have parts of your passphrase and/or it was short, there is some hope, and yes, pywallet can help (well, a tweaked version)

If not I don't think you'll recover them
You can still try to scan your hdd at a low level (pywallet can do this) to find private keys. It may remain some parts of your not-yet-encrypted wallet before you encrypted it

Hi everybody,

I am quite new on the bitcoin universe and I am already in trouble.

I lost the passphrase of my wallet, is it possible to reset or recover it with pywallet ?

Thank you very much for your help,


Stef

Yeah, the real problem is when the tx is broadcasted to the network
In this case, kjj's suggestion is the only thing to do

I'm guessing this is what happened... though I would have expected, if the txn was rediscovered from a peer, for it to show up in gettransaction/getrawtransaction probes, especially after doing the long txindex rebuild... but it did not. (I received an `error: {"code":-5,"message":"Invalid or non-wallet transaction id"}` for gettransaction.)

If I have to try this again, I'll keep the node off the network before testing... but that raises the question: is there a good way to do that, using just bitcoind/bitcoin-qt options? (Total network 'unplug' isn't possible for this particular wallet which i can only reach via the network.) It looks like a maxconnections of 0 will be ignored. Maybe a single 'connect' option to a known-bad address, with no addnodes, will leave a client started but unconnected?


I didn't get around to trying a delete-all-txns. I'd pushed the unconfirmed transactions myself to blockchain.info -- so yes in fact they all appeared there. But after using pywallet to remove them locally, they would not return from my client via 'gettransaction', even though they were still effectively consuming earlier outputs.

I was able to craft a replacement double-spend transaction, via the bitcoind raw txns api, to compete with the 1st unconfirmed transaction. After issuing that, with a larger transaction fee, it was fairly quickly mined into a block, making the other 6+ txns orphans. My replacement transaction evacuated the affected wallet entirely... so I believe my problem is resolved, with all funds again spendable rather than stuck as unconfirmed change.

I'm guessing kjj's theory above, rediscovery of the key transaction from peers, was the main factor in the spendable outputs/balances remaining the same even after local transaction deletion.

Thanks for the rapid replies and suggestions!

1. Your wallet isn't corrupted.
2. Did you try deleting all the tx's?
3. Did you check on blockchain.info if your tx is shown?
4. Can you post the recipient address?