Start with one question
“Why is this wallet empty?” is too broad for a single experiment. A better first question might be: “Did I restore the same account type that generated this receiving address?” Write the question before changing software settings. Keep your notes private; a useful notebook can reveal sensitive context even when it contains no private key.
Use four columns
| Record | Example without secrets |
|---|---|
| Observation | The file came from a 2015 laptop backup. |
| Hypothesis | The wrong application is interpreting the export. |
| Experiment | Compare the format with the original project documentation. |
| Conclusion | The format is still uncertain; no restore has been attempted. |
Capture enough to reproduce a result
- Assign a private backup identifier and preserve the original.
- Record the tool release, operating system and command template.
- Record input categories and candidate rules separately from the actual secrets.
- Write down the result, elapsed time and any errors.
- Mark a test as interrupted, completed or inconclusive. Those states are different.
Avoid the most expensive misunderstanding
“No match” is an observation about one configured test. “The wallet is unrecoverable” is a much broader claim. Before moving between them, check whether the test addressed the intended format, candidate set and verification target. A notebook makes those assumptions visible and reduces repeated work.
When you need another person
For an initial KeychainX enquiry, share the wallet application, approximate dates, backup type and the problem. Do not send the notebook’s secret pages or wallet attachments unrequested. A support conversation should first establish what evidence is needed and how it will be handled.