I'm getting much more serious with my attempts to recover the password, spending hour after hour mapping all possible elements and all possible combinations. I found that writing down all the possible elements on paper is sparking my memory to remember every possible word/number/character that I would ever use in a password.
I found that I wasn't feeding the special characters correctly into BTCRecover, the $ has to be written in the token file as %S, and ^ needs to be %^. One of my primary theories from my memory is that the password ends with something like !@#$%^&* --- basically all the special characters in a row on the keyboard, and since I wasn't doing the code right, it gives me hope that I'll find it now that the program is reading special characters correctly.
Perhaps I already almost cracked the password, but the $ and the ^ in the password weren't handled by BTCrecover. I think this is what's happening.
I'm going to look into running with GPU to see if that increases speed. If my speed was faster by some orders of magnitude, it would be much more feasible. Right now it's testing approximately 3,000 password combos every minute. I'm pretty sure that number can be brought up to the tens of thousands per minute once I optimize efficiency.
BTCRecover is definitely your best bet here. If I were you, I would combine it with a password generating tool such as cracken (
https://github.com/shmuelamar/cracken) to generate a big list of possible passwords.
For example:
cracken --wordlist firstnames.txt --wordlist lastnames.lst --charset 'ABCDEFabcdefg' '?w1?w2?1?d?d?d'
this command would create a list of all possible combinations of:
Wordlist1 +
Wordlist2 +
One of these characters: ABCDEFabcdefg +
A digit from 0-9 +
A digit from 0-9 +
A digit from 0-9Thank you for the advice.
Please if anyone else has good advice or knows which experts I can talk to, let me know in this thread. This is a pivotal moment in my life, and my family will be much more successful and secure if I can just get this password.
All things considered, I know that this is all from God and that this whole scenario is all for the best. That being said, it's definitely the right time to fix this huge problem, and I believe that once I get some more expert advice or assistance, that this will be solved. The upsides are that the Bitcoins are in a wallet on my computer nice and safe, and that I had to type the password twice to encrypt the wallet, so it has to be a password that I personally typed. And I have a whole list of possible password elements, it's just a matter of getting the right sequence.
Worst case scenario, I typo'd twice in a row when I saved the password. But even then, I would just use the typo features on BTCRecover, once I can narrow down the possibilities enough, or if I can get the program to be fast enough.