The queue and the wall
Two things commonly sit in front of the market itself. One asks you to wait and one asks you to prove you are a person. Both look like errors to somebody who has not seen them before.
Back to minute 15Crown 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 here
The address resolves and a page appears that is not a shop. Most often it is one of two kinds.
The first is a holding page. It tells you that you have been placed in a queue, gives some estimate of how long, and asks you not to reload. It may move you along by itself after a short interval. Its whole purpose is to control how many arrivals hit the thing behind it at once.
The second is a wall with a task on it. Type the characters, click the matching images, drag something into place. It exists because automated traffic is cheap and the wall makes it expensive. It is frequently harder than the ones on the ordinary web, because the tolerance for annoying a human is higher here than the tolerance for letting a machine through.
Why both exist
A service reached this way has a much smaller capacity than a normal website, and its front door is much easier to flood. A queue converts a crush into a line. A wall converts an automated flood into something that has to be paid for one attempt at a time.
Neither is there to inconvenience you specifically, and neither is a sign of anything being wrong. They are the visible parts of a service under load doing something sensible about it.
Getting through them without making it worse
- On a queue page, do not reload. Reloading commonly puts you back in the line, and the page usually says so in a sentence people skip.
- Leave the tab alone and do something else for the stated interval. Watching it does not speed it up and it does tempt you into refreshing.
- On a wall, slow down and read what is being asked. A surprising share of failures are people answering a slightly different question than the one on screen.
- If a wall fails twice, reload that one and take a fresh task rather than fighting the same one.
- If a queue does not clear in several times its stated wait, take another address from your set. That is what having a set is for.
- They keep a small service standing when the alternative is it falling over entirely.
- A wall makes bulk automated abuse cost something, which raises the floor for everyone behind it.
- A queue that states a wait gives you a number to hold against, which is better than an unexplained blank page.
- They are indistinguishable, to a new reader, from a broken address.
- They add minutes at exactly the point where somebody is least sure they are in the right place.
- A hard wall pushes people toward whatever alternative page appears easier, and easier is not a safety property.
The refresh loop is the main one. Somebody sees a wait figure, waits half of it, reloads, gets a fresh wait, and repeats. The perceived wait grows and the reader concludes the address is bad.
The second is treating an awkward puzzle as evidence of a fake. There is a reasonable instinct behind it, which is that a well run place should be pleasant. It does not apply here, and awkwardness carries no information about which address you are on.
The third is opening several addresses at once to race them. That multiplies the number of queues you are standing in without shortening any of them, and it makes it easy to lose track of which tab is which, which matters enormously for the check on the next page.
A stated wait is usually roughly honest. The reason a one minute queue turns into ten is almost always the reader reloading the page.
What to do while you wait
Use it. This is dead time with a screen in front of you, which is the best possible moment to do the check that belongs in this phase. Read the address in the bar against your own copy while the queue runs down.
It is also a good moment to decide whether you are still doing the whole run tonight. If the queue is long and your available hour is short, stopping here costs nothing at all, because nothing exists yet. That is the cheapest exit point on the entire timeline and it is covered in the stopping page.
A queue and a wall are a service protecting itself. Neither says anything about your address, and refreshing turns a short wait into a long one.