Dumping private key from hex

[gargouri20011]

I am trying to dump doge wallet private key from corrupted non encrypted wallet. Note: pywallet was unable to dump any private keys.

After some try I found that private key of dogecoin in hex should start with: 3081D30201010420

This is a sample of hex private key in new wallet: 3081D30201010420 0578AA4071328241247763B63134918892FFDA1E3C1DFE402F0A01D623B3FB97

Now i figured out that in order to get the base 58 of my private key : I need to add 2B at the start and then 0134CC212A at the end , so the full hex key will look like:

2B 0578AA4071328241247763B63134918892FFDA1E3C1DFE402F0A01D623B3FB97 0134CC212A

The base58 of this full hex give exactly the private key.

Now the question is how can I generate this hex (0134CC212A) for my corrupted wallet?

I am missing only this in order to get full hex of private key

Thanks for any help 

reward if i can recover wallet 500000 doge .

[1715485810]

1715485810

[1715485810]

1715485810

[1715485810]

1715485810

[achow101]

The hex you are looking for is a checksum. It is the first four bytes of the sha256 double hash of the version byte (0x2b) and the payload (your private key). This process is known as Base 58 Check encoding and you can read about it here: https://en.bitcoin.it/wiki/Base58Check_encoding

[gargouri20011]

Hello
could you please explain , what is the payload of private key or how to get it ?

[achow101]

Hello
could you please explain , what is the payload of private key or how to get it ?

The payload is the private key. The hex private key that you have represents the bytes of the private key. That is the payload.

[gargouri20011]

so  should do checksum (sha256(sha256 (0x2b) and private key in hex) ) ?

could please tell on the example above how to do exactly , i almost tried every combination , still  can't get the 0134CC212A

[achow101]

so  should do checksum (sha256(sha256 (0x2b) and private key in hex) ) ?

Almost. Private key as bytes.

could please tell on the example above how to do exactly , i almost tried every combination , still  can't get the 0134CC212A

You are probably hashing it as a string, not as bytes.

Also, what led you to think that you need to prepend 2b and what led you to think that you need to append 0134CC212A? What makes you think that 3081D30201010420 signals the start of a private key? What makes you think that 0578AA4071328241247763B63134918892FFDA1E3C1DFE402F0A01D623B3FB97 is your private key in hex?

From what I can find, the byte you need to prepend is 0x9e. 0134CC212A does not match the 4 byte checksum for Base58 Check encoding as it is 5 bytes. The private key should also be much longer as unencrypted private keys are stored in the super long form DER format.

[gargouri20011]

ok here what i did . sound like there some confusion here let's clear it out .

i created a new doge wallet DTBZuzsFoXxNu1gUPiwL7Yu64atUcsk7Tm .
Then dumpprivkey DTBZuzsFoXxNu1gUPiwL7Yu64atUcsk7Tm -- > QNoGCcEp6R86Ag5SNPoxVGkXMAx3L2Dedv6BkKJzCEoPSJzE8oLV
Then went here : https://walletgenerator.net/
This site show private key hex as : 0578AA4071328241247763B63134918892FFDA1E3C1DFE402F0A01D623B3FB97
opened hex editor searching for the string :
i found the string , as i said above all doge wallet private key has a start hex of 3081D30201010420   .

3081D30201010420 0578AA4071328241247763B63134918892FFDA1E3C1DFE402F0A01D623B3FB97


now when i do a base58 decode of the private key (QNoGCcEp6R86Ag5SNPoxVGkXMAx3L2Dedv6BkKJzCEoPSJzE8oLV)  here is what i get :

9E 0578AA4071328241247763B63134918892FFDA1E3C1DFE402F0A01D623B3FB97 (0134CC212A)


Here is the same procedure for another wallet :
New wallet : D6Rka31SFm8PnN2Cs9QWj5YcfzRpkXx6fw
Then dumpprivkey D6Rka31SFm8PnN2Cs9QWj5YcfzRpkXx6fw -- > QQToBX1SQBSuZo8ijsTLyL7cx9gn9QjK8s7XCBHXy8AUF2om1tNs
Then went here : https://walletgenerator.net/
This site show private key hex as : 3721D639228B9215C6BFF746CA163391CDBADB8566FC8FECB74871E8FAA24FE7
opened hex editor searching for the string :
i found the string , as i said above all doge wallet private key has a start hex of 3081D30201010420   .

3081D30201010420  3721D639228B9215C6BFF746CA163391CDBADB8566FC8FECB74871E8FAA24FE7

