I've got two wallets that have the same "ckey" and the first 32 characters of their "mkeys" match. Is there a quick way to get the "keymaterial" to access the ckey or mkey for my private key(s)? I need some guidance here... If I manage to get into my wallets, I promise there'll be a reward. Oh, and by the way, I'm using ./crackBTCwallet from albertoBSD to try and find the key for my ckey or mkey. When I dumped both wallets using pywallet, I found that info above.
Thanks
Do you mean this application https://github.com/albertobsd/crackBTCwallet? If so, you may want until user @albert0bsd give detailed answer.
If i understood how his program correctly, you could just use follow steps on section "Getting the PrivKey in WIF format".
But i can't verify whether i got it right, since compiled ./crackBTCwallet on my Debian VM doesn't show both command.
I got that from crackBTCwallet from albertoBSD Github page.
But I want to know is there any short way to get the "key material" to run "aesdecrypt" . In my case it's unique that 2 different wallets have same "ckey" and first 32 letters of my mkeys are same. There should be a ashort way to get the key material..
Hope someone will help..
Thanx
This means that those two wallets include the same encrypted private key.
Those first "32 letters" are part of the Encrypted AES Key's size (first 'two letters') followed by the encrypted AES Key itself.
Since it has the same private key but the other values aren't, that could mean that those are copies of the same previously unencrypted wallet,
Each copy was encrypted by different machines and/or passphrases.
Could be corruption or any alteration that can change the rest of the data.
You mean something that can utilize those matching data to decrypt the mkey?
No, you need either wallet's passphrase to decrypt its "mkey", the result is used to decrypt that "ckey".