Research Database & FAQ

Nexus operates as a hidden service within the Tor network, utilizing standard onion routing protocols to mask server location and user IP addresses. It employs a centralized database structure with distributed mirror endpoints to manage load balancing and redundancy.

The .onion top-level domain is not resolvable by standard DNS servers. Tor Browser routes traffic through an overlay network consisting of three relays, which provides the necessary anonymity and access capabilities to reach the hidden service descriptors.

To mitigate Distributed Denial of Service (DDoS) attacks, the network frequently rotates active onion addresses. This rotation distributes traffic across different nodes, preventing any single point from becoming overwhelmed by malicious traffic floods.

PGP (Pretty Good Privacy) signatures are used to authenticate messages and mirror links. The platform signs all official communications with a private key. Users verify this signature against the known public key to confirm the data has not been altered or spoofed.

2FA is implemented via PGP. Upon login, the server encrypts a unique challenge code using the user's public key. The user must decrypt this message using their private key and return the code to prove identity. This prevents access even if the password is compromised.

The mnemonic seed is a cryptographically generated string of words provided during account creation. It serves as the sole method for account recovery and password resetting, as no email addresses or personal identifiers are stored in the database.

Unlike traditional market wallets that hold funds indefinitely, the walletless system generates a unique address for each order. Funds are routed directly to the escrow address associated with the specific transaction, minimizing the platform's custodial risk.

The protocol currently facilitates transactions in Bitcoin (BTC), Monero (XMR), and Litecoin (LTC). Monero is often preferred in analysis due to its RingCT (Ring Confidential Transactions) privacy features which obfuscate transaction amounts and sender/receiver addresses.

This is a pre-programmed variable that automatically releases held escrow funds to the vendor if the buyer does not dispute the order within a set timeframe (typically 7-14 days), assuming the tracking or delivery logic conditions are met.

Multi-signature (Multi-sig) escrow requires 2 of 3 keys (Buyer, Vendor, Platform) to authorize a transaction. This ensures that no single party can control the funds unilaterally without consensus from at least one other party.

Captcha failures often occur due to strict Javascript settings in the Tor Browser or latency between the client and the exit node. Ensure the browser security slider is set to 'Safer' rather than 'Safest' if visual elements are not loading correctly, though this reduces anonymity.

Account recovery is only possible via the mnemonic seed phrase provided at registration. Due to the encrypted, log-less nature of the database, administrative staff cannot reset passwords or retrieve accounts without this specific cryptographic key.

Confirmation times are dependent on the specific blockchain network load (Mempool status). For Bitcoin, the platform typically requires 2 confirmations to prevent double-spending attacks. Monero typically requires 10 confirmations.