nexusmarkettorReference procedures for using Nexus Market over Tor
An open archive of numbered procedures covering how to reach the market, how to establish that the page you reached is genuine, how settlement works, and how to handle the situations that go wrong. Every document states why a step exists rather than only what to do, so it can be applied rather than followed.
nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onionnexusma2iegzo7atzwbrwxhcdopyri3vare2twibldnlc3txqjdeb5yd.onionnexusabcd6tyfhdwilyitaqiri6tisj2v2hueyjuj6qkvd6azvi5tuqd.onionRequired 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.
Documents covering Tor Browser setup, onion addressing, circuit behaviour and what to do when an address stops answering.
Documents covering onion address verification, the login screen check that identifies a cloned page, where published addresses come from and how phishing works.
Documents covering settlement coin selection, wallet custody, the deposit sequence and confirmation timing, the escrow protocol and withdrawal policy.
Documents covering the account creation standard, key management, counterparty assessment, dispute submission and how to behave during an outage.
Complete listing of all 14 documents
If you have not used the market before, read NM-001 and NM-002 in order, then NM-004 before you enter anything anywhere. Those three cover obtaining a browser you can trust, understanding what an address is, and establishing that the page in front of you is the market rather than a copy of it. Nothing else in the archive substitutes for them.
If you have used it before and something specific is unclear, the subject classes above are the faster route. Payment questions sit in NMT.pay, anything about accounts, counterparties or disputes sits in NMT.ops, and reachability failures are classified in NM-003.
Documents are versioned and dated because guidance without a date cannot be judged. Where a procedure changes, the version increments and the date moves rather than the text being quietly replaced.