Knowledge Base

Technical FAQ Database

A comprehensive repository of technical specifications, operational logic, and troubleshooting protocols for the Nexus Darknet ecosystem.

Access & Connectivity

What are the browser requirements for Nexus?

Access strictly requires the Tor Browser or a similar routing configuration capable of resolving .onion top-level domains. Standard browsers (Chrome, Edge, Safari) cannot access the hidden service network. For maximum security, the security slider in Tor should be set to "Safest" to disable JavaScript, which mitigates browser fingerprinting and XSS vectors.

Why do nexus onion links frequently time out?

Timeout errors are typically caused by network latency within the Tor circuit, client-side clock desynchronization, or DDoS attacks targeting specific guard nodes. If the main URL is unresponsive, users reference signed mirror lists.

DIAGNOSTIC: Check your system clock and ensure Tor circuit is established before retrying.

Where can I find verified mirror links?

Verified mirrors are distributed via PGP-signed messages from the market administrators. Below is the current primary entry node for reference:

Security Architecture

How does PGP Two-Factor Authentication (2FA) function?

When 2FA is enabled, the server encrypts a random alphanumeric string (the challenge) using the user's public PGP key. The user must copy this encrypted block, decrypt it locally using their private key and Gpg4win/GPG Suite, and return the decrypted string to the server. This cryptographic challenge proves identity without transmitting passwords.

What is the mnemonic recovery protocol?

Upon account creation, a 12-24 word mnemonic seed is generated. This is the only mechanism for password resets. Nexus architecture does not store email addresses or personal identifiers. If a user loses their password and their mnemonic, the account is cryptographically irretrievable.

How is session hijacking prevented?

Sessions are bound to a specific Tor circuit. If the circuit changes (e.g., New Identity is clicked), the session is invalidated. Additionally, aggressive timeout policies (15-30 minutes of inactivity) are enforced to reduce the attack surface of unattended terminals.

Market Logic & Payments

Explain the "Walletless Pay" system.

Walletless pay removes the need for a central market wallet. Instead of depositing funds into a balance, a unique address is generated for each specific order. The user sends the exact amount to this address. The funds move to an escrow state and are released to the vendor upon finalization. This limits the potential impact of a market-wide seizure or exit.

What cryptocurrencies are supported?

  • Monero (XMR): Primary supported currency. Utilizes RingCT and stealth addresses for transaction history obfuscation.
  • Bitcoin (BTC): Supported for liquidity, though typically requires external mixing or CoinJoin before use to maintain privacy.
  • Litecoin (LTC): Supported on select legacy mirrors for lower fees.

Does Nexus require a Vendor Bond?

Historically, Nexus has operated with a low-barrier entry system, often waiving vendor bonds for established entities migrating from other defunct platforms. However, this policy is dynamic and subject to change based on spam volume. Vendors are vetted through reputation analysis rather than purely financial gates.

How does the auto-finalize timer work?

If an order is marked as shipped and the buyer does not dispute or finalize it manually, the escrow system automatically releases funds to the vendor after a set period.

Digital Goods: 4-7 Days Physical Goods: 14-21 Days

Troubleshooting

Why is my deposit not showing up?

Deposits require a specific number of blockchain confirmations before being recognized by the Nexus daemon.
  • Bitcoin: 2 Confirmations (~20-40 mins)
  • Monero: 10 Confirmations (~20 mins)

If the time exceeds this window, verify that the correct generated address was used.

I am stuck in a Captcha loop.

Captcha loops often occur when the Tor circuit is dirty or flagged. To resolve:
  1. Click "New Circuit for this Site" in Tor browser.
  2. Ensure JavaScript is fully disabled.
  3. Verify the clock on your host machine is synchronized.

Can't find what you're looking for? Check the Security Protocols page for deep-dive analysis.