A prerequisite map for Zion Market. Read the arrows, not the list. Dependency map Onion addresses
zionmarket.biznothing works until

This is not a to-do list and not a walkthrough. It is a set of conditions and the arrows between them, so you can see what your problem is actually waiting on.

Zion Market onion addresses, printed here exactly as they were supplied

Two strings, reproduced character for character as they were handed to this site. Neither one is ranked above the other and neither carries a label, because a label would be a claim and this site is not in a position to make one. Nothing here opens them, so nothing here can tell you what happens when you do.

F1 · An order that can exist

A condition that must already be true

The listing is one you have actually read

The whole of the listing text has to have been read, because the conditions you will be held to are stated there and are not stated twice.

Confirm by: Write down, from memory, what the listing says about time, quantity and what happens if something goes wrong. Then check yourself against it.
Not this: Not a judgement of any listing. It is about whether you can quote the terms you agreed to.

Reading it means reading the part that looks like boilerplate

The condition is narrower than it sounds. Attached to any listing there is a block of text, and inside that block are the terms that will decide what happens later: what the other side treats as sent, what they treat as arrived, what has to be included when you write to them, what shape they want the delivery details in, whether anything is expected to be encrypted and to which key, and what they say they will do when something goes wrong. Those terms are stated once. They are not restated at the point of committing, they are not restated in a confirmation, and they are usually not restated in the message thread. Having read the first few lines and moved on is not a partial version of this condition. It is the condition being false.

The part most people skip is the part that carries the weight. Long boilerplate looks like formatting noise because it was written once and pasted into everything, and that is exactly why it is operative: it is the standing position of whoever wrote it. The descriptive sentences at the top are the part that varies and the part that commits to least.

There is a second reason, and it is the one that matters on this map. A later argument is settled partly on what was stated in the text. Whoever reads that argument was not present and can compare only two things: what the listing said and what you say happened. Never having read the first of those means bringing half a comparison to a process that needs both halves.

The single condition underneath this one

This card rests on exactly one thing, You can log in a second time. That looks like a formality until you notice what it supplies. Listing text is not yours. It lives behind the session, it can be edited, and it can stop being displayed. Being able to become the same account again is what turns the text into something you can return to and quote. Read it once with no way back and your only record of the terms is memory, which is the same position as not having read it.

Nothing else on the map supports this card. It needs nothing from A wallet exists and the keys are yours or from anything else in that stage, which makes it one of the cheapest conditions on the Dependency map to satisfy and one of the most expensive to leave false.

Four things that cannot be built on an unread listing

Four separate conditions take their input from here, and in each case the failure is not that they become harder. They become undefined.

The other side answered before you spent anything needs a question whose answer is already in the listing, because the value of the exercise is the comparison between the reply and the text. Without the text you can still send a message and get a reply, but you have collected only the fact that a reply exists. The half that told you whether it agrees with the stated terms is gone, and that half was the point.

The delivery address is written the way the post wants it usually has its shape specified in the listing: how many lines are wanted, whether a name is expected, what is to be omitted. Supply it in a shape nobody asked for and it gets rekeyed by hand at the other end, or not at all.

What you send is encrypted to a key that exists depends on the listing for three facts: whether encryption is expected, which key is the right one, and where that key is published. A key found somewhere other than where the listing points may be perfectly genuine and still belong to the wrong holder.

You can describe the problem in the market's own terms is the one that hurts. A description of a problem is a difference between two statements. You have the second statement, which is what happened. Without the first, the sentence has no subject and what you write turns into a mood rather than a claim.

Cannot holdThe reason it cannot
The answer before you spendNo question can be checked against a text you did not read
The address the post can readThe required shape of the lines was stated only in the listing
Encrypted to a key that existsWhich key, and whether one is wanted, is listing information
A problem you can describeA difference needs two statements and you kept one

The damage does not stop at those four. The answer card feeds The total is covered at the moment you press the button, which feeds the whole parcel stage, so an unread listing weakens conditions three and four steps away.

How the skip actually plays out

Nothing goes wrong at the time, and that is the whole shape of it. You skim, you commit, the order exists. There is no warning, because no system anywhere is measuring whether you read a paragraph. The cost is deferred and paid in one place: the moment you first have to say what was supposed to happen.

At that moment you go back to the listing and one of three things is true. The text is still there and says something you did not expect, in which case the argument is over before it starts. The text has been edited and you cannot tell whether it changed or whether you misremembered. Or it is no longer displayed at all. In every version the confusion lands in the wrong place: it feels like the other side moved the terms, when you never fixed them in the first place. See If this is false for the general shape of that displacement.

Restating the terms without looking

The check is a recall test and it costs nothing. Close the page, write down in your own words what the listing says about timing, about quantity, about what is expected from you and about what happens when something goes wrong, then open it again and compare.

A pass looks boring. Your four notes match the text, including the conditional clauses. A fail is easy to recognise: you reproduce the descriptive top of the listing accurately and go blank on every sentence containing the word if. That is the normal failure, because conditional sentences are the ones that do not become interesting until later.

Not a review of anything you read

It is not a judgement of any listing, and it says nothing about whether the terms are reasonable. It is only about whether you can quote them. It is also not the same as The other side answered before you spent anything, which tests the person; this one tests the text.

The chain around this condition

Read downwards. Everything above this card has to hold before it can, and everything below it is waiting on it. Two levels are shown in each direction; the full graph is on the dependency map.

Connected to this one

Where you are in the map