Nexus Loss Table Ranked by expected cost, not by how frightening it sounds
Table › What stops it

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.

Refuse urgency

Not a defence against one entry but the condition underneath most of them, because checking defeats nearly everything and urgency is what prevents checking.

The rule

Nothing genuine in this subject requires action within a stated period. Real address changes run long overlaps precisely so nobody has to hurry. So a deadline is not a schedule, it is the request telling you what it is.

What you seeWhy it is there
Migrate within 24 hoursReal changes overlap for exactly this reason
Your account will be restrictedFear, plus a reason to act before checking
Escrow is down, pay directA reason to hurry attached to a reason to bypass
A helpful address during an outageThe timing is the manipulation
The signing key has changedThe hardest case, and where waiting matters most

The three that genuinely are urgent

The real exceptionsA wallet phrase given away. A second factor code passed to somebody. A session you believe is compromised right now. All three are measured in minutes, and all three follow a mistake rather than precede a decision.

That distinction does most of the work. Genuine urgency arrives after something has gone wrong. Anything urgent asking you to do something new is the opposite pattern.

Rules instead of judgement

  1. Anything with a stated deadline gets nothing for a day.
  2. Anything arriving during an outage gets nothing until the outage ends.
  3. Anything asking for credentials or a wallet phrase gets nothing ever.

Three rules, no assessment required. They work because judgement is exactly what urgency attacks, and a rule decided in advance is not available to be attacked in the moment.

Why urgency is the load bearing part

Almost everything in this table is defeated by checking. A copied page fails a signature check, a near miss fails a comparison, a request to step outside escrow fails a flat rule. So anybody who wants any of them to succeed has one job, which is to stop the check happening, and a deadline is the cheapest way to do it. That makes urgency less a tactic than a prerequisite.

What the delay costs, honestly

If the pressure was fakeIf it was genuine
You lost nothing at allYou waited a day
You kept the balance, the account or the paymentThe address you were told to migrate to still works, because real changes overlap
You avoided the entry it was aimed atYou verified before acting, which was going to be necessary anyway

That is an unusually clean asymmetry. Most trade-offs on this site have a real cost on both sides, and this one does not.

Outages, where it matters most

During a stretch when nothing loads, the comparison you would normally run is unavailable and everybody is looking for a way in. That is the moment helpful addresses appear, and the timing is the manipulation rather than a coincidence. Waiting for the outage to end costs you access you did not have anyway, which makes it the easiest instance of the rule to follow and the one most often broken.