Multisig Escrow
The Nexus site uses automated 2-of-3 multisignature escrow for every transaction. Buyer, vendor, and the platform each hold one key; release requires two signatures. This eliminates single-point-of-failure exit scams and ensures funds are only released when the buyer confirms receipt or the dispute window expires with no claim.
On the Nexus url you can view escrow status and sign from your dashboard. Partial releases are supported for multi-item orders.
Vendor Bonding
To list on the Nexus site, vendors must lock a high-value bond in XMR. Bond tiers determine listing limits and visibility. If a vendor exit-scams or repeatedly violates policy, the bond is slashed and used for dispute payouts.
Bond amounts are published on the Nexus url. Always check vendor bond status before large orders.
End-to-End Encrypted Messaging
All messages and support tickets on the Nexus site are encrypted via PGP by default. The server never has access to plaintext. You and the vendor (or support) exchange public keys; encryption happens client-side.
Use the Nexus url PGP verify page to confirm the site's key before sending sensitive data.
No JavaScript Requirement
The Nexus url interface is fully functional without client-side JavaScript. You can browse, order, and communicate with JS disabled in Tor Browser for maximum OPSEC.
Recommended: use the Nexus site with "Safest" security level in Tor Browser.
Auto-Shop Support
Digital goods vendors on the Nexus site can use the auto-shop system for instant delivery. After payment confirms, the buyer receives the product automatically without vendor intervention.
Auto-shop listings are marked on the Nexus site product page.
Warrant Canary System
The Nexus site publishes a bi-weekly warrant canary signed by the admin PGP key. If a canary is missing or the message changes, do not use the Nexus url until an explanation is provided.
Canary history is available on the Nexus url; verify signatures with the published admin key.