Platform Architecture & FAQ

The Nexus Market infrastructure is hosted as a hidden service within the Tor network. Onion routing encapsulates data in multiple layers of encryption (like an onion). The data is transmitted through a series of network relays, where each relay peels away a single layer of encryption to reveal the next destination. This ensures that the IP address of the user and the server remain cryptographically concealed from each other.

Hidden services are frequent targets of Distributed Denial of Service (DDoS) attacks. To mitigate this, the platform utilizes a rotating mirror system. When a specific circuit becomes overloaded, it is discarded, and traffic is routed to alternative V3 onion addresses. Users are advised to verify PGP signatures on new mirrors before inputting credentials.

Access requires the Tor Browser configured to the 'Safest' security level. This setting disables JavaScript, preventing the execution of malicious scripts that could de-anonymize the user session via browser fingerprinting or IP leakage.

PGP 2FA is a cryptographic challenge-response mechanism. Upon login, the server encrypts a random alphanumeric string using the user's public PGP key. The user must decrypt this message using their private key and input the resulting string. This proves the user holds the private key associated with the account, securing it even if the password is compromised.

Nexus utilizes a predetermined "Anti-Phishing Code" set by the user during registration. This code is displayed on the login landing page. If the user does not see their specific code, they are likely on a phishing site and should exit immediately. Additionally, verifying the site's PGP signature provides mathematical proof of authenticity.

Due to the absence of email databases for security, password recovery is handled via a mnemonic seed phrase generated at account creation. This sequence of words is the cryptographic seed required to restore account access. If this phrase is lost, the account is permanently inaccessible.

Traditional markets require users to deposit funds into a central wallet, creating a single point of failure (exit scam risk). Walletless Pay architecture avoids this by generating a unique invoice address for every individual order. Funds are sent directly to the order escrow or the vendor, minimizing the amount of cryptocurrency held in central custody at any given time.

Funds are held in escrow by the market protocol. The vendor does not receive payment until the buyer marks the order as finalized. If the buyer takes no action, an "Auto-Finalize" timer (typically 7-14 days) triggers the release of funds. Disputes pause this timer and invite administrator adjudication.

The platform supports both, but implies different privacy models. Bitcoin transactions are recorded on a public ledger, traceable via chain analysis. Monero utilizes RingCT and stealth addresses to obfuscate the sender, receiver, and amount. XMR is generally preferred for its intrinsic privacy features.

To list items, accounts must pay a non-refundable bond (historically valued between $200-$1000 USD). This creates a financial barrier to entry that deters spammers and low-effort scammers from flooding the listings.

Captcha failure is often due to clock synchronization issues. The Tor network requires precise time settings. Ensure your system clock is synchronized to UTC. Additionally, aggressive circuit rotation can cause session tokens to expire mid-verification.

Cryptocurrency networks require a specific number of block confirmations before a balance is credited (e.g., 2 confirmations for BTC, 10 for XMR). If the blockchain is congested, this delay increases. Users must verify the transaction ID (TXID) on a block explorer to confirm it has been broadcast.