About this site

An independent reference page with a narrow job: describe conditions and the arrows between them, and refuse to state anything it cannot support.

What this site is

A prerequisite map for one marketplace, published as a set of thirty seven conditions with the dependency arrows drawn between them. It is independent. It has no connection to the operators of any market, no channel to them, and no way to confirm anything they might say. It sells nothing, hosts no accounts, sets no cookies, runs no analytics and carries no advertising.

The rules it is built to obey

State only what can be stated. Where the boundary is reached, say so rather than filling the gap with something plausible.
Never contact either published address. No availability figure, no status light, no date of last contact, no response time.
No invented facts. No statistics, no dates, no prices, no durations, no quotations, no named people, no testimonials.
Compute the graph rather than describing it. The downstream lists are derived from the upstream lists, so they cannot drift apart.
Publish the two addresses exactly as supplied, unlabelled and unranked, at the top of every page.
Make no request to any other host. No external fonts, scripts, images, trackers or embeds of any kind.

Why the arrows are computed

Each card declares what it depends on. Nothing declares what it blocks. The downstream lists on every card, the third column of the dependency map, the whole of the consequences index and both halves of roots and endings are all produced by reversing the same set of declarations. That means there is exactly one place where the graph is written down, and every view of it is generated from that one place. A hand written downstream list would be wrong within a week.

What it will not do

It will not tell you an address is working, because it has not looked. It will not tell you which address to use, because it has no basis for a preference. It will not tell you that anything makes you safe or anonymous, because no condition on this map does that and saying so would be worse than saying nothing. It will not give you a fee, a delivery window or a number of confirmations, because those change and a stale number does more harm than an absent one.

What it is for

One narrow thing: helping you find out what your problem is actually waiting on. Almost everything else written about this subject is arranged as a sequence of instructions, and a sequence cannot answer that question. If you take nothing else from the site, take the habit of asking whether a condition is true now, rather than whether you once performed the action associated with it.

How the pages are put together

Every page is built from the same small set of parts. A card carries a one line statement of the condition, four labelled fields, and a body that expands each of them. A stage hub explains what enters the stage, what leaves it, and where the stage is usually skipped. The three index pages, the map, roots and endings and the consequences index, contain almost no written text at all: they are views onto the same declarations, assembled at the moment you request them.

That uniformity is deliberate and it has a cost. Thirty seven pages with the same four labels do look alike at a glance, and a reader skimming quickly will feel they have seen the page before. The alternative is worse. Once each card is free to choose its own shape, the labels stop being comparable, and comparing them is the only thing the map is for.

What a good card looks like

The statement is a state, not an action. If it can be rewritten starting with a verb in the imperative, it is a task and it does not belong here.
The downstream section is the longest one, and it explains a mechanism rather than listing names.
The confirm step is something you can do today, with what you already have, without opening either address.
The final section names the stronger claim the card is not making.

Corrections

The content changes when the underlying files change, and the date at the foot of every page is taken from those files rather than from the clock. If something here is wrong in a way that matters, it is wrong in the data and not in a database, which makes it straightforward to fix. Start from how to read a card if you want to see what a correct card looks like before deciding whether one is wrong.