Technical Knowledge Base

The Nexus Onion Link infrastructure refers to the collection of decentralized hidden services (V3 Onion addresses) that host the market interface. It utilizes the Tor network to obfuscate server location and protect user anonymity through end-to-end encryption.

Accessibility issues often stem from Distributed Denial of Service (DDoS) attacks targeting the Tor circuit introduction points. Additionally, routine maintenance or Tor network congestion can cause temporary timeouts. Mirrors are deployed to provide redundancy during these events.

Access to the Nexus infrastructure requires the Tor Browser. Standard browsers cannot resolve .onion TLDs. For maximum security, the security slider is typically set to 'Safer' or 'Safest', which disables JavaScript on non-HTTPS sites to prevent script-based deanonymization.

Nexus utilizes PGP (Pretty Good Privacy) digital signatures. The market signs a timestamped message containing the current active mirrors with its private key. Users verify this message against the market's public key to confirm the mirrors are authentic and not phishing sites.

Two-Factor Authentication (2FA) on Nexus relies on PGP. During login, the server presents an encrypted message that can only be decrypted by the user's private PGP key. This ensures that even if a password is compromised, the account cannot be accessed without the private key.

JavaScript presents a significant attack surface in anonymous browsing. Malicious scripts can be used to exploit browser vulnerabilities, fingerprint users, or leak real IP addresses. The platform is designed to function with minimal to no client-side scripting.

The escrow system holds funds in a temporary neutral wallet until the transaction is finalized. Funds are released to the vendor only after the buyer confirms receipt or the auto-finalization timer expires. In disputes, a moderator reviews the case.

Walletless Pay eliminates the need to deposit funds into a central market wallet. Instead, a unique invoice address is generated for each order. Users send the exact amount to this address, reducing the risk of funds being seized or lost in a centralized exit scam.

Historical data indicates that Nexus has fluctuated on this policy. Currently, research suggests no mandatory vendor bond is required for basic listings, though premium status tiers may require a deposit to unlock advanced features.

The standard auto-finalize timer is typically set to 7-14 days depending on the shipping type (digital vs. physical). If a buyer does not dispute or finalize the order within this window, funds are automatically released to the vendor.

The infrastructure supports Monero (XMR) for maximum privacy, as well as Bitcoin (BTC) and Litecoin (LTC). Monero is the recommended standard due to its ring signature and stealth address technology which obfuscates transaction history.

Captcha failures are often caused by clock desynchronization on the client device or Tor circuit latency. Ensuring the system clock is accurate and refreshing the Tor identity (new circuit) usually resolves this issue.

Account recovery is performed using a mnemonic seed phrase provided during registration. Without this phrase or the associated PGP key, access cannot be restored due to the non-custodial nature of the database encryption.

Blockchain confirmations require time. Monero typically requires 10 confirmations, while Bitcoin requires 1-2 depending on market settings. Network congestion can also delay the appearance of funds in the interface.