Research Database & FAQ

Comprehensive documentation regarding Nexus Market Link infrastructure, cryptographic protocols, and network architecture. Data is compiled for educational analysis and research purposes.

1. Access & Network Architecture

Nexus Market functions exclusively as a Tor Hidden Service, utilizing Version 3 (v3) Onion addresses. These addresses are 56 characters long and employ ed25519 cryptography for enhanced security and anonymity compared to legacy v2 addresses.
Nexus employs complex client-side computation puzzles (proof-of-work captchas) to mitigate Distributed Denial of Service (DDoS) attacks. These require the accessing browser to perform calculations, increasing the resource cost for attackers attempting to flood the network.
Latency within the Tor network is common due to the multi-hop routing architecture (Guard, Middle, Exit/Rendezvous nodes). Additionally, heavy DDoS mitigation filters can add processing time to initial connection requests.
While the core market functionality is designed to be accessible, modern DDoS protection layers often require JavaScript to solve proof-of-work challenges before granting access to the static .onion site.

2. Security & Verification

PGP (Pretty Good Privacy) verification is the cryptographic standard for authenticating mirrors and communications. It ensures that the onion service accessed is signed by the market's private key, preventing Man-in-the-Middle (MitM) attacks and ensuring data integrity.
2FA on Nexus employs PGP encryption. Upon login, the server presents an encrypted message block that can only be decrypted by the user's private PGP key. The user must decrypt this message to reveal a unique code/token required to complete the login process.
Mirrors are verified by importing the market's public PGP key into a keyring (e.g., Kleopatra or GPG). Users then verify the signed message found on the landing page. A valid signature confirms the mirror is controlled by the private key holder.

3. Transaction Protocols

Unlike traditional centralized wallet systems, the walletless pay mechanism generates a unique deposit address for every individual order. Funds are transferred directly from the buyer to this specific escrow address, reducing the risk of centralized fund seizure or platform insolvency.
The network infrastructure supports both Monero (XMR) and Bitcoin (BTC). Monero is often prioritized in technical documentation due to its ring signature privacy features, which obfuscate transaction origins and amounts.
The escrow system acts as a neutral holding state. Funds are locked in the order address until the transaction is finalized by the buyer or the auto-finalize timer expires. In cases of dispute, a moderator intervenes to direct the release of funds.
The auto-finalize timer is a protocol that automatically releases escrowed funds to the vendor if the buyer takes no action within a specific timeframe (typically 7-14 days depending on the item type). This prevents funds from being indefinitely locked.
Standard Escrow holds funds until delivery is confirmed. Finalize Early (FE) allows the vendor to access funds immediately upon marking an order as shipped. FE privileges are typically reserved for vendors with high reputation metrics and long operational history.

4. Troubleshooting & Policy

The mnemonic seed is a cryptographic recovery phrase generated upon account creation. It is the only method to recover account access if a password is lost or if 2FA needs to be reset, as the system does not store personal email data.
Analysis of the registration architecture indicates that Nexus Market has historically operated without a mandatory monetary vendor bond. Instead, they rely on a reputation-based vetting system and strict adherence to policy guidelines to maintain network quality.
If a dispute is opened before the auto-finalize timer expires, the escrow allows a moderator to review the transaction details. The moderator then cryptographically signs a release transaction to either refund the buyer or pay the vendor.