What is BTCRecover? Creator, projects and recovery paths

What BTCRecover does

BTCRecover is an open-source tool for testing plausible wallet passwords and seed-phrase corrections. It is useful when you have enough of the original information to define a bounded search. It does not derive an arbitrary private key or a completely lost seed from a public Bitcoin address. The maintained project README describes its supported workflows.

Think of a recovery as two separate jobs: generate candidates, then check them against reliable evidence. A tokenlist can generate plausible passwords; a compatible wallet file provides a way to test them. A seed search needs the correct wallet scheme and verification data, such as a known receiving address. A plausible-looking result is not enough.

Who created BTCRecover?

BTCRecover originated with Christopher Gurnee, known on GitHub as gurnec. The original repository and its source copyright notice document that attribution. Its code credits Christopher Gurnee for 2014–2017; this is a copyright range, not a claim about an exact launch date.

Gurnec.com is an independent KeychainX educational resource. Christopher Gurnee is not presented as this website’s author, operator or endorser. Credit for creating software is different from endorsement of a website about that software.

Original project and maintained fork

Use the original gurnec repository to understand the project’s origins. These tutorials use the 3rdIteration fork and its documentation for current installation and recovery instructions. Do not mix legacy dependency instructions with commands intended for a different revision.

Record the exact revision before a meaningful search. A version label is helpful; a Git commit identifies the source more precisely. Our candidate laboratory publishes its tested commit and small synthetic inputs, so its claims can be checked. It does not certify every wallet or every operating system.

Choose the right starting point

• Wallet-file password: you have a supported encrypted backup and password hints.
• Seed correction: you have most of the phrase, with specific uncertainties.
• BIP39 passphrase: the mnemonic is known, but an additional passphrase is uncertain.
• Unsure which applies? Identify the original wallet and surviving evidence first.

A hardware device PIN is another input entirely. A password that encrypts an application backup does not automatically equal the mnemonic’s optional passphrase. Keep these hypotheses separate.

Practice without a wallet

Start with the ten downloadable exercises. They use invented River/Stone strings and display candidate lists without opening a wallet. Compare an anchored two-candidate search with an unanchored twelve-candidate search to see why assumptions about order matter. Only move to a wallet-specific search after your candidate rules behave as intended.