Bitcoin Forum
September 26, 2025, 05:15:52 PM *
News: Latest Bitcoin Core release: 29.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 »
1  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: March 07, 2025, 05:55:32 PM
Its been a long time and I have almost finished with the wallet.dats and I'm just wondering about what you said about putting them together as one and then using bitcoin core, I am just wondering how I would do that if anyone has an answer it would be greatly appreciated. Thanks.
2  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: February 08, 2025, 04:41:53 PM
Thanks for the Info, i have found more wallet.dats from another place so I am currently going through the process of recovering them and then putting them into bitcoin core. It will take along time because of the amount of wallet.dats and then each one in bitcoin core takes 6 hours.    Smiley

Thank you
3  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: February 01, 2025, 11:32:20 PM
Sorry for not being active recently, I am  going to use Disk Drill & have downloaded it from the official site. Thanks for the info.
4  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 27, 2025, 05:22:07 PM
oaky will do thanks.

so when i got the notification of the restore wallet failed, its said     data is not in recognized format.

Could it be the recovery software is the issue or is it that I didn't save the wallet.dat when I deleted the Bitcoin Core from my 'D' drive?
5  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 26, 2025, 06:59:18 PM
It took around 6 hours to load the wallet and there is nothing there, i have not tried text editor yet. Do you recommend any recovery software as I want to go back on to the old hard drive and recover it with a different software to see as it says that it is in incorrect format at the moment.
6  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 26, 2025, 01:34:02 AM
I have a fully updated un pruned bitcoin core that is trying to restore the wallet it is taking a very long time and will post the results as soon as possible, at least it hasn't failed



Hi sorry for the long wait. I have been trying different wallet.dats that I have been finding then using the recovery method and I have found this,

The new wallet C:\Python27\111recover_folder/recovered_wallet_1737671199.dat contains the 4103 recovered keys

Quite a surprise to me as I have never seen the scan go this far and it has never came back with this answer nor has it gone to the importing keys stage so it looks hopeful on this side. Is this a step in the right direction?

First, try loading the wallet in Bitcoin Core. If it gives an error, you can try opening the file with a text editor and look for any readable text within it. Since you created the wallet with Electrum v25, it's likely to be in SQLite format. Try searching within the file for readable text such as walletdescriptorkey, internalspk name, and even if you can visualize addresses. This will give you clues if the file belongs to a real wallet.

Is notepad good enough or which text editor do you recommenced. I will do this if the file fails to load.
7  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 23, 2025, 11:01:36 PM
Hi sorry for the long wait. I have been trying different wallet.dats that I have been finding then using the recovery method and I have found this,

The new wallet C:\Python27\111recover_folder/recovered_wallet_1737671199.dat contains the 4103 recovered keys

Quite a surprise to me as I have never seen the scan go this far and it has never came back with this answer nor has it gone to the importing keys stage so it looks hopeful on this side. Is this a step in the right direction?
8  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 17, 2025, 06:39:38 PM
Managed to get some time today and here is the results of the scan

Found 1 possible wallets
Found 6 possible encrypted keys
Found 0 possible unencrypted keys

Possible wallet #1
    with passphrase #1

Private keys not decrypted: 6
Trying all the remaining possibilities (6) might take up to 0 minutes.
Do you want to test them? (y/n): y

The wallet is encrypted and the passphrase is correct


Importing:


The new wallet C:\Python27\111recover_folder/recovered_wallet_1737138914.dat contains the 0 recovered key

The 111recover_folder has a recovered wallet in and some other stuff along with the db.001 to 006 but I'm guessing this is not good result.
9  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 16, 2025, 10:37:01 PM
I'm terribly sorry for no response this week, I have had a very hectic week to say the least and I will be back to it on Saturday  Smiley
10  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 12, 2025, 01:11:46 AM
Thanks, I have had a little bit of success, getting it to go through the scan of the Go Reads and here is the result that came through at the end

Traceback (most recent call last):
  File "pywallet.py", line 4034, in <module>
    recoveredKeys=recov(device, passes, size, 10240, options.recov_outputdir)
  File "pywallet.py", line 1713, in recov
    f=open(outputdir+'/pywallet_partial_recovery_%d.json'%ts(), 'w')
