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

NM-011: Account creation standard

IdentifierNM-011
Versionv2.2 · core
SubjectsOperations and risk, identity separation (NMT.ops)
Last updated2 Aug 2026
Applies toNexus Market, running since 2023, 2 of 3 multisig escrow
AbstractSpecifies the account creation requirements that make a credential leak survivable, and identifies the one decision in the process that cannot be corrected later.

1. Requirements

  1. A username used nowhere else, on any platform, ever
  2. A password generated by a local manager rather than composed
  3. The recovery phrase written on paper and stored away from the device
  4. PGP two factor enabled at creation rather than later
  5. The signing key backed up offline the same day it is generated

2. The irreversible decision

Passwords can be changed and keys can be rotated. A username that also exists on a forum you have posted to for years cannot be unlinked afterwards, because the association was created the moment both existed. This is the only requirement here with no repair path, which is why it appears first.

3. Two factor

With PGP two factor enabled, signing in requires proving control of a key as well as knowing the password. A credential leak becomes an inconvenience rather than the loss of the account. The corresponding risk is losing the key, which is why the backup requirement is stated in the same document rather than separately.

4. Recovery material handling

The recovery phrase restores the account and is therefore the object every phishing page is built to collect. It belongs on paper. It does not belong in a synced note, a screenshot, or any web form, including one that presents itself as an account recovery tool.

5. Verification

This standard is met when a leaked password alone would not open the account, a lost device would not lose the account, and nothing about the username connects to any identity you hold elsewhere.

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