Bitcoin Forum
November 12, 2024, 05:47:25 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Development & Technical Discussion / Re: Pywallet 2.2: manage your wallet [Update required] on: May 19, 2021, 11:42:44 AM
So i use the --dumpwallet command on the recoveredwallet into wallet.txt?
I'd try Bitcoin Core first... nothing to lose, easiest way to go about it. Just make a copy of the .dat file... then try opening it with Bitcoin Core... just be prepared to wait while it rescans the blockchain looking for transactions. Note this is NOT redownloading the blocks (assuming your node is NOT pruned), it just has to scan the block data.


and then how do i import those into a wallet of my choice.
Really depends on what wallet you want to import it too... But the --dumpwallet command should give you the private keys in WIF format... assuming that you include the --passphrase parameter when dumping the wallet.


For Bitcoin Core, you just use the importprivkey command on the console in Bitcoin Core (make sure to set rescan to false until you import the last key, otherwise it will run rescan every. single. time. Shocked Shocked Shocked)

Or you can look up one of the many many many guides on how to import private keys into Electrum... Like this one: https://bitcoinelectrum.com/importing-your-private-keys-into-electrum/

Google is your friend. Wink

ty i try to google when I can, just was confused on a few things that you set straight. Appreciate it.
2  Bitcoin / Development & Technical Discussion / Re: Pywallet 2.2: manage your wallet [Update required] on: May 19, 2021, 07:40:45 AM
a recovered_wallet.dat may or may not open with Bitcoin Core... theoretically, it should be compatible, so you should be able to open it directly... but it's possible that pywallet is not creating it in a format that Bitcoin Core can handle.

In which case, dumping the private keys out of it, then importing those into the wallet of your choice would be a viable solution.


Note that Electrum would enable you to import and scan the keys in a matter of minutes, whereas rescanning in Bitcoin Core could take hours. Neither guarantees that the "keys" found are actually going to contain any coins.

So i use the --dumpwallet command on the recoveredwallet into wallet.txt? and then how do i import those into a wallet of my choice. I have bitcoincore installed. almost done dling the blockchain


or should i just try opening the wallet in bitcoin core first. the old wallets were from 2013
3  Bitcoin / Development & Technical Discussion / Re: Pywallet 2.2: manage your wallet [Update required] on: May 19, 2021, 07:13:00 AM
Ok so I ran --recover on the old computer and got recovered wallet and pywallet partial recovery json what do I do next? dumpwallet? and then I import the keys with bitcoin core somehow? or do i just try to open the wallet with bitcoin core?
4  Bitcoin / Development & Technical Discussion / Re: Pywallet 2.2: manage your wallet [Update required] on: May 19, 2021, 01:17:57 AM
Hello I used Recuva on an old HDD from 2013/2014 and found a wallet.dat file. Recuva said the wallet.dat file was in excellent condition. I tried using 2 versions of Bitcoin Core (0.21.1 and 0.8.6) to read the wallet.dat and was given the warning "wallet.dat corrupt, salvage failed". I installed Python 2.7.11, Pywallet, and all its dependencies and tried the following commands.


Pywallet DumpWallet Attempt:
Code:
python pywallet.py --dumpwallet --datadir=./ --wallet=wallet.dat

'ecdsa' package is not installed, pywallet won't be able to sign/verify messages
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again. (Bitcore was not open)

Pywallet Recovery Attempt:
I reformatted a flash drive in FAT32 and put the wallet.dat file in it and attempted the following recovery code
Code:
python pywallet.py --recover --recov_device=E:\wallet.dat  --recov_size=14.5Gio --recov_outputdir=.

Found 0 possible wallets
Found 0 possible encrypted keys
Found 0 possible unencrypted keys
WindowsError: exception: access violation reading 0x000000005FF07E98

The wallet.dat file is 328KB. I inspected it using a HexEditor and Notepad++ and it doesn't look corrupted. When I search notepad++ for 'key', there is 1 match, but when I search for 'name' there are no matches. My next step is to recover the HDD using GetDataBack instead of Recuva, and then reattempt what I have done so far. I would appreciate any help!

I'm in the same boat as this guy. Except things are shuffled in the wallet. I can find ke and y1 and na and me but pywallet leads to the same error. Also don't remember getting that windows error. I did try --recover but no keys or possible wallets were found. Any ideas what command to try or where to proceed next?
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!