Bitcoin Forum
May 08, 2024, 01:56:42 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: Found my old wallet.dat which seems to be corrupted. Please Help.  (Read 410 times)
nc50lc
Legendary
*
Offline Offline

Activity: 2408
Merit: 5591


Self-proclaimed Genius


View Profile
November 11, 2022, 04:55:20 AM
Merited by Welsh (2)
 #21

Then I used pywallet to dump the keys from the corrupted wallet.dat file that was found. In the wallet.text file that pywallet generated, I found this 51 character key, along with an address. The address is valid and had one transaction as per blockchain explorer all the way back from 2011. Its a miniscule amount, though worth recovering as I am taking this as a learning experience incase I find the real missing wallet.
Does the "51 character key" written next to "sec":?
Because that's the WIF prvKey of the address above it; if it's in any other line, it's just a coincidence.

IDK if Pywallet will be able to dump corrupted private keys but since you're copy-pasting and it's invalid, then it might be the case.
But it's the encoding that's the issue and raw prvKeys in wallet.dat files aren't base58check encoded, perhaps it's an issue in Pywallet, try an earlier version.

.
.HUGE.
▄██████████▄▄
▄█████████████████▄
▄█████████████████████▄
▄███████████████████████▄
▄█████████████████████████▄
███████▌██▌▐██▐██▐████▄███
████▐██▐████▌██▌██▌██▌██
█████▀███▀███▀▐██▐██▐█████

▀█████████████████████████▀

▀███████████████████████▀

▀█████████████████████▀

▀█████████████████▀

▀██████████▀▀
█▀▀▀▀











█▄▄▄▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
.
CASINSPORTSBOOK
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀▀█











▄▄▄▄█
1715133402
Hero Member
*
Offline Offline

Posts: 1715133402

View Profile Personal Message (Offline)

Ignore
1715133402
Reply with quote  #2

1715133402
Report to moderator
Even in the event that an attacker gains more than 50% of the network's computational power, only transactions sent by the attacker could be reversed or double-spent. The network would not be destroyed.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715133402
Hero Member
*
Offline Offline

Posts: 1715133402

View Profile Personal Message (Offline)

Ignore
1715133402
Reply with quote  #2

1715133402
Report to moderator
1715133402
Hero Member
*
Offline Offline

Posts: 1715133402

View Profile Personal Message (Offline)

Ignore
1715133402
Reply with quote  #2

1715133402
Report to moderator
1715133402
Hero Member
*
Offline Offline

Posts: 1715133402

View Profile Personal Message (Offline)

Ignore
1715133402
Reply with quote  #2

1715133402
Report to moderator
givemebackmybtc (OP)
Newbie
*
Offline Offline

Activity: 12
Merit: 5


View Profile
November 11, 2022, 05:36:47 PM
 #22

Then I used pywallet to dump the keys from the corrupted wallet.dat file that was found. In the wallet.text file that pywallet generated, I found this 51 character key, along with an address. The address is valid and had one transaction as per blockchain explorer all the way back from 2011. Its a miniscule amount, though worth recovering as I am taking this as a learning experience incase I find the real missing wallet.
Does the "51 character key" written next to "sec":?
Because that's the WIF prvKey of the address above it; if it's in any other line, it's just a coincidence.

IDK if Pywallet will be able to dump corrupted private keys but since you're copy-pasting and it's invalid, then it might be the case.
But it's the encoding that's the issue and raw prvKeys in wallet.dat files aren't base58check encoded, perhaps it's an issue in Pywallet, try an earlier version.

Yes the key sits next to sec:

I'll try dumping they keys using a different version of pywallet
Berkeleydb1
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
November 11, 2022, 06:41:36 PM
 #23

Then I used pywallet to dump the keys from the corrupted wallet.dat file that was found. In the wallet.text file that pywallet generated, I found this 51 character key, along with an address. The address is valid and had one transaction as per blockchain explorer all the way back from 2011. Its a miniscule amount, though worth recovering as I am taking this as a learning experience incase I find the real missing wallet.
Does the "51 character key" written next to "sec":?
Because that's the WIF prvKey of the address above it; if it's in any other line, it's just a coincidence.

IDK if Pywallet will be able to dump corrupted private keys but since you're copy-pasting and it's invalid, then it might be the case.
But it's the encoding that's the issue and raw prvKeys in wallet.dat files aren't base58check encoded, perhaps it's an issue in Pywallet, try an earlier version.

Yes the key sits next to sec:

I'll try dumping they keys using a different version of pywallet


Hello my friend i need a guide for macomk pywallet. I'm a beginner and I don't have enough knowledge, can you please explain like you would to an idiot? I've been waiting for months I need your help for macomk, please help.

givemebackmybtc (OP)
Newbie
*
Offline Offline

Activity: 12
Merit: 5


View Profile
November 11, 2022, 07:35:18 PM
 #24

Then I used pywallet to dump the keys from the corrupted wallet.dat file that was found. In the wallet.text file that pywallet generated, I found this 51 character key, along with an address. The address is valid and had one transaction as per blockchain explorer all the way back from 2011. Its a miniscule amount, though worth recovering as I am taking this as a learning experience incase I find the real missing wallet.
Does the "51 character key" written next to "sec":?
Because that's the WIF prvKey of the address above it; if it's in any other line, it's just a coincidence.

IDK if Pywallet will be able to dump corrupted private keys but since you're copy-pasting and it's invalid, then it might be the case.
But it's the encoding that's the issue and raw prvKeys in wallet.dat files aren't base58check encoded, perhaps it's an issue in Pywallet, try an earlier version.

Different versions of pywallet end up dumping the same exact private key  Undecided

Last option, try to fully restore the deleted files from the HDD, and see if I can find the actual wallet.dat file manually.

I'm guessing like you mentioned the wallet.dat is too corrupt and it won't dump the keys correctly.
nc50lc
Legendary
*
Offline Offline

Activity: 2408
Merit: 5591


Self-proclaimed Genius


View Profile
November 12, 2022, 03:53:49 AM
Merited by Welsh (2), ABCbits (1)
 #25

Different versions of pywallet end up dumping the same exact private key  Undecided
Try to run: pywallet --tests
And see if you will get encoding-related errors.

Just to be sure, does your importprivkey command looks like this?:
Code:
importprivkey "51qecEjLcNQony2W6PrivateKeyNotValidq4dfJP8sHgeVKaU3"
Code:
importprivkey "51qecEjLcNQony2W6PrivateKeyNotValidq4dfJP8sHgeVKaU3" "label" true
No other signs aside from the quotation marks or even without those.

.
.HUGE.
▄██████████▄▄
▄█████████████████▄
▄█████████████████████▄
▄███████████████████████▄
▄█████████████████████████▄
███████▌██▌▐██▐██▐████▄███
████▐██▐████▌██▌██▌██▌██
█████▀███▀███▀▐██▐██▐█████

▀█████████████████████████▀

▀███████████████████████▀

▀█████████████████████▀

▀█████████████████▀

▀██████████▀▀
█▀▀▀▀











█▄▄▄▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
.
CASINSPORTSBOOK
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀▀█











▄▄▄▄█
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!