nexusmarkettorReference procedures for using Nexus Market over Tor
14 documents in 4 classes
3 verified addresses
Archive All documents Access and transport Verification and authenticity Payment and settlement Operations and risk Addresses FAQ Scope

Archive > Operations and risk > NM-014

NM-014: Outage response and risk posture

IdentifierNM-014
Versionv1.0 · in review
SubjectsOperations and risk, incident handling (NMT.ops)
Last updated7 Aug 2026
Applies toNexus Market, running since 2023, 2 of 3 multisig escrow
AbstractDefines the correct posture during a service outage, identifies the behaviour that converts an inconvenience into a loss, and states the standing measures that make an outage inconsequential.

1. Posture

An outage costs patience. It does not cost money. Every documented loss connected to an outage comes from the reaction to it rather than the outage itself, which makes doing nothing the strongest available response in most cases.

2. Permitted actions

  • Rebuild the circuit and retry
  • Try another address from a set held before the outage began
  • Wait and retry later
  • Check whether other onion services are reachable, to classify the failure

3. Prohibited actions

  • Searching for a replacement address, which is the origin of most credential losses
  • Accepting an address from a message, comment or announcement that appeared during the outage
  • Entering credentials on any page that has not passed the login screen verification
  • Sending funds to any address published as an emergency alternative

4. Standing measures

Two measures make an outage inconsequential in advance. Hold a verified address set before you need one, so a failure produces an alternative rather than a search. And hold no balance on the market beyond the current order, so that even a permanent outage costs you nothing but access.

5. Distinguishing a permanent ending

A market ending is preceded by a recognisable pattern rather than by silence alone. Withdrawals slowing while deposits continue, support going quiet over weeks, established vendors leaving together, signed communication stopping while the site remains up. None of that is inferable from an address being unreachable for a day, and the standing measures above make the distinction unnecessary for your own exposure.

Verified address set

Verified address set
[1]nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onion
[2]nexusma2iegzo7atzwbrwxhcdopyri3vare2twibldnlc3txqjdeb5yd.onion
[3]nexusabcd6tyfhdwilyitaqiri6tisj2v2hueyjuj6qkvd6azvi5tuqd.onion

Required check. Open in Tor Browser only. Before entering anything, compare the onion printed on the login screen against your browser address bar. A mismatch means the page is a copy and the tab should be closed. See NM-004.

Other documents in Operations and risk

NM-011v2.2 · core
Subjects: Operations and risk (NMT.ops)
Updated: 2 Aug 2026
Specifies the account creation requirements that make a credential leak survivable, and identifies the one decision in the process that cannot be corrected later.
NM-012v1.0 · stable
Subjects: Operations and risk (NMT.ops)
Updated: 22 Jul 2026
Specifies what to read on a vendor profile and in what order, distinguishes the fields carrying information from those that do not, and defines a first order policy.
NM-013v1.1 · stable
Subjects: Operations and risk (NMT.ops)
Updated: 28 Jul 2026
Specifies when to open a dispute, what a submission should contain, and why brevity and dates outperform argument in arbitration.