atithasos
|
|
April 18, 2021, 06:33:58 AM |
|
Hello Jack, is it possible to send me the 0.8 version of bitcoin? i try to find executable for windows or a way to make it but nothing. can you please help me? thanks in advance
|
BTC: 18Kz4PHHNaRndxUhsCU6wWSpNjkucPuF7S
|
|
|
HCP
Legendary
Offline
Activity: 2086
Merit: 4316
<insert witty quote here>
|
|
April 18, 2021, 08:07:41 AM |
|
is it possible to send me the 0.8 version of bitcoin? i try to find executable for windows or a way to make it but nothing.
Bitcoin Core 0.8.6 is available on the Bitcoin Core download repository... you just have to "hunt" for it a little bit: https://bitcoincore.org/bin/insecure/bitcoin-core-0.8.6/ Do note that this is in the "insecure" folder for a reason... there are security vulnerabilities in this old versions. Caution is advised.
|
|
|
|
malevolent
can into space
Legendary
Offline
Activity: 3472
Merit: 1722
|
|
April 18, 2021, 08:15:11 AM |
|
Hello Jack, is it possible to send me the 0.8 version of bitcoin? i try to find executable for windows or a way to make it but nothing. can you please help me? thanks in advance If you want the 0.8 version specifically, it's here: https://github.com/bitcoin/bitcoin/releases/tag/v0.8.0Just make sure you get all of the required dependencies right, as some of them are so old they might not be in your system's default repository. It would also probably be difficult to make this version sync with the current network. edit: or not, oldest node I found is 0.8.1 https://bitnodes.io/nodes/45.127.186.188-8333/
|
Signature space available for rent.
|
|
|
jonocodes
Newbie
Offline
Activity: 2
Merit: 0
|
|
April 24, 2021, 10:45:28 PM |
|
Probably user error, but I've tried a few different tactics to get pywallet working with Dogecoin. I've got a few old wallets we recovered from an old hard drive. Is there any special option I have to pass in to get it to work? python pywallet.py -d -w /<AREALLYCOOLPATH>/wallet.dat.r1 --passphrase=xxxxxx WARNING:root:pycrypto or libssl not found, decryption may be slow (22, 'Invalid argument -- __db_meta_setup: /Users/jono/pywallet/wallet.dat: unexpected file type or format') ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
I've tried this, I've tried downloading the super old https://github.com/01BTC10/dogecoin-pywallet to a file pywallet_doge_old.py - and ran with this: python pywallet_doge_old.py --datadir=<PATH> --wallet=wallet.dat.r1 --otherversion 30 --dumpwallet --passphrase=xxxxxxx #=> WARNING:root:pycrypto or libssl not found, decryption may be slow ERROR:root:Couldn't open wallet.dat/main. Try quitting Dogecoin and running this again.
I don't have Dogecoin running nor installed, I also had to get creative to get all the dependencies for pywallet installed - I'd be screwed if I wasn't a developer :vomit: Anyone have any feedback?
|
|
|
|
HCP
Legendary
Offline
Activity: 2086
Merit: 4316
<insert witty quote here>
|
|
April 25, 2021, 09:25:32 PM |
|
Have you tried downloading the Dogecoin Core wallet and opening the wallet.dat files with that? You don't need the dogecoin blockchain synced to be able to open the wallet. Just shutdown Dogecoin Core, then replace the wallet.dat in the Dogecoin data directory with a copy of one of your old wallets (renamed as wallet.dat) and then restart Dogecoin Core. If the wallet file is actually corrupt, you'll likely get errors from Dogecoin Core saying so. If you don't get any errors, you can try using walletpassphrase and dumpwallet from the Core client console to dump the keys from the wallet file.
|
|
|
|
|
HCP
Legendary
Offline
Activity: 2086
Merit: 4316
<insert witty quote here>
|
|
April 26, 2021, 05:21:17 AM |
|
Not overly familiar with the Dogecoin Core client (I've used it but not extensively)... but it might have the -salvagewallet option that might be able to recover something? Failing that, Python2.7 and an old copy of PyWallet before the latest 2021 updates (made by JackJack recently) might be your best bet with a Dogecoin wallet.dat. Either this version from the last commit back in 2014... or you can try my one here: https://github.com/HardCorePawn/pywalletBasically, the only mods I had made from the 2014 version were to stop it complaining about "key-meta" records and such that were in "newer" wallet.dat's.
|
|
|
|
morbius55
|
|
May 10, 2021, 09:43:22 PM |
|
Is the latest update useable and stable? Python 3 supported? Thanks.
|
|
|
|
strig1
Newbie
Offline
Activity: 4
Merit: 0
|
|
May 16, 2021, 06:49:24 PM |
|
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: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 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!
|
|
|
|
morbius55
|
|
May 17, 2021, 06:20:00 PM Last edit: May 17, 2021, 06:41:01 PM by morbius55 |
|
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".
If you see error message when you open Bitcoin Core normally, you can external Bitcoin Core tools to salvage your wallet properly. Check this thread, Salvagewallet in latest Bitcoin core. My next step is to recover the HDD using GetDataBack instead of Recuva, and then reattempt what I have done so far.
I strongly suggest you to make RAW copy of your HDD using tools such as http://www.hddguru.com/software/HDD-Raw-Copy-Tool/. After doing that, you can use the software to scan the RAW copy instead. If you're searching text with a hex editor then you need to type key!. The exclamation mark is important, but is not used for the master key (mkey). You might not get a hit on the word name as that doesn't always appear in a wallet.dat. It is another term for address. If the wallet was encrypted by using a passphrase, then the private keys should be searched by the term ckey! if using a hex editor.
|
|
|
|
strig1
Newbie
Offline
Activity: 4
Merit: 0
|
|
May 17, 2021, 10:01:05 PM |
|
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".
If you see error message when you open Bitcoin Core normally, you can external Bitcoin Core tools to salvage your wallet properly. Check this thread, Salvagewallet in latest Bitcoin core. My next step is to recover the HDD using GetDataBack instead of Recuva, and then reattempt what I have done so far.
I strongly suggest you to make RAW copy of your HDD using tools such as http://www.hddguru.com/software/HDD-Raw-Copy-Tool/. After doing that, you can use the software to scan the RAW copy instead. If you're searching text with a hex editor then you need to type key!. The exclamation mark is important, but is not used for the master key (mkey). You might not get a hit on the word name as that doesn't always appear in a wallet.dat. It is another term for address. If the wallet was encrypted by using a passphrase, then the private keys should be searched by the term ckey! if using a hex editor. I searched for 'mkey', 'ckey', 'key!', and 'key' using a Hex Editor and I only got 1 match for 'key', nothing else. Can I do anything with this? I am in the process of making a raw copy of my HDD using HDD-Raw-Copy-Tool and searching that for a wallet.dat file. Will probably have to delay that until the weekend though.
|
|
|
|
morbius55
|
|
May 17, 2021, 10:08:03 PM |
|
Did you run pywallet as administrator? Also I wouldn't count on recovery software to be the best option. I would run pywallet on the whole hard drive rather than on a file you recovered via recuva or whatever software. Make sure you include the passphrase when you run pywallet, if the wallet was encrypted. If It finds any private keys you can then use them with Electrum, I don't think you can just use a wallet recovered by pywallet straight into Bitcoin Core. Obviously it will be safer to try this on your cloned version of the hard drive. Good luck.
|
|
|
|
strig1
Newbie
Offline
Activity: 4
Merit: 0
|
|
May 17, 2021, 10:42:47 PM Last edit: May 18, 2021, 02:54:09 AM by strig1 |
|
Did you run pywallet as administrator? Also I wouldn't count on recovery software to be the best option. I would run pywallet on the whole hard drive rather than on a file you recovered via recuva or whatever software. Make sure you include the passphrase when you run pywallet, if the wallet was encrypted. If It finds any private keys you can then use them with Electrum, I don't think you can just use a wallet recovered by pywallet straight into Bitcoin Core. Obviously it will be safer to try this on your cloned version of the hard drive. Good luck.
I will try running pywallet as admin on the entire hard drive. What command should i run for a 1TB HDD. Will the below command work? I appreciate the help! python pywallet.py --recover --recov_device=E: --recov_size=932Gio --recov_outputdir=. EDIT: I figured out the code to run this and fixed it above.
|
|
|
|
HCP
Legendary
Offline
Activity: 2086
Merit: 4316
<insert witty quote here>
|
|
May 18, 2021, 03:26:44 AM |
|
recov_device should just be the drive letter (in windows) if you want to check an entire drive... you don't want to specify a "file" Try: python pywallet.py --recover --recov_device=E: --recov_size=1000Gio --recov_outputdir=.
|
|
|
|
strig1
Newbie
Offline
Activity: 4
Merit: 0
|
|
May 19, 2021, 12:09:33 AM |
|
recov_device should just be the drive letter (in windows) if you want to check an entire drive... you don't want to specify a "file" Try: python pywallet.py --recover --recov_device=E: --recov_size=1000Gio --recov_outputdir=.
Thank you this worked! I got a recovered wallet.dat file that was much bigger than my original (~1000KB) with a bunch of keys in it. I ran the code below and got a few hundred addresses. My Bitcoin Core is fully synced and I tried opening this wallet but get stuck on "Opening Wallet. Not sure what do next. pywallet.py --dumpwallet --wallet=wallet.dat > walletdump.txt Example Output: "addr": "1GK46gd6C8nXXXXXXXXXXXX3HMgbqHF", "compressed": false, "encrypted_privkey": "5613a75d7ad6c19135a26eXXXXXXXXXXXXXXXX1908e61cb08cf49e21dXXXXXb1c65142912", "label": "recovered: 93bfXXXXXXXXXXXXXXXXXX710881d50XXXXX89585154c", "pubkey": "04ef1bc57033e7942233fb6d21f421XXXXXXXXXXXXXXXXXXXXXXXXXX6f74cf794ced69144dbb379c373d4b780fa4151bb50a3", "reserve": 0 },
|
|
|
|
madmartyk
Legendary
Online
Activity: 2688
Merit: 1030
Yes I am a pirate, 300 years too late!
|
|
May 19, 2021, 12:49:43 AM |
|
Import the keys into a blank wallet.
|
|
|
|
Drawn23s
Newbie
Offline
Activity: 4
Merit: 0
|
|
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: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 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?
|
|
|
|
HCP
Legendary
Offline
Activity: 2086
Merit: 4316
<insert witty quote here>
|
|
May 19, 2021, 07:06:54 AM |
|
My Bitcoin Core is fully synced and I tried opening this wallet but get stuck on "Opening Wallet. Not sure what do next.
It's likely that Bitcoin Core was "rescanning" your "new" wallet with all the recovered keys in it... it will be starting from basically block 0... and this can take several hours to complete. Check the debug.log in your Bitcoin Core datadir... you should hopefully see a bunch of debug lines like this: ... 2021-05-19T05:59:34Z [default_wallet] Still rescanning. At block 538973. Progress=0.525272 2021-05-19T06:00:34Z [default_wallet] Still rescanning. At block 544471. Progress=0.538657 2021-05-19T06:01:34Z [default_wallet] Still rescanning. At block 550317. Progress=0.555550 2021-05-19T06:02:34Z [default_wallet] Still rescanning. At block 555563. Progress=0.571671 2021-05-19T06:03:34Z [default_wallet] Still rescanning. At block 561564. Progress=0.590429 ...
It should also give you an idea how how quickly it is syncing... note that the progress value is from 0 to 1.0, where 1.0 == 100%... so in the lines above... the last line was at just over 59% complete
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?
Sounds like a corrupted recovery... or possibly the text editor you're using is formatting the binary data in a really weird way... what text editor did you use? I'd recommend Notepad++ If Pywallet isn't able to find any keys to recover, then it's possible the recovered wallet is too badly damaged or the data has been overwritten on disk, so it wasn't able to find anything resembling a wallet.dat. It can be a bit "hit and miss"... so maybe try different recovery software... or maybe raw image the drive then try scanning the raw image for the hex markers for wallet.dat fields/private keys etc
|
|
|
|
Drawn23s
Newbie
Offline
Activity: 4
Merit: 0
|
|
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?
|
|
|
|
HCP
Legendary
Offline
Activity: 2086
Merit: 4316
<insert witty quote here>
|
|
May 19, 2021, 07:33:35 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.
|
|
|
|
|