Hold on, hold on! Before you think we're scamming, please read this.
So you propably heard of people selling wallet.dat files, right? And that they're fake if sold online, right? We decided to give it a shot and oh, surprise, it indeed was a scam (glad we didn't spend money).
But we had already built a software to spread workload over multiple computers, allowing for faster processing time. So we thought about what we should do next, what the next step should be.
So this is how we came up with the idea to use our available processing power for a good purpose. And, well, that's why you are reading this post right now!
You're likely asking yourself how you can make sure you actually receive a valid password without us saying "yoink" and stealing it all. For that, you need to know what actually is inside of wallet.dat.
Inside of the BerkelyDB of the wallet.dat is a hash (the password hash). It can, for instance, look like this:
$bitcoin$64$24b4a225bbf86972233aec387401b536ef1fe333fd18cf15d13e8fe1b1acfbe2$16$7363b105beaf4028$36762$2$00$2$00
You can extract some values from it, in this case for instance:
Hash: 24b4a225bbf86972233aec387401b536ef1fe333fd18cf15d13e8fe1b1acfbe2
Salt: 7363b105beaf4028
Rounds: 36762
Cycling through the hash value gives us a realistic chanche to crack 8 digit passwords, even more if there is a hint from the owner. This is where we come into play.
We have the processing power needed for the job, the only thing we are missing are clients. If you're interesting in being our first, then please dm us!
TL;DR:
- we can decrypt the passwords
- we do not need access to the actual wallet for it
- we do not charge upfront
It works for basically all wallets hashcat supports
