TorZon Market Knowledge Base
This document outlines the operational parameters, security protocols, and usage guidelines for the TorZon Darknet Market ecosystem. Users are expected to familiarize themselves with these protocols to ensure operational security (OpSec) and seamless transactions.
1. Access & Network Connectivity
Access requires the Tor Browser, available from the Tor Project. Standard browsers (Chrome, Firefox, Safari) cannot resolve .onion top-level domains. Once the Tor circuit is established, input a verified TorZon onion link into the address bar. Ensure Javascript is set to "Disabled" in the browser security settings to mitigate browser-based fingerprinting exploits.
TorZon utilizes a rotational mirror system to mitigate Distributed Denial of Service (DDoS) attacks common on the Tor network. If a specific mirror becomes unresponsive due to network congestion or attack, consult the verified mirrors list on the Links page. We recommend refreshing your circuit (New Identity) if connection latency persists.
Every login page on the TorZon market contains a PGP-signed message signed with the market's official private key. Users should import the TorZon Public Key into their PGP client (GPG, Kleopatra) and verify this signature before entering credentials. This cryptographic verification ensures you are connected to the genuine server infrastructure.
2. Financial Protocol
TorZon supports Bitcoin (BTC) and Monero (XMR). Monero is the preferred currency for operational security due to its ring signature and stealth address technology, which obfuscates transaction history. Bitcoin is supported for liquidity but offers less privacy; coin mixing is recommended prior to deposit if using BTC.
Bitcoin: Requires 2 network confirmations (approx. 20 minutes).
Monero: Requires 10 network confirmations (approx. 20-30 minutes).
Wallet balances update automatically once the blockchain threshold is met. Do not open a support ticket for unconfirmed transactions; wait for the blockchain to process the blocks.
Both methods are supported. Users may maintain a balance in their onsite wallet for rapid checkouts, or utilize "Direct Pay" at checkout to generate a unique invoice address for a single order. Direct Pay minimizes the time funds are held on the market platform.
Withdrawals are processed automatically by the backend daemon. A flat network fee is deducted from the withdrawal amount to cover miner priority fees. For security, users must enter their account PIN and 2FA code (if enabled) to authorize any outbound transfer.
3. Security & Account Management
PGP (Pretty Good Privacy) is integral to TorZon operations. Users are strongly encouraged to add a Public PGP Key to their profile immediately upon registration. This enables Two-Factor Authentication (2FA), ensuring that even if a password is compromised, the account cannot be accessed without the private key.
We adhere to a strict data minimization policy. Order information, chat logs, and transaction history are retained only for the duration of the escrow period plus 30 days for dispute resolution. After this period, data is purged from the servers. Users are advised to locally save any necessary information before it is deleted.
Stealth Mode is a UI setting that disables the loading of product images. This serves two purposes: it drastically reduces bandwidth consumption for faster page loads over the Tor network, and it enhances privacy by preventing image-based metadata loading. This can be toggled in the User CP.
4. Marketplace Operations
TorZon acts as a trusted intermediary. When an order is placed, funds are held in the market's escrow wallet. The vendor is notified to ship. Once the buyer receives the goods and inspects them, they must "Finalize" the order to release funds to the vendor. If no action is taken, funds auto-release after 14 days (physical goods) or 48 hours (digital).
Disputes should be opened if an item is not received within the estimated timeframe or arrives significantly different from the description. Opening a dispute freezes the escrow timer. Moderators will review chat logs, tracking information (if applicable), and vendor history before issuing a refund or releasing funds.
Vendor accounts require a non-refundable bond of $250 USD (paid in crypto) to prevent spam and low-quality merchants. This bond is paid directly through the "Become a Vendor" tab in the dashboard. Established vendors with verifiable history on other markets (Recon/Dread) may apply for a bond waiver via support ticket.
Network Status
Market Stats
Verified Entry Nodes
Main V3 Onion:
torzonvdudh6nljgtykaskpusutcrezkwjvih3azoxei4d7ec527s2id.onion
Failover Mirror:
torzonvhw6cug47m5w43ldoj2mkp66wpcyljnoc2alkc42qqjuvt5gyd.onion
OpSec Reminder
Always encrypt sensitive shipping data using PGP before pasting it into the order form. Do not rely solely on server-side auto-encryption.