Lost note guide
Step-by-step triage before calling recovery impossible.
Phase A: Lock ground truth
- Confirm exact network.
- Confirm exact pool denomination.
- Confirm approximate deposit timestamp range.
- Confirm source wallet/session context.
If these are wrong, every downstream recovery attempt can fail for the wrong reason.
Phase B: Build an artifact map
- Local backups and exports
- Archived browser profile or old machine data
- Encrypted note/account traces from original workflow
- Internal logs or records that preserve contextual clues
Phase C: Execute path-aware recovery
- Run one path at a time and keep outputs separated.
- Do not merge all notes before interpretation.
- Treat failed decryptions as diagnostic signal, not instant dead-end.
- If results are empty, re-check assumptions before widening scan scope.
Worksheet: what to write down before scanning
| Field | Why it matters |
|---|---|
| Network | Wrong network produces systematic empty results. |
| Denomination | Pool denomination determines which event set matters. |
| Deposit window | Narrows candidate commitments and reduces false assumptions. |
| Available artifacts | Determines whether recovery is realistic or only speculative. |
Phase D: Security red lines
- Never send recovery materials to public support chats.
- Never paste recovery materials into unverified web forms.
- Never trust unsolicited DM claiming "instant recovery".
- Verify handle and links character by character.
When to pause and re-check assumptions
- Every scan returns empty but chain/denomination were never independently verified.
- Recovered candidates appear on the wrong pool or wrong network.
- Different recovery paths produce conflicting interpretation.
- You are about to use recovery materials in an unfamiliar interface.
Good recovery is conservative. Do not keep widening scope blindly when the base facts are shaky.
Guided workflow option
If manual scripting is not practical, some users test:
Related: tornado-note-recovery