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 > Access and transport > NM-002

NM-002: Onion addressing and the verified address set

IdentifierNM-002
Versionv1.4 · stable
SubjectsAccess and transport, addressing (NMT.acc)
Last updated3 Aug 2026
Applies toNexus Market, running since 2023, 2 of 3 multisig escrow
AbstractDescribes the structure of a version three onion address, why Nexus publishes several at once, and the handling rules that prevent an operator error from becoming a loss.

1. Address structure

A version three onion address is fifty six characters followed by the .onion suffix. Those characters are derived from a public key rather than chosen, which is why they look like noise and why they cannot be shortened, guessed or corrected from memory. Two addresses differing by one character are unrelated services with no connection to each other.

2. Why several addresses exist

Nexus publishes more than one address and keeps them live simultaneously. A hidden service absorbs sustained traffic floods, and a service reachable at a single address stops being reachable at all when that address is targeted. Several addresses means an attacker has to hold all of them at once to produce the same effect.

The addresses are entry points to one service rather than copies of a site. The account, the balance, the order history and any open dispute are identical behind each one, so switching mid session costs nothing and loses nothing.

3. Handling rules

  1. Copy addresses, never type them, because fifty six characters reproduced by hand is the single most common way somebody lands on a lookalike
  2. Take them from a source you trusted before you needed one, rather than from a search performed while your usual address is quiet
  3. Store them somewhere you will still have in six months, and check a stored address against a current source before use
  4. Treat any address arriving through a chat message or a comment as unverified regardless of who sent it

4. The verified set

The addresses listed on this archive are the set it treats as verified. They are shown in full rather than shortened, with a copy control, on every page, because an address that has to be hunted for is an address somebody will end up searching for instead.

5. Retirement

Addresses are retired and replaced over time. A saved address that stops working is more often retired than compromised, but the two look identical from outside, which is why the rule is to check against a current source rather than to assume either.

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 Access and transport

NM-001v2.1 · core
Subjects: Access and transport (NMT.acc)
Updated: 5 Aug 2026
Specifies how Tor Browser should be obtained, verified and configured before a first connection to Nexus Market, and states why each step exists rather than only what to do.
NM-003v1.2 · stable
Subjects: Access and transport (NMT.acc)
Updated: 29 Jul 2026
Classifies the reachability failures a user encounters, separates causes local to the user from causes at the service, and specifies the response for each class.