tokens.txt or tokenlist tokens.txt

[maxwan]

hi ,  can some of you people with more knowledge than me  help me with a template for a  btcrecover or a tokens-auto.txt file.
i have it running but something is not quite right it takes only a few minutes to process when i start btcrecover , then finishes with a line saying exhausted .

hope I made sense .
hope you can help.
thanks Paul

[1715290043]

1715290043

[1715290043]

1715290043

[1715290043]

1715290043

[1715290043]

1715290043

[1715290043]

1715290043

[1715290043]

1715290043

[uartasic]

hi

i am about to do a ful tutorial on basic aspects of btcrecover.

i also have a virtual box image of the pc configured ready to go.

i have done this for a work colleague and the kids in the family who want to use it.

i refer back to gurnec repo on gihub alot. full credit to him for creating a good tutorial.

i havent had to use complicated variables as my passwords were more of knowing the length and finding the gaps of the missing passwords at the middle start or end.

most of my variables are %p so it searches through all ascii text.

the reason why its says exhausted is because it cannot create anymore variants of the characters you have entered into your tokens file.

also means it didnt find the password within.

again, i only use the tokens.txt config i didnt use the auto config, nor have i needed to.

my tokens.txt looks like this, where the password ends up being btcbtc2017

%p%pcbtc%p017

so the gaps unknown are ascii guesses

hope this makes sense/ helps.

feel free to PM me if you want rather than cluttering the thread with to and from responses, but there might also be users out there in the same situation so the banter might also be helpful.

[HCP]

hi ,  can some of you people with more knowledge than me  help me with a template for a  btcrecover or a tokens-auto.txt file.

The only person that can really help create the tokens file is YOU. The whole point of this file is that it should contain fragments that were likely to have been used in the password. So, if you always used a password like:

ThisIsMySecretPassword12345

But you're not sure if it had 12345, or 54321, or 67890 etc, but you're sure it had 5 numbers on the end... you would create a token file like:
ThisIsMySecretPassword
%5d

This would try ALL combinations of "ThisIsMySecretPassword" + 5 digit numbers from 00000 to 99999

Honestly, the best resource for this is the btcrecover tutorial here: https://github.com/gurnec/btcrecover/blob/master/TUTORIAL.md#the-token-file

It explains all the options with examples of how you put together a tokens file. If you're unsure of what your password was to begin with... and you're just attempting to bruteforce your password... you can probably just use a tokens file that consists of just %p... with however long you think your password was... ie. for a password of up to 10 characters:

%1,10p

Note that this will generate literally MILLIONS of passwords... and is the reason why you really need to have a relatively good idea of what your password was likely to be, so you can narrow it down using tokens.

[maxwan]

Thanks for you replies HCP and uartasic ,
The token text file had the word tes ( short for test ) , which is the wallet password so I could test the  btcrecover programme but it didn't find it , what I would like is a text file from which I can input my guess at my wallet password of which I know but not in the right order . Could either of you email me one where I can input my guess .

Thanks Paul

[HCP]

Try creating a file that just has:

Code:

%3in

And see if that works with your wallet file that has the password "tes"... it should test ALL passwords with 3 characters... including lowercase, UPPERCASE, numbers, but excluding symbols. It should generate a few thousand guesses... but should find "tes"... otherwise, you're not running btcrecover correctly. What command are you using to run btcrecover?

[Welsh]

Try passwordlist instead of tokens to make sure that the program is running correctly, tokens should work, but you may have made a mistake when creating it. If that doesn't work then it's likely you've made a mistake with the password, or the program hasn't been installed correctly. Have you ran "run-all-tests.py" and got the expected results back?

[maxwan]

Thanks HCP and welsh
I found a template and edited the passphrase and it ran with the result .
one more question is I tried it a second time and the second attempt wouldn't run because it found the password on its first attempt. Is that normal

[HCP]

You mean it says something like "password already found, password = foobar" or something like that? Or you mean the script just won't run?

I vaguely remember reading in the docs that btcrecover has the ability to "remember" it's current progress for a particular search... so if you're searching say 3,000,000,000 passphrases... you can stop it, and it will start again from where you stopped it.

So, it's possible that it has recorded the "progress" for that particular wallet file, so when you try to run it again, it just gives you the password.

[uartasic]

if you used the --autosave savefile in the cli then its likely saved it already.

Thanks HCP and welsh
I found a template and edited the passphrase and it ran with the result .
one more question is I tried it a second time and the second attempt wouldn't run because it found the password on its first attempt. Is that normal

[maxwan]

Hi , I deleted the save file ( moved to desk top ) . And it starts fine ,
Thanks for your time all .

[RichardBTC]

HI All,

can anyone help with refining my token list?

I have a couple of words in my token list but i know the the password is more then X amount of words, so i can i tell btcrecover to only try combinations with 3 or more words (or combinations) in the passwords

[o_e_l_e_o]

I have a couple of words in my token list but i know the the password is more then X amount of words, so i can i tell btcrecover to only try combinations with 3 or more words (or combinations) in the passwords

You can simply add the commands --min-tokens and/or --max-tokens to your command line entry. So in your case, add the following to the end of your command:

Code:

--min-tokens 3

You can read more here: https://btcrecover.readthedocs.io/en/latest/tokenlist_file/#token-counts

[RichardBTC]

I have a couple of words in my token list but i know the the password is more then X amount of words, so i can i tell btcrecover to only try combinations with 3 or more words (or combinations) in the passwords

You can simply add the commands --min-tokens and/or --max-tokens to your command line entry. So in your case, add the following to the end of your command:

Code:

--min-tokens 3

You can read more here: https://btcrecover.readthedocs.io/en/latest/tokenlist_file/#token-counts

thanks i did this and tried it on a combination of 26million passwords and it only shaved off about 50k passwords?

[o_e_l_e_o]

thanks i did this and tried it on a combination of 26million passwords and it only shaved off about 50k passwords?

Yeah, that's probably about right.

Let's say you have five tokens in your file. If you allow any combination of tokens from one token on its own to all five tokens in every combination possible, then there are (5*4*3*2*1)+(5*4*3*2)+(5*4*3)+(5*4)+(5) = 325 possible combinations.

If you want to cut out all passwords using only one or two tokens, then you are only cutting out (5*4)+(5) = 25 combinations.

For each additional token, the possibilities increase exponentially. Removing the lower end of the range will only ever have a very minor effect on the total possibilities.