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 > Payment and settlement > NM-008

NM-008: Wallet custody and funding path

IdentifierNM-008
Versionv1.3 · stable
SubjectsPayment and settlement, custody (NMT.pay)
Last updated31 Jul 2026
Applies toNexus Market, running since 2023, 2 of 3 multisig escrow
AbstractSpecifies 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.

1. Required path

Acquisition, then a wallet you control, then the order. The intermediate step is not optional in this procedure and it is the difference between a payment and a straight line from an identity checked account to a marketplace order.

2. Acquisition

Coin may be bought on an exchange with an identity check, traded peer to peer, or swapped from another coin without an account. These differ in how much identity is attached at purchase and are otherwise equivalent for this procedure. The exchange route is the most convenient and produces a record connecting a name to a withdrawal, which is precisely why the funds then move.

3. Custody

Coin held on an exchange is controlled by the exchange, subject to whatever happens to that company, and attached to the identity used at signup. A local wallet holds the keys on your own device. For Monero, Feather on desktop and Cake on mobile both route over Tor and both are straightforward. The official GUI suits anybody wanting to run a full node.

4. Recovery material

  • The recovery seed is the wallet. The application and the device are replaceable, the words are not
  • Write it on paper at creation, before putting anything of value into the wallet
  • Store it away from the device it belongs to
  • Never type it into a web page and never photograph it or place it in a synced note

5. Funding

From the wallet, send to the deposit address issued for the specific order. Configure the wallet to add the network fee on top of the amount rather than deduct it, since deduction produces a shortfall on every order and a shortfall leaves the order unfunded.

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 Payment and settlement

NM-007v2.0 · core
Subjects: Payment and settlement (NMT.pay)
Updated: 4 Aug 2026
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.
NM-009v1.2 · stable
Subjects: Payment and settlement (NMT.pay)
Updated: 26 Jul 2026
Defines the deposit sequence, expected confirmation timing, and the failure modes that account for nearly all deposits that appear not to arrive.
NM-010v1.1 · core
Subjects: Payment and settlement (NMT.pay)
Updated: 1 Aug 2026
Describes the two of three multisig arrangement used on Nexus, the conditions under which funds move, and the single action that voids the protection.