Pywallet 2.2: manage your wallet [Update required] - page 13.

edgar

legendary

Activity: 1858

Merit: 1001

during recovery it asked if i had one & to enter it, with no option to not enter.

i hit space and enter, then enter again.

the wallet is >2 yrs old and never had any password on it

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Are you 100% sure you never used a passphrase?
That would be really strange

edgar

legendary

Activity: 1858

Merit: 1001

Quote from: jackjack on March 21, 2017, 10:18:59 AM

Hi!
Yes, sorry for the overflowing inbox Grin

What does partially recovered mean? What happened and where does the wallet you're dumping come from?

If it comes from the pywallet recovery feature then the password is what you wrote when pywallet asked you to choose a passphrase for the new wallet

Hi!!

Thanks for your reply!!

at first i could get no information other than wallet address, with help i/we managed to get more addresses & ckeys, using otherversion 55 i managed to get encrypted privkeys & pubkeys.

but we're at a loss how to move fwd.

initially the wallet.dat was removed while the client was open, it has sat dormant since 2015

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Hi!
Yes, sorry for the overflowing inbox Grin

What does partially recovered mean? What happened and where does the wallet you're dumping come from?

If it comes from the pywallet recovery feature then the password is what you wrote when pywallet asked you to choose a passphrase for the new wallet

edgar

legendary

Activity: 1858

Merit: 1001

hi jack,

PM'd you yesterday but i imagine your inbox is overflowing with 'please help'

ive a ppc wallet i managed to partially recover with some help, but i never used a password/phrase so no idea why i have encrypted privkeys..

   },
   {
   "addr": "PUYxxxxxxxxxxxxxxxxxxxxxxxxxczt",
   "compressed": true,
   "encrypted_privkey": "64949033adc7ca15de0cefac43a196a21dd410adab8b91271c45dbf722e7d644e00165ca488d920 97ff4fe6cd2083972",
   "pubkey": "021b66d33c146e9ea7d390b581d934bd5699c113c36f355dc0e90ec27a408433e0",
   "reserve": 1
   },

can you please advise? ive spent ages trying to sort this

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Quote from: eduncan911 on March 16, 2017, 02:30:25 PM

Hello JackJack.

I have some old wallet.dat files from early 2014 I am trying to get the PrivateKeys from - and only the private keys. They are from Bitcoin-QT (Windows version).

All wallets have a passphrase.

I am now on OSX.

When I run pywallet.py, with the correct passphrase, I get a Segment Dump error - with no stacktrace.

Code:

$ ./pywallet.py --dumpwallet --datadir=data/ --wallet=wallet-9.dat
# moving wallet-9.dat to its own data9/wallet.dat
$ ./pywallet.py --dumpwallet --datadir=data9/

Both of these give the segment fault and crashes.

Also tried the web interface, same error.

NOTE: I am disconnected from the Internet when running the pywallet.py script.

Here's the version I am on:

Code:

$ git remote -v
origin  [email protected]:jackjack-jj/pywallet.git (fetch)
origin  [email protected]:jackjack-jj/pywallet.git (push)
$ git log
commit b52c955f8c93a75745166ebf281448016e1f22e2
Merge: 069ef00 7c847c1
Author: jackjack-jj 
Date:   Mon Sep 8 20:59:58 2014 +0200

    Merge pull request #11 from gurnec/crypto-fixes

    Fix wallet creation bugs related to crypto

Using virtualenv for python2.7, I installed:

Not sure how to move forward from here.

I can open the wallet.dat files, all of them, with an old Bitcoin-QT wallet I have on a disconnected-from-the-net Windows Virtual Machine. So, I know the wallet.dat files are valid.

Thanks!

Sadly I don't know OSX, I'll check where this error can come from
In the mean time you should try the method of shorena (the dumpwallet command)
By the way, how big is the wallet?

Quote from: Sammo619 on March 17, 2017, 01:43:59 PM

Hi..... HELP.
I have a corrupted, unrecoverable wallet.dat file.

I can't get any of this working.

