-
Notifications
You must be signed in to change notification settings - Fork 691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have wallet.dat file when i run btcrecover.py then this error shows #85
Comments
Are you using Bitcoin Core, or an alternative? What's the full version (it's the first line from the |
Q: Are you using Bitcoin Core |
What about this question:
Also, do you receive a warning when you run btcrecover which looks like this?
|
I'm currently using |
|
Q: Also, do you receive a warning when you run btcrecover which looks like this? |
My wallet.dat file is old. |
OK, so I can't be sure, but my best guess right now is that you have a corrupted wallet.dat file. If you have a different backup, please give it a try first. If not, you can try to use Bitcoin Core's
(The location of your If this doesn't work, you may want to look into Pywallet, specifically take a look at this post to attempt to scan a wallet.dat for keys and construct a new one. Finally, if you'd like to, you can send me the output from a slightly modified btcrecover extract script, and I can try to make some sense out of it. First, install a decent text editor such as Notepad++ (this won't work with the built-in Notepad, although the built-in WordPad might work if you really don't want to download Notepad++). Next, using Notepad++, open the print(base64.b64encode(mkey)) Next, run (No guarantees I'll be able to help, but I'll give it a try.) |
How can i install Pywallet on windows 10. |
Download the ZIP file from its GitHub page here and extract it and run it pretty much the same way as btcrecover. |
After using Bitcoin Core's -salvagewallet, Nothing helping. |
First off, if you have a lot of value in that wallet: since it appears to be a corrupted file, the safest thing to do would be to stop using your hard drive completely and look into hiring a data recovery specialist. If you continue tinkering, you will decrease the chances that a specialist can recover any corrupted data. This is all far beyond the scope of btcrecover (and my expertise) in that case... If you'd like to keep tinkering anyways, could you try to sign a message in Bitcoin Core (it's in the Have you tried the other two options I suggested? Using Pywallet or running the modified version of I hate to be pessimistic, but it's not looking very hopeful if you have no backups and |
Yes, I have tried above described method but I'm unable to proceed with Pywallet , I don't know that how to operate it. Is it method work? If any python developer build GUI software for entering the passwords in bitcoin core where we can change password by entering old password & new password or in transfer tab where bitcoin core asked password for sending balance, Thank You. |
The link I posted above (this one) goes to a post with the pywallet command you'd need to run to attempt to scan for and recover keys in a corrupted wallet. You'd need to change those two parameters (the one which says where your wallet.dat currently is and the one which says the folder where the recovered wallet should go). There's no way to know beforehand if your wallet can be recovered... as I said, since If you're having trouble with it, I'd suggest you make a post in that same thread; the developer of that tool, "jackjack", still checks it on occasion and there are others there who may also be able to help. |
I've run this command pywallet.py --dumpwallet > temp.txt That method discussed here: https://walletrecoveryservices.com/limited/ |
The "encrypted_key" you posted above is 64 letters (32 bytes) long. It should be 96 letters (48 bytes) long. Your wallet file is corrupted, or it was written by a buggy version of Bitcoin Core. I don't know of any buggy version of Bitcoin Core that does this, so it's probably corrupted. It might not be possible to recover. How sure are you that you remember your password? |
I have extracted $bitcoin$64$cb2, How much character is good for this? |
Sorry, but I don't understand your question.... |
I have extracted hash from wallet.dat for password cracking, I'm asking that how can i know that it is not corrupted, I'm pasted here uncompleted hash > $bitcoin$64$cb2d26e335eea661916 |
I have extracted the hash from wallet.dat with this command > JohnTheRipper/run/bitcoin2john.py Desktop/wallet.dat |
That's from JohnTheRipper's bitcoin2john, correct? It shows the same issue. In particular, that 64 should be a 96 if it came from a non-corrupted wallet. Even if you had your password, your wallet may be too corrupted to recover any funds. It's hard to say... but could you answer this please?
|
I'm not sure, I can provide you wallet.dat file for examine. |
Wallet.dat file have 450+ bitcoins. I will send wallet.dat file to chris@gurneeconsulting.net ,Please can you help me for examine this wallet? Thank You. |
You can see all of the test hashes in JtR here. They all have a What are all 5 of the numbers in the
There are 5 numbers that are between If you'd rather send them by email, I'm at chris@gurneeconsulting.net. |
@qasimilyas99 If you manage to salvage an encrypted key and get an extract and want help cracking it, add me on skype petr5476. I have a slight suspicion he could be loading some altcoin wallet.dat and seeing +450 in the transaction logs. |
I have sent wallet.dat file to chris@gurneeconsulting.net. |
For posterity: I received the wallet.dat (to others reading this issue: please don't send me your wallet.dat files...) and responded back. I'd rather not go into specifics in the interest of OP's privacy, however I suspect that OP is mistaken about what they think they have or need... |
I think it might be worth closing then? |
I'm still waiting for a response back from OP... |
I've sent you response via email, Thank You for your cooperation. |
hi, it seems this wallet file got some history and was sold at least 4 times. I hope its alright for me to leave this link to bitcointalk here where the accusation is discussed. |
Figured something was up, nobody sends a $1million wallet.dat to another person so easy. |
This issue seems to have run its course. Further discussion should probably happen over in the bitcointalk thread, so I'll go ahead and close this. |
I have wallet.dat file when i run btcrecover.py then this error shows >>
encrypted_master_key, self._salt, method, self._iter_count = struct.unpack_from(b"< 49p 9p I I", mkey) struct.error: unpack_from requires a buffer of at least 66 bytes
The text was updated successfully, but these errors were encountered: