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

Where the address lives between visits

The string cannot be remembered, so it has to live somewhere, and where it lives is a real decision.

Longest run with no vowel
22
1
2
3
longest stretch with no vowel in it
Characters to store
56
characters, before .onion
Characters in the whole set
168
characters in the set
Traded share of the set
26.8%
of the set is an easily traded symbol

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.

Why storage is forced not optional

A 56 character string with long unpronounceable runs cannot be held in memory. That is measured on the vowel runs panel and the first tile here repeats the figure.

So there is no version of this where you simply remember the address. It goes somewhere, every time, and the only question is where. People who have not thought about it still made the decision, they just made it by default.

The options and what each costs

Where it livesWhat it costs
A browser bookmarkConvenient and stable. It is also on the machine, in a file, and survives longer than most people expect.
A note in a fileUnder your control and easy to check. Also easy to forget about, back up automatically, and sync somewhere you did not intend.
A message to yourselfConvenient and the worst of the common options, because it puts the address into a system built to keep and copy things.
PaperOutside every system, and requires transcription every single time, which is where errors come from.
Getting it again from a page each timeNo storage at all, and moves the entire question to whether the page you return to is the same page.

The trade nobody names

Every option above trades storage risk against transcription risk. Storing it well means you never retype it and never make a transcription error. Storing it nowhere means nothing persists but you retype constantly, and the traded symbol gauge on this panel says how error prone that is.

There is no option that avoids both. Recognising that is more useful than any particular recommendation, because it turns a vague unease into a choice with two named sides.

The habit that quietly fixes the checking problem

If you store the address once, carefully, from a source you thought about at the time, then every subsequent visit is a copy from your own store rather than a fresh arrival from somewhere. You stop needing to evaluate a new string each time, because you are not receiving one.

That is the strongest practical thing on this board, and it is a storage habit rather than a checking technique. All the reading panels are about the situation where a new string arrives. This one is about arranging not to be in that situation.

When your stored copy stops working

It will happen eventually, because addresses do change and this board publishes 3 of them precisely so there is somewhere to go when one does not answer.

The wrong response is to grab the first replacement you find and store that. That converts a considered store into an unconsidered one, and it is exactly the moment when a substituted string is easiest to accept, because you are frustrated and looking for anything that works.

The better response is to treat it as a fresh arrival: slow down, go back to whatever source you trusted originally, and store the new one with the same care you gave the first.

Storing all three as one decision

The set is published as 3 strings, and storing one of them is a strange half measure. If the reason to have a stored copy is that you cannot remember an address, that reason applies equally to the other two, and a store containing one address puts you back in the fresh arrival situation the moment it stops working.

Storing all of them costs almost nothing extra, 168 characters in total rather than a third of that, and it changes what happens on a bad day. Instead of going looking, you try the next one.

Keep them together, in the order they were published, without adding your own labels. Marking one as the good one is a note to your future self that will be wrong eventually, and a note that is confidently wrong is worse than no note, because you will believe it.

Questions that come up on this panel

Is a bookmark a bad idea?

It is a normal idea with normal costs. This board is not going to rank the options, only to name what each one trades away.

Should I store all three addresses?

The set is published as three, and having all of them means a failure on one is not a crisis. Storing them is the same decision repeated three times.

Reading this panel wrong

3 ways it happens
  1. Reading the vowel run bars as a storage recommendation.They explain why storage is forced. They say nothing about which method to use.
  2. Assuming a stored address is a permanent address.The board publishes several precisely because they are not permanent. A stored copy is a convenience, not a guarantee.
  3. Treating retyping as free.It is the alternative to storage, not the absence of a cost. The traded symbol share is the size of that cost.

What this panel is not: a recommendation. It names what each storage option trades and leaves the choice where it belongs.

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