Now at the
Instead do that:
It would be easier to install WinPython (choose 32 or 64bit depending on your computer: https://sourceforge.net/projects/winpython/files/WinPython_2.7/2.7.12.4/)
Go where you installed it
Launch "WinPython Command Prompt.exe"
Execute this: python -m pip install twisted ecdsa
Then: python C:\path\to\pywallet.py
Stage.

and I get this:

File "pywallet.py", line 852
_p = 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFC2FL
^

I doubt I can get my wallet back as its been overwritten, but undelete software can still locate the old file, but recovery of it leaves a corrupt file.

This seems my only slim chance but I have no idea what I am doing.
PLEASE HELP

Please provide the complete error message

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: eduncan911 on March 16, 2017, 06:56:45 PM

Quote from: madmartyk on March 16, 2017, 03:00:56 PM

Can't you just dump the private key from the QT wallet?

Too many public keys... each requires the dumpprivkey entry.

Would rather script it using this tool across my many wallet.dat files.

You can dump all priv keys from a wallet.dat using

Code:

dumpwallet "filename"

Dumps all wallet keys in a human-readable format.

Arguments:
1. "filename"    (string, required) The filename

Examples:
> bitcoin-cli dumpwallet "test"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "dumpwallet", "params": ["test"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/

Sammo619

newbie

Activity: 4

Merit: 0

Hi..... HELP.
I have a corrupted, unrecoverable wallet.dat file.

I can't get any of this working.

Now at the
Instead do that:
It would be easier to install WinPython (choose 32 or 64bit depending on your computer: https://sourceforge.net/projects/winpython/files/WinPython_2.7/2.7.12.4/)
Go where you installed it
Launch "WinPython Command Prompt.exe"
Execute this: python -m pip install twisted ecdsa
Then: python C:\path\to\pywallet.py
Stage.

and I get this:

File "pywallet.py", line 852
_p = 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFC2FL
^

I doubt I can get my wallet back as its been overwritten, but undelete software can still locate the old file, but recovery of it leaves a corrupt file.

This seems my only slim chance but I have no idea what I am doing.
PLEASE HELP

eduncan911

member

Activity: 101

Merit: 10

Miner / Engineer

Quote from: madmartyk on March 16, 2017, 03:00:56 PM

Can't you just dump the private key from the QT wallet?

Too many public keys... each requires the dumpprivkey entry.

Would rather script it using this tool across my many wallet.dat files.

madmartyk

legendary

Activity: 2702

Merit: 1030

Yes I am a pirate, 300 years too late!

Can't you just dump the private key from the QT wallet?

eduncan911

member

Activity: 101

Merit: 10

Miner / Engineer

Hello JackJack.

I have some old wallet.dat files from early 2014 I am trying to get the PrivateKeys from - and only the private keys. They are from Bitcoin-QT (Windows version).

All wallets have a passphrase.

I am now on OSX.

When I run pywallet.py, with the correct passphrase, I get a Segment Dump error - with no stacktrace.

Code:

$ ./pywallet.py --dumpwallet --datadir=data/ --wallet=wallet-9.dat
# moving wallet-9.dat to its own data9/wallet.dat
$ ./pywallet.py --dumpwallet --datadir=data9/

Both of these give the segment fault and crashes.

Also tried the web interface, same error.

NOTE: I am disconnected from the Internet when running the pywallet.py script.

Here's the version I am on:

Code:

$ git remote -v
origin  [email protected]:jackjack-jj/pywallet.git (fetch)
origin  [email protected]:jackjack-jj/pywallet.git (push)
$ git log
commit b52c955f8c93a75745166ebf281448016e1f22e2
Merge: 069ef00 7c847c1
Author: jackjack-jj 
Date:   Mon Sep 8 20:59:58 2014 +0200

    Merge pull request #11 from gurnec/crypto-fixes

    Fix wallet creation bugs related to crypto

Using virtualenv for python2.7, I installed:

Code:

$ brew info berkeley-db 
$ YES_I_HAVE_THE_RIGHT_TO_USE_THIS_BERKELEY_DB_VERSION=1 BERKELEYDB_DIR=/usr/local/Cellar/berkeley-db/6.2.23 pip2 install bsddb3
$ pip2 install Twisted

Code:

$ python2 -V
Python 2.7.13

$ pip2 freeze
appdirs==1.4.0
attrs==16.3.0
Automat==0.5.0
bsddb3==6.2.4
constantly==15.1.0
ecdsa==0.13
futures==3.0.5
greenlet==0.4.12
incremental==16.10.1
mccabe==0.6.1
mercurial==4.1.1
msgpack-python==0.4.8
neovim==0.1.13
packaging==16.8
pbr==2.0.0
pycodestyle==2.3.1
pydocstyle==1.1.1
pyflakes==1.5.0
pylama==7.3.3
pyparsing==2.1.10
six==1.10.0
stevedore==1.21.0
trollius==2.1
Twisted==17.1.0
virtualenv==15.1.0
virtualenv-clone==0.2.6
virtualenvwrapper==4.7.2
zope.interface==4.3.3

Not sure how to move forward from here.

I can open the wallet.dat files, all of them, with an old Bitcoin-QT wallet I have on a disconnected-from-the-net Windows Virtual Machine. So, I know the wallet.dat files are valid.

Thanks!

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Sorry to hear that
Even a new wallet has 100 keys so I'm not surprised you don't find anything on the 10 you found Sad

See PM for my email

sachalamp

newbie

Activity: 9

Merit: 0

I managed to finally get the old HDD so that I can run the script on it. To my surprise, after being formatted and used (so new files having been written) it found 10 keys, which is about right I guess, I had very few transactions. Sadly, after dumping them to check the balance on them in txt file using your instructions from here: https://bitcointalksearch.org/topic/m.3074581

they seem to be on 0 balance on all addresses.

So I guess that's that, even though I find it kind of strange, perhaps it recovered the new wallet Bitcoin Core created after the windows refresh?

I would like you to have a look if you want to, I can send you the initial wallet file I recovered with Icare Data Recovery back in 2014 and from which pywallet extracted 0 addresses and the new wallet created by pywallet (with 10 keys) after scanning the old hard drive. I need your email for it though, I couldn't find it.

Thank you anyway for this program and for your kind assistance so far.

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

There's a really tiny chance it may work but yeah don't have too high expectations Sad

sachalamp

newbie

Activity: 9

Merit: 0

I figured scanning c: would not do anything in this situation but did so anyway just in case.

I'm currently trying to scan the older hdd to it's full size although i assume that since it was formatted and used for storage it is very unlikely to still contain data from 2014.

In case that doesn't work, if you could look at the .dat file i'd appreciate it. Can you link me an email please?

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Unfortunately I'm rather sure your current wallet.dat doesn't contain any key
You can send me your wallet if you're ok with me taking a look at it as a last resort

Do you still havethe computer bitcoin was on? It may still contain parts of your wallet

Btw, no need to scan C: in your new computer according to the events
If you scan C: (if you can scan the old computer), you must use the size of C:

sachalamp

newbie

Activity: 9

Merit: 0

wallet.dat comes from another computer, which windows 7 or 8 at that time "refreshed" (because something went bad and it couldn't boot), which theoretically should've left everything except the system files intact.

When I saw that Bitcoin Core was reset and had started to update from scratch after the windows refresh, I used different recovery programs to find the former wallet. Which I then transferred to another computer that I am using now.

I tried scanning c: and the same thing happens http://imgur.com/a/w2wlC

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

Yeah that's strange, did you try scanning the whole C: partition?
Where does this file come from?
(yes it would have seen the encrypted keys if you had used a passkey)

sachalamp

newbie

Activity: 9

Merit: 0

Thank you for all your help so far an sorry for wasting time with beginner mistakes, I don't know programming.

You example worked, which prompted me to correct the lines i was running to:

python pywallet.py --recover --recov_size 30.1Gio --recov_device c:\python27\wallet.dat --recov_outputdir c:\python27\recover

Which worked but found 0 possible wallets, 0 encrypted keys and 0 unencrypted keys, which I guess means I lost the btc I had there. The only thing that feels off is that the wallet.dat file is 150kb, larger than an empty wallet. I don't remember if I had used a passkey but I think pywallet would've notified me if I did.

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

I'm sorry it's not clear enough, the recover part it's not in the web interface, it's only usable from the command line

Try this to see if it's really broken:

Quote

python pywallet.py --info --importprivkey=5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreAnchuDf

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