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-013

NM-013: Dispute submission procedure

IdentifierNM-013
Versionv1.1 · stable
SubjectsOperations and risk, arbitration (NMT.ops)
Last updated28 Jul 2026
Applies toNexus Market, running since 2023, 2 of 3 multisig escrow
AbstractSpecifies when to open a dispute, what a submission should contain, and why brevity and dates outperform argument in arbitration.

1. Trigger conditions

Open a dispute when the stated dispatch window has clearly passed without dispatch, when goods have not arrived within a reasonable period after dispatch, or when what arrived does not match the order. Do not open one while a stated window is still running.

2. Prior action

Send one clear message with the order reference and a specific question before escalating. A single precise message is more likely to produce a response than several vague ones, and its presence in the record helps the submission afterwards.

3. Submission contents

  1. Order reference and the relevant dates, stated first
  2. What was ordered, what arrived, and when
  3. Any listing terms that bear on the outcome, quoted accurately
  4. The outcome being requested, stated plainly

4. What to omit

Characterisation of the other party, restatement of the same point, and description of how the situation feels. Arbitration compares two accounts of one order against whatever the market recorded. Material that cannot be checked adds length without adding weight, and length reads as uncertainty.

5. Evidence boundary

Only what happened inside the market message system is available to arbitration. A conversation moved to an outside channel is effectively invisible to the process, which is the operational reason to refuse such moves rather than a matter of preference.

6. During the dispute

Funds remain in escrow while the dispute is open, so delay costs time rather than money. Do not confirm receipt to close a dispute that appears to be going badly, since that action releases the payment and ends the process in the counterparty favour.

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-014v1.0 · in review
Subjects: Operations and risk (NMT.ops)
Updated: 7 Aug 2026
Defines 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.