Here is the information for the address
EDIT: Was told that this information is necessary, so here you go
"mkey": {
"encrypted_key": "3ce2900d6c2df58a1cfa9ea1755a1599e0b60001fcd29d730c298de7538e3a0709e4fdb738d8ac6 1b5b03c582d724214",
"nDerivationIterations": 80062,
"nDerivationMethod": 0,
"nID": 1,
"otherParams": "",
"salt": "d07e66c2606ae4fc"
},
Is there someone who can help me try and recover with this information above? I can see it in bitcoin2john.py, but I think I don't need the wallet.dat, is that correct? He can run the python script and post the hash, which is safer. Then all that anyone can do is recover the password for wallet.dat, but not the private key(s), so the funds cannot be stolen. (Is that correct?) Otherwise he could share wallet.dat with someone if he wants to, with some detailed information about the person recovering for some assurance that he could hit back if the funds are stolen.
There is also another address within the wallet that has 3 btc that i am hoping to recover. I will give the person who produces the successful password 0.5 in addition to the address above, but I guess youll have to trust me on following through.
Crack this wallet and feel free to take the money, but please message me the password! Or post it here
Just a bounty you feel is worth the recovery, if successful, otherwise cost of recovery is sufficient.
I forgot the password i used back in 2013 and im dying to figure it out so i can take funds from the other addresses in the wallet. I really don't remember anything about the password but it wasnt very long
Also, does anyone have any time approximations for bruteforcing according to password length? Such as
5 char = xx min
About 3.5 hours for me, assuming charset a-z, A-Z, 0-9 (62 possible characters in pwd)
6 char = xx min
About 9 days, with above charset. Or just a-z or A-Z (either) and digits: 8 hours.
7 char = xx min
With just lowers or uppers, and digits: 9 days.
With charset a-z A-Z 0-9 for me, about 226 days. That assumes 75,500 h/sec.
With charset a-z A-Z 0-9 length 8 chars, again with 75,500 cracks at wallet.dat per second in a rather blind fashion, the entire kespace: 95 years or so.
This assumes cracking the latest Bitcoin Core wallet.dat.
I could give it a good go with the info I need and estimate cost/time, or I might just get lucky with the possible passwords you posted and some good rule sets with my own scripts derived from others that generate candidates from known (or guessed, and not quite correct) information.
Let me know if you'd like me to have a crack at it... I can double my compute power at least, so I might have a reasonable chance.
There are some other possibilities for address 12KGAcU47BhCSQJCN9r2dHAvhDALMVsJkk. I might give those the old college try. It's a bit of a stab in the dark, but worth a shot for a little while to see what happens. I'll post back if I get any interesting results. Some of them I will have to ask for help with, so I could be a few days.
Good luck!
