How to read your diagnosis

You answered six questions and got back a map, a count of risks, and exactly one action. This explains what each of those three things means, so you can argue with them instead of believing them.

What a “structural risk” is

It doesn't mean something is misconfigured. It means the shape of your setup has a point where, if one piece fails, there is no other path. How good that piece is doesn't enter into it.

A seed phrase written on paper, in a fireproof box, in one house, is an excellent backup with a structural risk: there is one location. The quality of the paper doesn't change that count. That's why the diagnosis talks about dependencies and not about products.

Why it sometimes says there's a tie

When two problems carry the same severity and the same blast radius, the engine says so and lets you pick by whichever is easier. It could invent an order — it would look tidier — but that would be false precision.

Being told “these two are equal, start with the one you can actually do today” is real information: it means either one moves the needle the same amount, and the one you'll finish beats the one that sounds more important.

Why “nothing has been rehearsed yet”

It's the most uncomfortable line on the screen and the most important one. Your answers describe what you believe you have. That's enough to find dependencies, and it is not enough for anything else.

Here's the concrete case: you can have the phrase written down, complete and legible, and still be unable to recover the wallet — because it's missing which wallet created it, or because there's a passphrase nobody wrote down, or because the address type is a different one. None of that shows up by looking at the paper. It shows up by trying.

That's why the map starts with everything unverified. It isn't distrust: verification is an act, not a declaration.

The five-minute action

You get one. Not a prioritised list of twenty, because nobody does a list of twenty.

And it's almost always writing down something that isn't a secret: which wallet created the seed, what year, whether a passphrase exists and where the other half lives. Those lines cannot spend a satoshi, and they are what most people who lose access turn out to have been missing.

And then, the proof

Once the plan is in order, the other half remains: checking that what you wrote down actually rebuilds your wallet. That's the ceremony, and it's arithmetic done in your browser with your public key — never the private one, never the phrase.

Run the ceremony →