GUIDE 03 / PASSWORD RECOVERY
Build a small, testable tokenlist
Turn remembered password fragments into a controlled set of guesses. Preview every candidate before searching.
Create the example file
In the BTCRecover folder, save the following as a plain-text file named demo-tokens.txt. These are invented password fragments, safe to use for practice.
+ ^River
+ 2021 2022
+ !$The leading + makes a line required. Alternatives on the same line are mutually exclusive. The ^ anchor puts River at the beginning; $ puts the exclamation mark at the end.
Preview before searching
python btcrecover.py --listpass --tokenlist demo-tokens.txtThe generated candidate set is:
River2021!
River2022!This preview does not open or test a wallet. For real searches, remember that the preview itself exposes password hints in the terminal and any logs you save.
Change one rule at a time
Replace the invented pieces with your own remembered fragments only in your private recovery environment. Put spelling alternatives on one line when they could not both occur in the same password. Use required lines and anchors only when you have evidence for those restrictions.
If a part might have been absent, remove that line’s leading +. If the order is uncertain, remove the relevant anchor. Preview again after each change and check whether the guesses you expect are actually present.
Avoid an accidental huge search
Do not start with every wildcard and typo option. Each additional uncertainty can produce many more candidates. Keep separate tokenlists for different hypotheses so you can explain what each run tested.
When the preview looks correct, follow the wallet password guide to test against a supported wallet copy. For spaces, non-English characters, wildcards, or token count controls, use the detailed upstream references below.
CONTINUE WITH THE PRIMARY SOURCES
Sources & further reading
Commands and capabilities can change. Check the maintained documentation for your wallet and installed revision.