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 > Listing > Verification and authenticity

Verification and authenticity

Documents covering onion address verification, the login screen check that identifies a cloned page, where published addresses come from and how phishing works.

Class code NMT.ver. Documents in this class are listed below in identifier order.
NM-004v3.0 · core
Subjects: Verification and authenticity (NMT.ver)
Updated: 6 Aug 2026
Specifies the single check that distinguishes the genuine market from a cloned login page, explains why it cannot be defeated by a copy, and defines the required response to a failed check.
NM-005v1.1 · stable
Subjects: Verification and authenticity (NMT.ver)
Updated: 24 Jul 2026
Defines what makes a published address trustworthy, ranks the common sources by reliability, and explains why the moment of greatest risk is an outage.
NM-006v1.0 · stable
Subjects: Verification and authenticity (NMT.ver)
Updated: 20 Jul 2026
Describes how cloned marketplace pages operate, which signals genuinely distinguish them, and which commonly cited signals carry no information.

How this class fits together

Verification is the highest value class in the archive and the shortest to apply. It rests on one observation, which is that everything visible about a page can be copied but the address a page lives at cannot be faked to the browser. From that single fact the whole class follows, including why appearance carries no information, why a familiar prefix is weaker evidence than none, and why the comparison has to happen every session rather than only the first time.

The three documents divide the problem by where it occurs. NM-004 covers the moment of use, which is the comparison performed on the login screen before anything is typed. NM-005 covers what happens before that, which is where the address came from and why sources rank differently under pressure than they do in the abstract. NM-006 describes the threat itself, since knowing how a cloned page actually operates makes both other documents easier to apply and harder to talk yourself out of.

Read together they answer a question the rest of the archive assumes: whether the thing you are following procedures against is the market at all. Every other class in this archive is worthless if that question is answered wrongly, which is the reason two of the three documents here carry core status.

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.