IOError: [Errno 2] No such file or directory: 'C:\\Python27\\111recover_folder/pywallet_partial_recovery_1736643639.json'

I also have an additional file named  111dump01.tx  in the directory and files called __db.001 to __db.006
11  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 12, 2025, 12:11:37 AM
I have got this far but it would not let me type in the passphrase when prompted to  Huh

PS F:\> ./python pywallet.py --recover --recov_device=F: --recov_size=57Gio --recov_outputdir=C:\Python27\111recover_folder
WARNING:root:pycrypto or libssl not found, decryption may be slow
Enter the passphrase for the wallet that will contain all the recovered keys:
Enter the passphrase for the wallet that will contain all the recovered keys (can't be empty):
Enter the passphrase for the wallet that will contain all the recovered keys (can't be empty):

Enter the possible passphrases used in your deleted wallets.
Don't forget that more passphrases = more time to test the possibilities.
Write one passphrase per line and end with an empty line.
Possible passphrase:
Possible passphrase:

Pywallet uses bsddb3 (Berkeley DB), which is for legacy wallets. Bitcoin Core 25 uses SQLite by default for wallets instead of the traditional Berkeley DB, although both are compatible a legacy wallet is currently created by editing bitcoin.conf and with a command in the console so I don't think Pywallet will help you since I assume you created your wallet by default.
you should look for tools with wallet descriptor support, or recover an older version of the file, or subject your disk to file recovery software like tesdisc.
what happened that your address got corrupted?


I did create the wallet and named it, but I didn't save it so I recovered the file using recovery software (EASEUS) and the .dat file I recovered when loading it into the bitcoin client comes back with an error message with the wallet being in an incorrect format.
12  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 10, 2025, 11:45:18 PM
I have got this far but it would not let me type in the passphrase when prompted to  Huh

PS F:\> ./python pywallet.py --recover --recov_device=F: --recov_size=57Gio --recov_outputdir=C:\Python27\111recover_folder
WARNING:root:pycrypto or libssl not found, decryption may be slow
Enter the passphrase for the wallet that will contain all the recovered keys:
Enter the passphrase for the wallet that will contain all the recovered keys (can't be empty):
Enter the passphrase for the wallet that will contain all the recovered keys (can't be empty):

Enter the possible passphrases used in your deleted wallets.
Don't forget that more passphrases = more time to test the possibilities.
Write one passphrase per line and end with an empty line.
Possible passphrase:
Possible passphrase:
13  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 10, 2025, 11:08:08 PM
So I have put my wallet.dat file into C Python27 and ran the command in Windowspowershell replacing the passphrase with mine ands the name of my wallet.dat file and it came out with
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
I didn't have anything to do with bitcoin open. Does this mean I have to do the other method as it is corrupted.

Is this wallet old? If you open the file with a text editor you can read something, like, walletdescriptorkey, sqlite? If so, I think pywallet doesn't support it because it uses sqlite and the old ones use berkeleydb.

The wallet is approximately 13/14 months old, this is the version that the .dat was created in the bitcoin client bitcoin-v25.0.0.



-snip- and it came out with ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
I didn't have anything to do with bitcoin open. Does this mean I have to do the other method as it is corrupted.
That error shows if pywallet can't lock of the wallet.dat usually if it's being used by Bitcoin Core or another client/program.
But yes, that also appears when pointed to a corrupted wallet file, case-to-case basis.

For the other method (--recover), your options are:
  • Use an existing partition (drive letter) as --recov-device; this may result with lots of false positives/negatives based from the number of wallets that you've used in that partition.
  • Create a small partition (about <1GB) from your non-system drive (not C: drive) by "shrinking" it and creating a new partition.
  • Grab a small USB flash drive (preferably USB3) to be used as your --recov-device

The simplest is the third option where you can immediately start --recover.
Here's how to:
  • Plug your USB Drive and remember the drive letter it's allocated with, let's say it's shown as "F:".
  • Paste all of your wallet.dat files inside that flash drive.
  • Then open PowerShell with python and pywallet's folder as its working directory (SHIFT-Right-click method)

Then enter this command:
Code:
./python pywallet.py --recover --recov_device=F: --recov_size=16Gio --recov_outputdir=C:\Python27\111recover_folder
You must replace the "--recov_device=<letter>:" and "--recov_size=<size>Gio" based from your Flash Drive's letter and maximum size.

In that same PowerShell window, pywallet will ask you to type a passphrase for the wallet.dat that it'll create (where the keys will be imported).
Next, it will ask you the passphrase(s) of the wallet files in that drive, one passphrase per line (enter), enter a blank passphrase in the next line after typing all the passphrases.
Note: it will not display the passphrase that you've typed for safety purposes.

If the command is successful whether there are keys imported or not, a wallet.dat will be created inside a folder named "111recover_folder" in C:\Python27\ directory.
The result should tell you whether there are private keys imported or not.


Just FYI when I try to load the corrupted wallet.dat, bitcoin client tells me the wallet
is in an incorrect format.This is the file i recovered after stupidly deleting it from my D drive.

Im going to be using a USB flash drive as my non system drive, I am unsure if i can shrink the partition on this?
Or does it have to be an actual hard drive

Grab a small USB flash drive (preferably USB3) to be used as your --recov-device. Does this mean i need a second USB drive for the --recov-device drive, i have one if that is the case.
I am just about to try the simplest third method after posting this message thanks Smiley

[moderator's note: consecutive posts merged]
14  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 09, 2025, 01:07:40 AM
So I have put my wallet.dat file into C Python27 and ran the command in Windowspowershell replacing the passphrase with mine ands the name of my wallet.dat file and it came out with
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
I didn't have anything to do with bitcoin open. Does this mean I have to do the other method as it is corrupted.
15  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 08, 2025, 01:14:40 AM
Okay so silly me had a (1) in the middle so I changed that to just pywallet.py and yeah this came up when I retyped the command. I'm guessing this is where I will need my corrupted file in my C python 27 and run the command you sent in an earlier post. Also where will I place the command in all this text.

PS C:\Python27> ./python.exe pywallet.py -h
WARNING:root:pycrypto or libssl not found, decryption may be slow
Usage: pywallet.py [options]

Options:
  --version             show program's version number and exit
  -h, --help            show this help message and exit
  --dump_bip32=DUMP_BIP32
                        dump the keys from a xpriv and a path, usage:
                        --dump_bip32 xprv9s21ZrQH143K m/0H/1-2/2H/2-4
  --bip32_format=BIP32_FORMAT
                        format of dumped bip32 keys
  --passphrase=PASSPHRASE
                        passphrase for the encrypted wallet
  --find_address=FIND_ADDRESS
                        find info about an address
  -d, --dumpwallet      dump wallet in json format
  --dumpformat=DUMPFORMAT
                        choose what to extract in a wallet dump
  --dumpwithbalance     includes balance of each address in the json dump,
                        takes about 2 minutes per 100 addresses
  --importprivkey=KEY   import private key from vanitygen
  --importhex           DEPRECATED, useless
  --datadir=DATADIR     REMOVED OPTION: put full path in the --wallet option
  -w WALLETFILE, --wallet=WALLETFILE
                        wallet filename (defaults to wallet.dat)
  --label=LABEL         label shown in the adress book (defaults to '')
  --testnet             use testnet subdirectory and address type
  --namecoin            use namecoin address type
  --eth                 use ethereum address type
  --otherversion=OTHERVERSION
                        use other network address type, either P2PKH prefix
                        only (e.g. 111) or full network info as
                        'name,p2pkh,p2sh,wif,segwithrp' (e.g. btc,0,0,0x80,bc)
  --info                display pubkey, privkey (both depending on the
                        network) and hexkey
  --reserve             import as a reserve key, i.e. it won't show in the
                        adress book
  --multidelete=MULTIDELETE
                        deletes data in your wallet, according to the file
                        provided
  --balance=KEY_BALANCE
                        prints balance of KEY_BALANCE
  --recover             recover your deleted keys, use with recov_size and
                        recov_device
  --recov_device=RECOV_DEVICE
                        device to read (e.g. /dev/sda1 or E: or a file)
  --recov_size=RECOV_SIZE
                        number of bytes to read (e.g. 20Mo or 50Gio)
  --recov_outputdir=RECOV_OUTPUTDIR
                        output directory where the recovered wallet will be
                        put
  --clone_watchonly_from=CLONE_WATCHONLY_FROM
                        path of the original wallet
  --clone_watchonly_to=CLONE_WATCHONLY_TO
                        path of the resulting watch-only wallet
  --dont_check_walletversion
                        don't check if wallet version > 81000 before running
                        (WARNING: this may break your wallet, be sure you know
                        what you do)
  --random_key          print info of a randomly generated private key
  --whitepaper          write the Bitcoin whitepaper using bitcoin-cli or
                        blockchain.info
  --minimal_encrypted_copy
                        write a copy of an encrypted wallet with only an empty
                        address, *should* be safe to share when needing help
                        bruteforcing the password
  --tests               run tests
16  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 06, 2025, 04:33:38 PM
So I have copy and pasted pywallet into C:\Python27
When I typed in the command   ./python.exe pywallet.py -h   
It came out with   
C:\Python27\python.exe: can't open file 'pywallet.py': [Errno 2] No such file or directory

not sure why it says No such file or directory, maybe I'm being stupid?
17  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 04, 2025, 06:20:00 PM
So  PS C:\Python27> C:/python27/python.exe -V
      Python 2.7.18

Does that mean it is all good now because it shows what version of python I am using. That is on windows PowerShell when i hold shift and right click on  This PC  local disk C  Python 27.
18  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: January 02, 2025, 11:16:37 PM
I can now see the extensions.

Yes I am using windows10. I downloaded python from your link and when I type in the command in PowerShell  > python -s
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases.

I chose to download Windows x86-64 MSI installer and went through the instillation. I can also open python.exe so not sure why i am getting that answer.
I also ran the command python pywallet.py --tests in powershell by shift and right clicking and so fourth where i had "pywallet.py" downloaded and got this answer
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases.
Maybe because my python is not installed correctly
19  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: December 30, 2024, 01:29:00 AM
Code:
python3 pywallet.py
This is the message I get on command prompt Downloads>python3 pywallet.py
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases

Yes that's exactly what was happening when  double-click .py file, it'll print message on CMD and quit immediately.
I presume I'm not using the commands correctly to get pywallet in my downloads folder because as you can see I'm a numpty with them.

know it's a silly question, but have you installed Python? I'm not sure which version of PyWallet you downloaded, but it used to require Python 2.7, and the command was something like this:

Code:
python pywallet.py --dumpwallet --datadir=

or

Code:
python pywallet.py --recover --recov_device=key --recov_size=1000 --recov_outputdir=./recovered --datadir=./wallet

I have downloaded from this link https://github.com/jackjack-jj/pywallet/blob/master/pywallet.py  and it is currently in my downloads folder as pywallet as far as installing it, it keeps going off the second i double click on it.
20  Bitcoin / Bitcoin Technical Support / Re: Recovering private keys from a wallet.dat file on: December 30, 2024, 01:00:33 AM
I have tried to download python (Pywallet) from GitHub but when i try and run it, it instantly crashes on itself and shuts down. I have even tried to run it as administrator. Is it possible to use java? I am using windows 10 pro. Someone please guide me. Undecided

I think that's not the case. If you simply double-click .py file, it'll print message on CMD and quit immediately. You should try open CMD, cd to path where pywallet is located and run this command.

Code:
python3 pywallet.py

This is the message I get on command prompt Downloads>python3 pywallet.py
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases

Yes that's exactly what was happening when  double-click .py file, it'll print message on CMD and quit immediately.
I presume I'm not using the commands correctly to get pywallet in my downloads folder because as you can see I'm a numpty with them.



I have tried to download python (Pywallet) from GitHub but when i try and run it, it instantly crashes on itself and shuts down. I have even tried to run it as administrator. Is it possible to use java? I am using windows 10 pro. Someone please guide me. Undecided

I think that's not the case. If you simply double-click .py file, it'll print message on CMD and quit immidiately. You should try open CMD, cd to path where pywallet is located and run this command.

Code:
python3 pywallet.py
OP: If you do not know how to cd to the path, you can just type cmd in the address bar within the folder that holds "pywallet.py", and CMD will open with the correct path. From there just run the command that ABCbits mentioned and it will run as expected.

There isn't a folder with pywallet.py in it, it is in my downloads as pywallet and if I type cmd in the address bar in my downloads nothing happens. Sorry I'm obviously being stupid.

[moderator's note: consecutive posts merged]
Pages: [1] 2 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!