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.
Describes 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.
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.
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.
Defines what makes a published address trustworthy, ranks the common sources by reliability, and explains why the moment of greatest risk is an outage.
Compares the settlement options accepted by Nexus in terms of what each records permanently, and states why this decision outlasts every other decision a buyer makes.
Specifies the path funds should take from acquisition to an order, why an intermediate wallet under your control is required, and how recovery material is handled.
Specifies the account creation requirements that make a credential leak survivable, and identifies the one decision in the process that cannot be corrected later.
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.
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.
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.
Status meanings
core marks a procedure the rest of the archive depends on, where skipping it invalidates the others. stable marks a procedure that is settled and unlikely to change. in review marks one being revised, which does not mean it is wrong, only that the wording is being worked on.
nexusmarkettorReference procedures for using Nexus Market over Tor