+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: Bitcoin private keys (/thread-13386.html)
Bitcoin private keys - pbies - 09-18-2025
I have three huge sets of data:
1. hash160 = RIPEMD160, which is in format 40 digits hex (that's the result of public key hashing)
2. brainwallets=passwords that I want to check (convert), one per line
3. addresses with '1' at the start (I can base58check decode them to hash160), one per line
Using modes 6000 and 28501 how should I work with these files to check as much as I can?
I don't know what the input data format should be for check against these 3.
Can I check for all of these for one piece at a one run of hashcat, or can I prepare a list that it will be checked against the above?
RE: Bitcoin private keys - pbies - 09-18-2025
Raw hash (mode 6000), cryptocurrency wallet (mode 28501) - what are these?
Raw hash in bytes or hex, what about few of them in input file?
Wallet - a wallet.dat file or private keys in WIF/hex format in input file?
RE: Bitcoin private keys - pbies - 09-18-2025
I can see that when searching for 6000/28501 we need:
012cb9b334ec1aeb71a9c8ce85586082467f7eb6
or
1Jv6EonXm9x4Dw4QjEPAhGfmzFxTL7b3Zj
respectively.
But what is in the other file we put into hashcat?
Will be there going any conversion? What is the source format for both modes files?
RE: Bitcoin private keys - pbies - 09-18-2025
Ok, for now I know, that
mode 6000 is getting RIPEMD160 hashes in one file (to which is the comparison and coversion) and brainwallets in second.
Have found some hashes.
28501 seems to be not needed for me now.