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.

G2 · A parcel that can arrive

A condition that must already be true

The name on the parcel fits the door it arrives at

The name has to be one that the address will accept without a question, which is a fact about the building and not about you.

Blocks: Nothing further on this map. The chain ends here, which means a failure at this point costs you only this.
Confirm by: Ask whether a parcel with that name would be handed over, refused or returned at the specific door in question.
Not this: Not a suggestion to use any particular name. It is about the match between two things.

Two names being compared by somebody holding a box

The condition is a match between two things decided separately. One is the name printed on the label, which you chose. The other is the set of names that address recognises, which you did not. Recognition here is institutional and dull: somebody at that door, or in that post room, or on that mailbox, associates the name with the place. When an item is handed over, a person makes that comparison quickly and without thinking. When it fails, the responses available are to query it, refuse it, send it back, or leave it anyway, and you do not get to pick.

The claim says this is a fact about the building rather than about you, and that phrasing is exact. Whether a name works at a door is decided by a mailbox label, an entry panel, a tenancy record, a list on a reception desk, and the habits of whoever handles post there. None of those are yours to edit. You can choose a name. You cannot choose whether it is recognised, and an unrecognised name is a name that generates a question.

The ways this is commonly half true are worth naming, because half true is where the damage lives.

Known but spelled otherwise
The building knows a person by one spelling and the label carries another. Machines do not care. A person might.
Known to the wrong part of the building
A neighbour recognises the name, the post room does not, and the post room is where items go.
Known for letters, not handovers
Anything that fits through a letterbox is compared to nothing. The first item needing a signature is the first real test.
Formerly known
The name belonged to somebody who was there and is not now, the case a building has a procedure for.

The two conditions underneath the label

The delivery address is written the way the post wants it supplies the rest of the block. A name is one line of an address, read last and by a person rather than a machine. If the lines beneath it are wrong, the item never arrives where anybody could compare the name to anything, so the question is never asked at that address. That is not the same as passing.

Somebody can take delivery at that address supplies the handover, and it changes the character of the test rather than merely enabling it. If a handover happens, the name is checked against local knowledge, loosely and fast. If none happens, the item is redirected and the check runs again at a counter, against a document. The same name can pass one and fail the other, so the order of these cards is not decorative: the one above decides which examination this one sits.

Nothing waits on this, which is not the same as it not mattering

This card is terminal. Nothing on the map depends on it, which you can confirm on Roots and endings, where the cards with nothing beneath them are listed alongside the roots with nothing above them. That is an unusual position and it deserves an honest account rather than a reassuring one.

Terminal here means the cost of failure is contained. It arrives immediately, lands in one place, and stops. A queried name produces a question at a door, or a refusal, or a return, or a slip. None of those reaches back up the map. Your session still works, your stored address is still stored, escrow is untouched by a name being read out badly, and you can come back tomorrow and still be you is unaffected. Compare a root condition, where one false statement quietly poisons every card hanging from it.

But containment describes propagation, not size. The cost that does land is real and not small in the moment. A refusal is a conversation with a person now paying attention to an item they had ignored. A return sends it back with a reason attached. A query at a communal door involves somebody saying a name out loud in a hallway. Those events are local, and they are the most person-facing thing in this stage. The map is quiet about them only because dependency is its subject, and no other condition waits on the outcome.

What a mismatch costsWhat it does not cost
A question asked at a door, in person, about a nameAnything upstream. Session, stored address and keys are untouched.
A refusal or a return, decided by the carrierThe value in escrow, held by a mechanism that never sees a label.
The chance of a clean handover at that doorThe rest of the map, which has no arrow leading out of this card.

The other terminal card worth reading beside this one is the browser doing this does nothing else, whose failure is contained in the opposite way: silently, and possibly for a long time. Between two contained failures, loud and immediate is the better one to have, because you find out.

How a mismatch actually unfolds

Skipping this produces nothing you can see. No field anywhere reports a name being queried. The order state says what it said before. The other side knows nothing, because nobody tells a sender that a name looked unfamiliar in a hallway. An item goes back, or sits somewhere, or is handed over anyway by somebody who could not be bothered, and you cannot tell those apart while they are happening.

If a slip appears it usually says something procedural and unhelpful, which is what a document written for the common case does. Because the paperwork points at process, the conclusion drawn is that the problem is in the process, so people go back to the address they typed, then the listing, then the other side. All three are innocent. The mismatch was between a printed line and a mailbox label, and neither is visible from a screen.

The whole cost of this card is paid at one door on one occasion. Nothing downstream absorbs the damage for you, and nothing downstream is damaged by it either.

Asking about the door instead of about yourself

The check is a question about a specific building, answered about that building rather than about carriers in general. Would a parcel bearing this name be handed over, refused or returned at this door. A pass is a mechanism you can state: the name is on the mailbox, the name is on the tenancy, the receptionist keeps a list and it is on the list. A fail is reasoning rather than knowledge: they probably would, it is unlikely anyone checks, most of the time nobody looks.

This check involves nobody but you and a building you already know. No address has to be opened and no message sent, which is why it belongs before anything is committed.

What choosing a name has to do with this

This is not advice to use any particular name, and none is suggested here. It is also not the address formatting card, which is upstream and concerns the shape of the lines rather than the word on the first one. And it is not about identity documents in general: the only identity question in this stage appears at a counter, and arriving at one is the failure described by the card above.

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.

You are here
G2 The name on the parcel fits the door it arrives at
One step forward
Nothing. This condition is terminal, so a failure here stays where it is.
Two steps forward
Nothing further. The chain ends within one step of here.

Connected to this one

Where you are in the map