Search content
Sort by
Showing 6 of 6 results by mikecolins
Re: Don't buy "wallet.dat" files with lost passwords; EXCHANGE THEM.
Hi!
I have done some "research" on wallets.dat I got, don't mean that they are the same like here, but you should check, before you try to guess the password...
at the following wallet if you compare the files in a simple way the iteration is the same.
All have: 35714
10.08 1EQjwXjyom9T35764huyriFEredLGmneVC
12.8219 19tLSCZWhX5YBVy6uX2kLheNjdUb9RBojS
22.85 19Hj5Pzi4hCj12porw97i183XYTrScbtXS
42.2445 1NKmf6GszBQ6wo349LUT4Je1csNyDDpb5Y
I'd say it very unlikely that so much wallets have the same, iteration!
Maybe this is only true for my files, but check this...
Bye
I have done some "research" on wallets.dat I got, don't mean that they are the same like here, but you should check, before you try to guess the password...
at the following wallet if you compare the files in a simple way the iteration is the same.
All have: 35714
10.08 1EQjwXjyom9T35764huyriFEredLGmneVC
12.8219 19tLSCZWhX5YBVy6uX2kLheNjdUb9RBojS
22.85 19Hj5Pzi4hCj12porw97i183XYTrScbtXS
42.2445 1NKmf6GszBQ6wo349LUT4Je1csNyDDpb5Y
I'd say it very unlikely that so much wallets have the same, iteration!
Maybe this is only true for my files, but check this...
Bye
Hey, that's incredible remark!
Then it's is possible to assume that duplicate iterations are crafted fake wallets.
Code:
cat all.btc.hashes | cut -d'$' -f7 | sort | uniq -c | sort -nr
If you'll see in the result more than one instance of iteration - don't waste time on itI will be more than happy if author of this thread will check his wallet hashes for duplicate iterations and mark them as probably fake
Thanks!
Re: Don't buy "wallet.dat" files with lost passwords; EXCHANGE THEM.
I also have some wallet .dat in my possession if you want to replace it.
Hello N1OTC.
What do you mean "replace it"?
A greeting.
Probably he means "exchange" and not replace.
Re: Don't buy "wallet.dat" files with lost passwords; EXCHANGE THEM.
For the reference: https://github.com/hashcat/hashcat/blob/master/docs/hashcat-brain.md
Just a simple example:
you run an attack on some hash (no matter which type 3 or 0):
1. hashcat -m 11300 -a 0 myholywallet.hash some_dictionary.txt -r very_cool_rules.rule
2. it fails, and you decide to make another attack then another and another
3. you execute again attack #1 because you've already forgot about it
4. hashcat brain checks if it already done it in it's database, and if so - rejects all password candidates.
5. You earn the time of not doing the same work twice (or more)
Just a simple example:
you run an attack on some hash (no matter which type 3 or 0):
1. hashcat -m 11300 -a 0 myholywallet.hash some_dictionary.txt -r very_cool_rules.rule
2. it fails, and you decide to make another attack then another and another
3. you execute again attack #1 because you've already forgot about it
4. hashcat brain checks if it already done it in it's database, and if so - rejects all password candidates.
5. You earn the time of not doing the same work twice (or more)
Re: Don't buy "wallet.dat" files with lost passwords; EXCHANGE THEM.
I was following this topic for a while and decided now to jump in.
I don't know if I am allowed to post link here so I will provide it through private messaging.
I am sitting here on an old wallet.dat with 50 BTC.
After reading all the comments in this thread I decided to set up a solution to share wallet hashes (not the wallet file).
This solution also splits the brute force tasks among a hashcat connected network of computers.
The only knowledge required is to be able to install python (as well as 2 extensions) to run the client.
It downloads by itself the necessary files (hashcat, the hash files and, if necessary the dictionary files) and share online the resources with the others.
For me the wallet is lost, so if peoples are interest to jump in, they only need to contact me and I'll configure them an account to share the resources.
If we are able to find the password, I will share the 50BTC to all involved participants.
I don't know if I am allowed to post link here so I will provide it through private messaging.
I am sitting here on an old wallet.dat with 50 BTC.
After reading all the comments in this thread I decided to set up a solution to share wallet hashes (not the wallet file).
This solution also splits the brute force tasks among a hashcat connected network of computers.
The only knowledge required is to be able to install python (as well as 2 extensions) to run the client.
It downloads by itself the necessary files (hashcat, the hash files and, if necessary the dictionary files) and share online the resources with the others.
For me the wallet is lost, so if peoples are interest to jump in, they only need to contact me and I'll configure them an account to share the resources.
If we are able to find the password, I will share the 50BTC to all involved participants.
Hey, it's definitely bad idea to share resources with someone you don't trust.
A better idea might be to share dictionaries and open private (known to specific people) hashcat brain server to the internet.
It will reject password candidates based on attack type and it's position. Of course one who attempt to guess a password should not send password hashes to the brain server, but only attack positions (--brain-client-features=2) otherwise network bandwidth and brain server resources will become a bottleneck.
I don't know if there are some kind of vulnerabilities in brain server, and if it's secure to open it to the internet, but it may be a solution to distributing the cracking power.
I'm interested in contributing in such process, so PMs are welcome
by the way of making this happen we could learn to work with each other and build a trust.Re: Don't buy "wallet.dat" files with lost passwords; EXCHANGE THEM.
Great question!
I don't really have an answer.
To be fair we should think about trust only when we'll get to the point of actual transfer BTC out of cracked wallet.
For now, to start cracking i need only wallet hashes which doesn't reveal any private keys.
Let's crack first and then think about trust
I don't really have an answer.
To be fair we should think about trust only when we'll get to the point of actual transfer BTC out of cracked wallet.
For now, to start cracking i need only wallet hashes which doesn't reveal any private keys.
Let's crack first and then think about trust
Re: Don't buy "wallet.dat" files with lost passwords; EXCHANGE THEM.
Hey guys, what do you think about combining cracking power and making different hashcat attacks together in parallel?
Benchmark of my setup:
~/hashcat -m 11300 -b
Hashmode: 11300 - Bitcoin/Litecoin wallet.dat (Iterations: 200459)
Speed.#1.........: 10716 H/s (66.11ms) @ Accel:2 Loops:1024 Thr:1024 Vec:1
Speed.#2.........: 11148 H/s (63.59ms) @ Accel:2 Loops:1024 Thr:1024 Vec:1
Speed.#3.........: 11092 H/s (64.11ms) @ Accel:2 Loops:1024 Thr:1024 Vec:1
Speed.#4.........: 3863 H/s (80.94ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1
Speed.#5.........: 3827 H/s (81.85ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1
Speed.#6.........: 3830 H/s (81.87ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1
Speed.#7.........: 3790 H/s (82.58ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1
Speed.#*.........: 48265 H/s
All we need to share is a wallet hash in hashcat format.
Benchmark of my setup:
~/hashcat -m 11300 -b
Hashmode: 11300 - Bitcoin/Litecoin wallet.dat (Iterations: 200459)
Speed.#1.........: 10716 H/s (66.11ms) @ Accel:2 Loops:1024 Thr:1024 Vec:1
Speed.#2.........: 11148 H/s (63.59ms) @ Accel:2 Loops:1024 Thr:1024 Vec:1
Speed.#3.........: 11092 H/s (64.11ms) @ Accel:2 Loops:1024 Thr:1024 Vec:1
Speed.#4.........: 3863 H/s (80.94ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1
Speed.#5.........: 3827 H/s (81.85ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1
Speed.#6.........: 3830 H/s (81.87ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1
Speed.#7.........: 3790 H/s (82.58ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1
Speed.#*.........: 48265 H/s
All we need to share is a wallet hash in hashcat format.