The recovery material
Something is displayed once and will not be displayed again. Everything that matters about this phase happens in the sixty seconds after it appears, which is exactly when people are least prepared to make a decision.
Where minute 35 sits in the whole runCrown market addresses
crownm5jmtbhqnoxhexx7nyiygqgqofp3wnjyyfl74gziohqqy6oq5id.onioncrownrywlm7mnohkzntlir2tlhafq6tzphgqyag5cw5en7nprchfklad.onioncrownwpaimgizxylrvrh4u6acpvk4l757cfla7xs6zjki7tdjqbnv6qd.onionPublished exactly as supplied. Nothing on this site is monitored, tested or checked, so no address here is claimed to be working. What a copied address does and does not settle.
What actually happens in this phase
The account is created and the screen shows you something. A phrase of several words, or a string, or a code, with a line of text saying to keep it safe because it cannot be shown again. Sometimes it is offered as a download. Sometimes it is only on the screen in front of you.
What happens next is the phase. Either it goes somewhere durable in the next minute, or it does not, and the difference between those two outcomes will not be visible for weeks or months. That delay is the whole problem. Nothing punishes you for skipping this today.
The three pages here
Why this phase is separate from the account
On the timeline these sit ten minutes apart, and they could reasonably have been one phase. They are separate because they fail separately. Almost nobody fails to create an account. Very many people fail to keep the thing that lets them back into it.
Putting them together hides that, because the recovery step then reads as the last item of a form rather than as a phase with its own decision. It is not a field. It is the moment where the account stops depending on this browser session and starts depending on something in the physical world.
The stall is a decision about storage made in a hurry, with a screen open that you would rather close. Where does this go. A photograph is quick. A note application is quick. Both are quick because they are the least suitable options available, and both are what people choose under time pressure.
The second stall is deferral. Somebody leaves the tab open, intending to deal with it after funding, and either the session ends or the tab gets closed by accident. There is no second showing.
The third is not a stall but a slow leak. It gets written down correctly, in a place that seemed sensible, and six months later nobody remembers which place that was. Recording it and being able to find it are two separate jobs, and the second is covered on the testing page.
This is the phase where spending five times the expected duration is unambiguously correct, and it is also the phase most likely to be skipped entirely.
What you should have leaving this phase
- The recovery material recorded somewhere that survives the loss of this machine.
- The account name, the password and the second code in the same place, because any one of them missing produces the same locked door.
- A specific, sayable answer to the question of where that place is, which you will still be able to answer in three months.
If you cannot get all three, this is a good place to stop for today. Nothing is at stake yet. An account with no balance and no recovery material is a small loss. The same account with money in it is a different matter, and that is what the next phase creates.
One screen, shown once, with no second chance. The phase costs two minutes and it is the most commonly skipped step in the entire run.
Questions that come up here
I closed the page before writing it down. What now?
Assume it is gone. If the account still has an open session, look for the security area to see whether the material can be regenerated. If it cannot, and there is nothing of value in the account, starting a fresh account is cheaper than hoping.
Is a screenshot acceptable?
It is the most common answer and the weakest one. A screenshot lands in a folder that frequently syncs elsewhere, and it is readable by anything that gets access to that folder.