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.

E1 · Value you can move

A condition that must already be true

A wallet exists and the keys are yours

The place the value sits has to be one where the keys are held by you, because everything downstream assumes you can move it without asking.

Confirm by: Ask whether you could move the whole balance right now without any third party agreeing. If the answer needs their cooperation, this is false.
Not this: Not a comparison of wallets. It is the single question of who can stop a transaction.

Who is able to stop the transaction

A wallet is a set of keys, and the keys are the only thing that decides what moves. So this card asks one narrow question about wherever your value currently sits. If you decided this minute to move the whole of it somewhere else, is there a party whose agreement you would need. If there is, the value is not in your hands. What you hold is a claim on somebody who holds it.

A claim behaves exactly like the thing it is a claim on, for as long as it is honoured, which is what makes this condition easy to get wrong. A balance held by a third party shows the same digits, rises when value arrives and falls when value leaves. Nothing on the screen separates a holding from a promise to pay. The difference is structural, and it becomes observable on the single day the promise is not kept, when the language is always mild. Something is under review, or temporarily unavailable, or subject to a limit that was not there before. None of it reads as a refusal, and frequently none of it is meant as one.

It does not have to be. The map does not require the third party to be hostile, only that it is a step, because everything downstream assumes that moving value is a decision you make alone. Stated plainly: key material exists, you have it, and you can assemble and broadcast a transfer using nothing but what you already possess.

What the ground floor hands up to this card

the machine is one you actually control supplies the surface the keys live on. Whoever can install software decides what that software does at the moment you press send. Key material on a machine administered by somebody else can be read, copied or quietly substituted, and a wallet can be perfectly self-custodial in design while being nothing of the sort in practice. The design of the wallet is not the question here. The administration of the machine is.

losing the device does not lose the account supplies the single copy problem. Keys living inside one installation on one disk and nowhere else are one accident from being no keys at all, and an accident here means a drop, a seizure or a reformat. Taking custody yourself does not soften that. It sharpens it, because removing the third party also removes the only party who could have restored anything for you.

Both parents sit at ground level on roots and endings. Nothing supports them in turn, which is why nothing on this stage can be repaired from inside it.

What a promise to pay cannot support

Two cards hang directly off this one, and through them the rest of the value stage and the order that follows.

Cannot holdThe reason it cannot
the balance has confirmed and can be spentSettlement is a fact about a transfer to keys you hold. If the keys are somebody else's, the thing that settled is their holding, and what you read is their bookkeeping about it. Spendable then means willing, which is not a property you can check.
you hold the coin this order is priced inClosing a denomination gap means moving value, and moving value is the capability this card is about. A custodian may offer the conversion, but at their pace and under their conditions.

Take the settlement card first. It asks whether value has settled far enough to be spent right now, and that question presupposes that spending is something you do. When a third party holds the keys, the transfer that settled ended at their address. What you see afterwards is an entry in their records, and whatever policy stands before releasing it is theirs to change. The downstream card does not become false. It becomes unanswerable, which is worse, because a false condition can be noticed and an unanswerable one cannot.

The denomination card fails more plainly. Matching what you hold to what the order is priced in is a movement, and every movement inherits this condition. A holding you cannot move is one you cannot convert, so the gap stays open at exactly the moment a window is running.

The damage does not stop there. there is something left over for the fee and the deposit address came from the session you are in sit under those two, and both feed the total is covered at the moment you press the button, which needs several conditions true in the same instant. A holding that requires anybody else to agree cannot be true in an instant of your choosing. if this is false traces the width of that spread.

This is one of the few cards whose failure is silent for its whole useful life and then total. Nothing downstream reports it; every downstream failure reports as something else.

How the day it matters actually goes

Nothing goes wrong for a long time. The balance appears where it should and rises when value arrives. If you have moved value out before, that worked too, which does the real damage, because a movement that succeeded once gets taken as proof of a capability rather than as one instance of permission being granted.

Then there is a day with a deadline on it. Instead of the confirmation you have seen before there is a short line of text about a check, a hold or a review. Nobody has said no. The value is simply not moving. The confusion then lands in the wrong place: a deposit shows nothing arriving, so people start re-checking strings and generating new destinations. None of that touches the fault, which was decided when the value was placed somewhere that answers to someone else.

The whole balance question, asked honestly

Settle this without moving anything and without opening anything. Ask what sending the entire balance out right now would involve, then look for the steps in that story that are not network steps. A pass: you open the wallet, you produce the key material, you build the transfer, and only the network can delay it. A fail: an account, an approval, a cooling period, a support channel, a verification step, a cap somebody else set, or a note that large movements are handled by hand.

There is a blunter signal too. If you were never shown key material of any kind, and there is nothing you could take elsewhere to reconstruct the holding, the keys are not yours.

Custody is not the same as security

This card compares no wallets and recommends none. It does not claim that holding your own keys is safer in general, because the errors it exposes you to are simply different errors. It says one narrow thing: it names who can refuse. how to read a card explains why the map only asks that kind of question.

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