Yes, you only specify %% when you a creating a "single" char token... when you're specifying chars in [...] format... you just use a single %. I've just tested it... and created the following token file:

And then tested using:

It output:

In addition to that... there is a weird character just before your final "]" which is actually what is causing your error... you need to delete that and the extra %... so your token file should looks something like this:


Yes... a 9 character password, with that many special chars will take a LONG time to test... With 104 possible characters, it's something ridiculous like 1,423,311,812,421,484,500 possible combinations just for the 9 character passwords... then you have the 8 char passwords, 7 chars, 6 chars etc etc. All up, (with my bad maths) it is something like 1,437,130,373,707,129,900 combinations

If you can check 1,000,000,000 passwords/second... You would need: ~1437130373.73 seconds to check them all...
= ~23952172.9 minutes
= ~399202.9 hours
= ~16633.5 days
= ~45.6 years

You might be better off trying to exclude some characters which you're fairly sure you would not have used to reduce the total search space to a more reasonable amount.

You can also try and do it using Amazon Web Services, but the costs can get prohibitive... so unless you have a significant amount of money in this wallet, that might not be the most cost effective way of doing it. Again, talking to wallet recovery experts who already have the equipment and code setup and ready to go might be a better option.

Ok... so I think you need to read the "Unicode Support" part of the btcrecover docs (if you haven't already): https://github.com/gurnec/btcrecover/blob/master/TUTORIAL.md#unicode-support

You will need the --utf8 commandline argument... and to make sure that your token file is saved in UTF-8 format.

It looks like you still have all the necessary files... so that's a good start. Now, it's really just a matter of finding the correct password.

Does the MultiBit install still work? As in, you can actually load up MultiBit and see the wallets etc? If so, that would suggest the files are hopefully not corrupt. Then, it's just a matter of getting the password.


Getting Python and btcrecover working can be a bit daunting if you're not experienced with commandline applications... but it's not impossible. You just need to make sure you use Python 2.7.x and follow the instructions as outlined on the btcrecover github: https://github.com/gurnec/btcrecover/blob/master/docs/INSTALL.md

If you're unable to get btcrecover working, then you're basically left with the option of engaging a 3rd party to try and recover things for you... my recommendation would be: https://walletrecoveryservices.com/


Also, in case it wasn't obvious, there are a lot of scammers here on Bitcointalk... so be VERY cautious if anyone offers to help via PM or Telegram etc and asks you to send your wallet files/passwords etc!