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

Reading an address in blocks

Cutting a long string into fixed blocks manufactures the attention peaks you naturally have only at the ends.

Digits per block, address one
3
busiest eighth for digits
Digits per block, address three
4
busiest eighth for digits
Characters in one address
56
characters, before .onion
Symbol variety per block
7
least varied eighth of this address

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 idea in one sentence

Break the address into equal blocks, treat each block as a separate small comparison, and do the blocks in a fixed order. That is all chunking is, and it is the only manual technique on this board that reliably improves a by-eye comparison.

It works because attention has a shape. It peaks at the start and end of whatever you consider to be the current task. Making eight small tasks out of one large one gives you sixteen attention peaks instead of two.

The block metrics and their point

Every block metric on this board cuts an address into seven equal pieces and counts something inside each. The first two tiles do that for digits, on two different addresses.

Look at them side by side. They are different lines with nothing in common, which is the intended lesson: the blocks are a tool for the reader, not a feature of the string. There is no natural place to divide an address, no meaningful boundary, and no block that is more important than another.

The last tile counts distinct symbols per block, and it is almost flat. That flatness is the reassuring part. It means no block is unusually repetitive or unusually varied, so a fixed block size is as good as any clever one.

Choosing a block size

  • Small enough to hold in your head at once. Four to eight characters is the usual range for most people.
  • Consistent between the two things you are comparing. Different block boundaries on the two copies defeats the whole method.
  • Counted, not eyeballed. If you find blocks by looking for landmarks, you are back to landmark reading and the blocks will not line up.
  • The same every time you do this. A routine that changes is a routine you cannot tell you have done correctly.

What chunking does not fix

It does not make a manual comparison equivalent to copying. It reduces the error rate of a bad procedure, which still leaves you with a procedure that has an error rate.

It does not help at all if one of the two copies is wrong at the source. Chunking is a comparison aid, so it inherits every weakness of the thing you are comparing against.

And it does not help with the two regions that are guaranteed to match. Blocks covering the shared opening will always agree, so the first block or so is doing no work regardless of how carefully you read it.

The realistic recommendation

Copy the address. Use the button. That is the whole recommendation and it is what this board says on the copying panel as well.

Chunking is what you do when copying is unavailable: when the address is on a screen you cannot select from, on paper, or in a photograph. Those situations are real and worth having a technique for, and this is the technique. It is a fallback, and treating a fallback as the standard method is how people end up doing careful work in the wrong place.

Doing it on paper the version that works

The physical version is simple and worth writing down. Put the two copies one above the other in a fixed width font, cover everything except the current block with two pieces of card, compare, then move both pieces of card together to the next block.

Covering matters more than it sounds. An uncovered string invites the eye to wander ahead, and wandering ahead is how you end up comparing a block against the wrong block. Physically hiding the rest removes the temptation instead of resisting it.

Mark off blocks as you complete them. A comparison you abandoned halfway and a comparison you finished look identical afterwards, and the only way to tell them apart is a record you made at the time.

Questions that come up on this panel

Why seven blocks in the tiles?

Seven divides the address length evenly, which keeps every block the same size. Nothing about the number seven matters beyond that.

Does reading blocks backwards help?

It breaks the habit of skimming forward, which helps some people. It also makes losing your place easier, so it is worth trying rather than adopting.

Reading this panel wrong

3 ways it happens
  1. Reading the two sparklines as comparable.They are different addresses. Their only relationship is that neither has a pattern, which is the point of showing both.
  2. Treating block boundaries as part of the address.They are imposed by this site for display. The address has no internal divisions of any kind.
  3. Thinking a careful chunked read beats a copy and paste.It does not, and the panel says so twice on purpose.

What this panel is not: a validated method. It is a description of a technique that reduces error in a procedure you should mostly avoid.

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