Nexus Panel BoardPanels of numbers this site works out for itself
Reading

Copying rather than typing

A wrong character does not produce an error message, it produces a different address, and that difference is the whole argument.

Positions that must be right
56
characters, before .onion
Traded symbols per address
45
1
2
3
symbols from the easily traded set
Traded share of the set
26.8%
of the set is an easily traded symbol
Characters in the whole set
168
characters in the set

Nexus market addresses in this board

copy, do not retype
nexusb2l73qzjn4slhyfxa3jvpolw7fomiz5sgyyefnsdhikaqgborqd.onion
nexusma2iekjhhyenua3u4zlyfsj2ubwxr2nt6gdte5rvwukzze63fyd.onion
nexusabcdbnjw6or46y3hh6uicsl4xvu5cncfp27hkggznvtxhxlngad.onion

Printed as supplied, in no order, with nothing marked best or main. This board never opens an address, so nothing on this page says one of them is reachable for you now.

The core fact no redundancy anywhere

Most identifiers people handle have slack in them, and nexus market links have none at all. Postcodes have a structure, card numbers carry a check digit, ordinary words can be misspelled and still understood. A string of this kind has none of that available to a person. Every one of the 56 positions has to be right.

The format does contain error detection, but it is not something you can apply by looking, and it is not what saves you from a typo. What happens in practice is that a mistyped address either fails to resolve, with no explanation of why, or resolves to something that is not what you wanted. Neither outcome tells you which character you got wrong.

Why there is no partial credit

A string that is one character wrong is not a nearly correct address. It is a different address, in exactly the same way that a different phone number is not a nearly correct phone number. There is no closeness, no correction, no suggestion, and no did you mean.

This is the single most important thing to internalise about handling nexus market links, and it is why every page on this board carries a copy button next to each address rather than trusting anybody to read them.

Where typing goes wrong specifically

  • Traded symbols. A meaningful share of the set is made of symbols the eye swaps, and the bars and gauge above put a number on it.
  • Doubled symbols. Where a symbol repeats immediately, transcription drops one or adds one more often than anywhere else.
  • Line wraps. A string that wraps across two lines loses characters at the break more often than in the middle of a line.
  • Restarts. Losing your place and starting a block again is where duplication and omission both come from.

What copying does not solve

It moves the problem rather than removing it. A copied address is exactly as correct as the place you copied it from, so the whole question becomes where the address came from rather than whether you transcribed it correctly.

That is a much better question to have. Sources can be thought about, compared and kept. Transcription accuracy cannot be improved by thinking about it.

It also means the copy button on this page is not a guarantee of anything. It copies what this site was given. If what this site was given were wrong, the button would faithfully copy the wrong thing, which is why the board says on the addresses page that copying is the only thing it did.

Photographs, screenshots and paper

Sometimes there is nothing to copy from. An address on paper, in a photograph, or on a screen you cannot select from has to be transcribed, and no amount of preferring copying will change that.

In that case use the block method from the chunking panel, work in a fixed width font, and check the result once against the source afterwards rather than trusting the first pass. Then, if you can, get a copyable version and replace what you typed. A transcribed address is a temporary thing that should not become the one you keep.

Why the failure is silent and what that costs

The reason this matters more than ordinary typing accuracy is the absence of feedback. Type a web address wrongly on the ordinary internet and you usually get a page that tells you something is missing, a suggestion, or a search result. None of that exists here.

A mistyped address of this kind simply does not resolve, and the message you get is the same message you would get if the service were unavailable, if your connection were having trouble, or if the address were correct but nothing was listening. One symptom, four causes, no way to tell them apart from the screen.

That is why people spend so long troubleshooting the wrong thing. They assume the destination is down when the actual fault is a character they got wrong twenty seconds earlier, and there is nothing on the screen to point at the difference. The panel on error screens covers this ambiguity in detail.

Questions that come up on this panel

Does the copy button send anything anywhere?

No. It writes the text to your clipboard in your browser. This site has no server side handling of any kind and makes no external requests.

Is retyping ever safer than pasting?

Not for accuracy. There are situations where you would rather not have something in a clipboard, and that is a different concern with a different answer.

Reading this panel wrong

3 ways it happens
  1. Reading the traded gauge as specific to these addresses.It is a property of the alphabet and the length. Any address of this kind gives a similar figure.
  2. Assuming a copied address is a verified address.Copying preserves whatever it was given, including a mistake made further upstream.
  3. Thinking a wrong character produces an error.It produces a different address. That is the whole reason this panel exists.

What this panel is not: a guarantee. The button copies what this site holds, and the site holds what it was given, unchecked.

Nearby panels

Every panel on the board

68 pages
Strings
How long each address is The symbols an address can contain The opening all three share Where the three part company Digits, and where they fall What repeats inside an address How far apart the three are The character they all end on
Reading
Symbols the eye trades What a front and back check proves The part nobody reads Reading an address in blocks Copying rather than typing The stretches you cannot say Reading an address out loud What a check cannot reach
Route
What the browser is doing The first load of the session When a page loads slowly Why the path keeps changing What each step can see The screens that mean failure Where the address lives between visits Where the address came from
Session
The name you choose The login screen How long a session lasts What stays behind Two tabs, one account Ending a session on purpose Losing access Encrypted text in a session
Money
The deposit address Waiting for confirmations What escrow holds Where the cost sits Rounding and leftovers Taking a balance back out The waiting, laid out The steps you cannot take back
Orders
Before the order exists Placing the order The delivery details Between placing and dispatch What tracking does not say Finalising When it goes to dispute The feedback you leave
Corpus
How much is on this board How the panels are distributed How long a panel is The tiles, counted Which phrases the board uses What is deliberately left out How the panels connect The tiles that come back empty
Reference
All panelsHow the numbers are madeThe addressesWhat this board covers