Attribution and scope
The GitHub project burjorjee/pyethrecover is derived from ethereum/pyethsaletool. Its README describes password candidates supplied directly, from a line-delimited file or from a specification. This website is an independent KeychainX resource; owning this domain does not make KeychainX the author or maintainer of that software.
Inspect the exact revision
In the source inspected on 20 September 2026, the wallet path is read as JSON and candidate verification uses encseed and ethaddr. That is a presale-specific workflow. It is not evidence that the program accepts every Ethereum V3 or validator keystore. Save the revision identifier of any copy you assess; a fork may behave differently.
Three details worth noticing
- The inspected attempt function skips candidates shorter than ten characters. Do not assume every proposed candidate is tested.
- The password-specification path calls Python eval. Treat such a file as executable input and never use a specification received from an untrusted source.
- The program prints candidate values and can print recovered secret material. Terminal history, recordings and shared logs deserve attention.
Compatibility is a separate question
A historical README’s Python compatibility statement is not a current installation test. Old dependencies and forks can differ. This publication does not claim that the legacy recovery program was executed or audited end to end. Review the environment and practice with disposable fixtures before considering an authorized real-wallet workflow.
Make an informed next choice
Start with backup identification. Then compare the exact tool’s input requirements with your evidence. The BTCRecover documentation is another project reference, not an interchangeable command recipe. If you need help, describe the backup type and software history to KeychainX first; keep passwords, seeds and unrequested files out of the initial message.