Research & FAQ Database

The DrugHub infrastructure operates exclusively on Tor V3 hidden services. This protocol utilizes Ed25519 cryptography for address generation, resulting in 56-character addresses. This ensures end-to-end encryption and hides the server's physical location within the Tor network.

Mirror unavailability is typically a result of Distributed Denial of Service (DDoS) mitigation tactics. The network automatically rotates active circuits to absorb traffic spikes. This rotation can cause temporary connection timeouts on specific mirrors. Researchers are advised to check Links for current verified mirrors.

Access requires a Tor-compatible browser configured to route traffic through the Onion network. JavaScript settings usually need to be set to 'Safer' or 'Safest' to prevent client-side script execution vulnerabilities. Standard browsers (Chrome, Firefox) cannot resolve .onion domains natively.

Yes, all verified mirror links point to the same backend database. Data is synchronized across the load-balanced infrastructure, meaning actions taken on one mirror are reflected on all others.

The platform utilizes a 2FA challenge-response protocol. The server generates a random nonce, encrypts it with the user's public PGP key, and presents the ciphertext. The user must decrypt this using their private key and return the nonce to authenticate. This eliminates the need for password transmission.

Internal messaging utilizes RSA-4096 or curve25519 asymmetric encryption. Messages are encrypted client-side (recommended) or server-side before storage, ensuring that only the holder of the recipient's private key can read the content.

Users should import the market's public key into their GPG keychain. When a signed message is received, the 'verify' function in GPG checks the digital signature against the public key to ensure the message has not been altered by a third party.

The mnemonic system generates a seed phrase upon account creation. This phrase is the cryptographic key to recover account access and funds if the user loses their password or PGP key. It functions similarly to a cryptocurrency wallet seed.

The escrow system holds funds in a temporary multi-signature or server-controlled wallet until the transaction conditions are met. Finalization occurs either manually by the user or automatically after a pre-defined timer expires, preventing fund seizure by either party during a dispute.

Monero is utilized for its ring signature and stealth address technologies, which obfuscate the sender, receiver, and transaction amount on the blockchain. This prevents transaction graph analysis, unlike transparent ledgers such as Bitcoin.

Historical data indicates that vendor bonds are held in escrow to deter malicious behavior. These bonds are typically forfeited if the vendor violates market protocols. The bond amount acts as a barrier to entry to prevent spam accounts.

The Auto-Finalize timer is a smart contract-like script that releases escrowed funds to the vendor if the buyer takes no action within a specific window (typically 7-14 days) after the order is marked as shipped. This prevents funds from being locked indefinitely.

The network typically requires 10 confirmations on the Monero blockchain before crediting a wallet. With a block time of approximately 2 minutes, this process usually takes around 20 minutes. Users should monitor the transaction hash on a blockchain explorer.

CAPTCHA failures during high traffic are often due to session desynchronization. If the server response time exceeds the client's session timeout window, the CAPTCHA token becomes invalid before submission. Refreshing the identity or circuit usually resolves this.

Dispute resolution involves a moderator reviewing the transaction logs and communication history. The moderator has the cryptographic authority to sign a transaction releasing the funds to either the buyer or the vendor, depending on the evidence presented.