now when i do a base58 decode of the private key (QNoGCcEp6R86Ag5SNPoxVGkXMAx3L2Dedv6BkKJzCEoPSJzE8oLV)  here is what i get :
9E 3721D639228B9215C6BFF746CA163391CDBADB8566FC8FECB74871E8FAA24FE7 (015B6ADEE0)


I hope that you get the point all that i need now is to generate this (015B6ADEE0 or 0134CC212A ) for my own wallet .

[achow101]

ok here what i did . sound like there some confusion here let's clear it out .

i created a new doge wallet DTBZuzsFoXxNu1gUPiwL7Yu64atUcsk7Tm .
Then dumpprivkey DTBZuzsFoXxNu1gUPiwL7Yu64atUcsk7Tm -- > QNoGCcEp6R86Ag5SNPoxVGkXMAx3L2Dedv6BkKJzCEoPSJzE8oLV
Then went here : https://walletgenerator.net/
This site show private key hex as : 0578AA4071328241247763B63134918892FFDA1E3C1DFE402F0A01D623B3FB97
opened hex editor searching for the string :
i found the string , as i said above all doge wallet private key has a start hex of 3081D30201010420   .

3081D30201010420 0578AA4071328241247763B63134918892FFDA1E3C1DFE402F0A01D623B3FB97


now when i do a base58 decode of the private key (QNoGCcEp6R86Ag5SNPoxVGkXMAx3L2Dedv6BkKJzCEoPSJzE8oLV)  here is what i get :

9E 0578AA4071328241247763B63134918892FFDA1E3C1DFE402F0A01D623B3FB97 (0134CC212A)


Here is the same procedure for another wallet :
New wallet : D6Rka31SFm8PnN2Cs9QWj5YcfzRpkXx6fw
Then dumpprivkey D6Rka31SFm8PnN2Cs9QWj5YcfzRpkXx6fw -- > QQToBX1SQBSuZo8ijsTLyL7cx9gn9QjK8s7XCBHXy8AUF2om1tNs
Then went here : https://walletgenerator.net/
This site show private key hex as : 3721D639228B9215C6BFF746CA163391CDBADB8566FC8FECB74871E8FAA24FE7
opened hex editor searching for the string :
i found the string , as i said above all doge wallet private key has a start hex of 3081D30201010420   .

3081D30201010420  3721D639228B9215C6BFF746CA163391CDBADB8566FC8FECB74871E8FAA24FE7

now when i do a base58 decode of the private key (QNoGCcEp6R86Ag5SNPoxVGkXMAx3L2Dedv6BkKJzCEoPSJzE8oLV)  here is what i get :
9E 3721D639228B9215C6BFF746CA163391CDBADB8566FC8FECB74871E8FAA24FE7 (015B6ADEE0)


I hope that you get the point all that i need now is to generate this (015B6ADEE0 or 0134CC212A ) for my own wallet .

I see. And where did the 2B come from?

Anyways, I see the problem. The 01 is actually part of the payload (i.e. the private key). It is a flag byte that signals that the private key should be used with a compressed public key. So the bytes you actually hash is

Code:

9E3721D639228B9215C6BFF746CA163391CDBADB8566FC8FECB74871E8FAA24FE701

Hashing those as bytes with sha256d (you can use a tool like http://www.fileformat.info/tool/hash.htm) yields the following hash:

Code:

5b6adee01d509671a81c129ab5395c906df775bb0520a633e862a62c76458f20

The first 4 bytes of that hash matches the checksum that you need: 5b6adee0

[gargouri20011]

Big thank for your help now i have to go over all those 3081D30201010420 there is a ton of them ,
If i will recover the doge i will contact you to send you the 500k doge

[Wyre08]

Just out of curiosity how much Dogecoin do you have in the wallet that you're offering $500usd to recover it.

Good luck btw. Sorry I can't help.

[gargouri20011]

i am still testing all key now , there are 5 ml doge on it

[gargouri20011]

right now i am writing a script to check all keys ,
I did not understand what u mean exactly ?
0x953721D639228B9215C6BFF746CA163391CDBADB8566FC8FECB74871E8FAA24FE7 is WIF private key ?
could y explain what to do exactly ?

[gargouri20011]

Got it , but isn't this the same as above ?

[gargouri20011]

i finished work on it , i got about 1500 keys and imported them via rpc cli . overall balance 0 . so none of those keys are my real key