Nexus Loss Table Ranked by expected cost, not by how frightening it sounds
Table › How money goes

Nexus addresses

Three published addresses for the same market. Copy rather than retype.

nexusb2l73qzjn4slhyfxa3jvpolw7fomiz5sgyyefnsdhikaqgborqd.onion
nexusma2iqgauqqvjcgds4ckv5xbf272tkfagq4epojjhsgleqpwxiqd.onion
nexusabcdrwy7632jfmkfu3f6u7usyw2xn2mcfiljunz6zsj4p5vioqd.onion

This list is published, not monitored. An address that opens is not an address that is genuine.

An old address that answers again

The one entry in this table that specifically catches people who have been doing this for years.

How often
Periodic
Typical size
The account and its balance
Recoverable
Sometimes
Cost to prevent
Seconds, monthly
The ruleAn address dropped from the published set that later serves a login page has not recovered. Nothing retired returns under the same string. Close the tab.

Why it reaches the wrong people

Every other entry here is filtered by experience. This one inverts that. The reader most likely to hold a long dead address is the one who has been doing this longest, has the strongest sense of knowing what they are doing, and is least likely to look closely at a string they recognise.

Familiarity does all the work, and familiarity has never been evidence of anything.

What a retired address is worth to somebody else

Consider what an address that served for two years has that a fresh imitation does not. It sits in old forum posts, archived pages, unmaintained lists, bookmarks and screenshots. Whoever answers there inherits all of that without doing anything, and the traffic arriving is disproportionately people who trust the string because they remember it.

Being precise about what is possible

Possible?
Taking over the exact addressNo, absent a key compromise. Serving traffic there requires the private key it was derived from.
Standing up a close resemblanceYes, and cheaply. This is what you will actually encounter.

Matching four or five opening characters takes minutes on an ordinary machine. Seven or eight takes days and is still practical. Matching all fifty six is impossible. So the forgery always has a familiar opening and a middle that differs, which is why the middle is where you look.

The habit that removes it

  1. Keep addresses in a file you control, with the date beside each one.
  2. Compare against the published set every few weeks. Under a minute.
  3. Delete rather than archive when something drops off. An address kept just in case is one you might paste months later.
  4. Check the middle of any address you did not paste from a current list.

Why addresses get retired at all

Load, pressure, key rotation, or an operational decision nobody explains. From outside the reason is unavailable and does not matter. What matters is that retirement is normal, expected, and the published set is the only statement about what is in use. An address is not retired because it was bad and it does not come back because things improved.

The specific trap for long term readers

Experience produces a shortcut: you recognise the opening characters and stop reading, because you have typed or pasted that string dozens of times and it has always worked. The shortcut was earned honestly and it is exactly the thing being exploited.

Newer readers paste from a current list every time, because they have nothing memorised. That is one of the few places in this subject where having less experience is safer, and it is worth knowing about yourself.

What to do with an address you are unsure about

  1. Do not log in first and check afterwards. That order gives away everything the check was for.
  2. Compare it against the current published set, in full, pasted rather than read.
  3. If it is not on the list, it is not in use. Not maybe, not an old mirror still running quietly.
  4. Delete it from wherever you keep addresses, so the same question does not come up again in six months.