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

NM-010: Escrow protocol and release conditions

IdentifierNM-010
Versionv1.1 · core
SubjectsPayment and settlement, escrow (NMT.pay)
Last updated1 Aug 2026
Applies toNexus Market, running since 2023, 2 of 3 multisig escrow
AbstractDescribes the two of three multisig arrangement used on Nexus, the conditions under which funds move, and the single action that voids the protection.

1. Arrangement

An order payment is held at an address requiring two of three keys before it can move. The keys are held separately by the buyer, the vendor and the market. No party can move the funds alone, which is the property that makes buying from a stranger workable.

2. Release conditions

SituationKeys usedOutcome
Order arrives and is correctBuyer and vendorPayment released to the vendor
Dispute decided for the buyerBuyer and marketPayment returned
Dispute decided for the vendorVendor and marketPayment released
Market unavailableBuyer and vendorParties can still settle between themselves

3. Scope of protection

Escrow protects the payment attached to an order. It does not protect a balance held outside one, it does not make a vendor competent, and it does not guarantee an outcome in a dispute. Its scope is narrow, which is why it works.

4. Voiding condition

Confirming receipt before goods arrive releases the payment and removes the dispute route in the same action. This is the only user action that voids the protection entirely, and it is irreversible. Requests to do so should be declined as a matter of policy rather than judged case by case, because the ability to distinguish a legitimate request from a fraudulent one is exactly what a buyer lacks.

5. Correct behaviour

Confirm receipt when the goods are physically present and match the order. Not before, not as a courtesy, and not to encourage progress on a slow order.

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-008v1.3 · stable
Subjects: Payment and settlement (NMT.pay)
Updated: 31 Jul 2026
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.
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.