Knowledge Base
SYSTEM PROTOCOLS | SECURITY OPERATIONS | PLATFORM MECHANICS
Last Updated: Current Cycle
Infrastructure & Access
DrugHub operates as a decentralized V3 Onion Service on the Tor network. We utilize a distributed load-balancing system where users are routed through varying entry nodes to mitigate DDoS attacks and prevent traffic correlation. This hub acts as the verified directory for these nodes, ensuring you always have a cryptographic path to the market core.
Verification is mandatory for OpSec. Every legitimate mirror will display a PGP-signed message in the footer or a dedicated /verify endpoint.
- Import the DrugHub Official Public Key (0xF45A...) into your GPG keyring.
- Copy the signed message from the mirror.
- Run
gpg --verifyto confirm the signature matches the market key.
Never enter credentials on a mirror that fails signature verification.
While many legacy markets disable JS entirely, DrugHub uses sanitized, minimal JavaScript for essential cryptographic operations (client-side encryption) and dynamic UI loading. Our scripts are non-obfuscated and audit-friendly. Users with "Safest" Tor settings may experience limited functionality. We recommend "Safer" for the optimal balance of functionality and security.
Account Security Protocol
We have eliminated the "username/password" paradigm to prevent credential stuffing attacks.
- Registration: You provide a PGP Public Key.
- Login: The server encrypts a random nonce (token) with your Public Key.
- Decryption: You decrypt this token with your Private Key and paste it back.
Funds for orders are generated into a multisignature wallet associated with three keys: Buyer, Vendor, and Market. Moving funds requires 2 of 3 signatures.
Scenario A (Success): Buyer + Vendor sign to release funds upon delivery.
Scenario B (Dispute): Buyer + Market sign to refund buyer, OR Vendor + Market sign to release to vendor.
This system prevents exit scams, as the market administrator cannot seize funds without a second signature.
Scenario A (Success): Buyer + Vendor sign to release funds upon delivery.
Scenario B (Dispute): Buyer + Market sign to refund buyer, OR Vendor + Market sign to release to vendor.
This system prevents exit scams, as the market administrator cannot seize funds without a second signature.
Monero & Settlement
Bitcoin (BTC) is a transparent ledger; transaction history is public and traceable by chain analysis firms. Monero (XMR) forces privacy by default using Ring Signatures (hides sender), RingCT (hides amount), and Stealth Addresses (hides receiver). To protect our vendors and buyers from correlation analysis, we enforce XMR exclusivity.
To mitigate server-side risk, the market hot wallet holds minimal funds. The majority of assets are moved to offline Cold Storage. Consequently, withdrawals are not instant. They are processed in batches every 6-12 hours manually by staff. This time delay serves as a security buffer against automated exploit attempts.
Vendor Bond: A deposit of 1-5 XMR required to sell. This prevents "sybil" spam attacks and ensures vendor commitment.
FE (Finalize Early): A privilege granted to trusted vendors allowing funds to be released upon dispatch rather than delivery. Only vendors with 500+ sales and 98% positive feedback are eligible for FE status.
FE (Finalize Early): A privilege granted to trusted vendors allowing funds to be released upon dispatch rather than delivery. Only vendors with 500+ sales and 98% positive feedback are eligible for FE status.
Upon reaching Level 2 Buyer status, users are assigned a private .onion URL. This URL is unique to the user account. This isolates the user from public DDoS attacks targeting the main entry nodes and provides a high-speed, low-latency lane for established customers.
QUICK ACTIONS
VERIFIED ENTRY NODES
LIVE
ayi5yaxkvbruvseypnjrw3a5k3anjntipprqvwyfexhvxkls6npspnqd.onion
gkdr5qyuw2hmdfrfm5h4sqzzdapaj46jqpwvxmq35k5yz74zoxyjgaid.onion
hleq4ya7g6jsyddutgxoiro62mqnyzczytnrhw2gcfdpu4b3jjhgsbid.onion
ls67yymi67wqfz2jrbiwpoz2eltxk3duobxoc4633hzcalyy3nnsyoad.onion
umfeo6dediv4div2o7xi4k5zzl6sc22rtxh36jhnykykbhqatidegjqd.onion
Copy/paste into Tor Browser. Verify signature.
OpSec Protocol
Always disable WebGL and verify PGP signatures. Never communicate outside the market encryption. Use Monero for all financial settlements.
PGP Key:
VERIFIED
SYSTEM TAGS
#Monero_XMR
#MultiSig
#PGP_2FA
#Vendor_Bond
#Cold_Storage
#Tor_V3