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

The character they all end on

The last character of every address of this generation is the same, and it is the only position on the board where sameness is structural.

Final symbol across the set
d
3 of 3 end on this symbol
Positions where all three agree
6
positions where all three agree
Symbol variety along the third address
6
least varied eighth of this address
Positions where all three differ
44
positions where all three differ

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 observation and the reason behind it

Look at the end of each of the three addresses printed above. They finish on the same symbol, and the first tile confirms it across the set.

This one is not a coincidence and it is not a choice. The material encoded into an address ends with a version marker, and because every address of this generation carries the same version marker, the encoding of that final piece comes out the same every time. Any address of this kind, from any service anywhere, ends on that symbol.

What it lets you check quickly

It gives you a second free check to sit alongside the length check. If a string ends on anything else, it is not an address of this generation, and you have found that out by looking at one character.

Two free checks in a couple of seconds is genuinely worth having. Between them, length and final symbol will catch a truncated paste, a string that lost its tail at a line wrap, and anything that is not really an address at all.

What it absolutely does not do

It cannot distinguish anything. Every valid address passes, including every address that is not the one you want. A check that everything passes filters out only the malformed.

It is worth being blunt about this because the ending has the same seductive quality as the opening. Both look like a signature. Neither is. The opening is chosen and can be copied. The ending is fixed and is shared by the entire format. The only part of the string that identifies anything is the long stretch between them.

Guaranteed sameness versus accidental sameness

This panel is the reason the agreement count on the divergence panel comes out higher than the shared opening alone. The final position is guaranteed to agree, so it adds to the count for a structural reason rather than a random one.

That distinction is worth keeping. Some of the sameness in the set is built into the format, some was chosen by whoever generated the keys, and some is coincidence. Only the third kind is meaningless, but none of the three kinds is evidence about the address being the right one.

The whole free check in one place

  • Count the characters. Anything other than 56 is wrong.
  • Look at the final symbol. Anything else is wrong.
  • Look for characters outside the allowed alphabet. Any of them means wrong.
  • If all three pass, you have established that the string is shaped like an address. You have established nothing about which address it is.

That last line is the point of the whole strings section. Cheap checks catch damage. Only a position by position comparison against a source you already trust catches substitution, and no property of the string alone will ever do it for you.

Why the ending survives damage better than the middle

There is one more reason the final character is worth a glance, and it has nothing to do with identity. It is the part most likely to go missing.

Long strings get truncated. A messaging app cuts a link at a length limit, a chat window wraps and somebody copies only the first line, a note taking app trims trailing characters, a paste picks up everything except the last few symbols. In every one of those cases the front looks perfect and the tail is gone.

Checking the ending catches all of it at once. It is the single cheapest guard against the most common way an address arrives broken, and it costs one glance. That is a rare ratio and worth using, as long as you remember it guards against damage and not against being handed the wrong thing.

Questions that come up on this panel

Do older addresses end the same way?

No. An older and much shorter generation of address existed and did not carry this marker. None of the strings on this board is one of those.

If the ending is fixed, why print it at all?

Because it is part of the address and removing it would produce something that does not work. It is fixed, not optional.

Reading this panel wrong

3 ways it happens
  1. Reading a matching ending as a match.Every valid address of this generation matches. It rules out damage and nothing else.
  2. Thinking the ending is a checksum you can verify by eye.There is error detection in the format, but it is not something a person can compute by looking. The visible constant is the version marker.
  3. Treating the free checks as a complete check.They are a filter for malformed strings. Substitution passes all of them comfortably.

What this panel is not: a verification step. It confirms a string is shaped correctly, which every wrong address also manages.

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