> Knowledge Base & FAQ

Onion routing provides anonymous communication by encrypting data and transmitting it through multiple decentralized relays. This architecture obscures the IP addresses of both the client and the hosting server, ensuring privacy-by-design.

Distributed denial-of-service (DDoS) attacks and scheduled maintenance routines regularly cause temporary unavailability. The architecture relies on rotating .onion addresses to distribute load and mitigate targeted traffic floods.

The Tor Browser is explicitly required to resolve .onion addresses. This software utilizes modified configurations designed to prevent fingerprinting, isolate cookies, and disable potentially compromising scripts by default.

Advanced load balancing and anti-DDoS challenge screens mitigate high traffic volumes. These challenges must be cryptographically solved or visually deciphered before backend access is granted, shielding the core databases.

Pretty Good Privacy (PGP) utilizes public-key cryptography to authenticate messages. Users verify the digital signature of provided data against known historical public keys to ensure the integrity of the communication and rule out interception.

The 2FA protocol requires a client to decrypt a randomly generated challenge message using their associated private key before session initiation is permitted, ensuring robust identity verification beyond standard passwords.

The operational standard dictates that all sensitive data must be encrypted client-side using the recipient's public PGP key prior to any transmission, rendering the data unreadable to intermediaries or platform hosts.

Short-lived session tokens, strict IP binding to Tor nodes, and enforced automatic timeouts are employed to prevent unauthorized session hijacking during network operations.

Escrow holds cryptocurrency deposits in an isolated state until the transaction parameters are fulfilled. Only after mutual confirmation is the digital asset disbursed to the designated recipient.

The platform predominantly utilizes Monero (XMR) due to its inherent privacy-centric ring signatures. Bitcoin (BTC) is also utilized, typically requiring external mixing protocols for equivalent obfuscation.

Historical data indicates a mandatory cryptocurrency bond is locked upon account creation for providers. This acts as a financial deterrent against malicious behavior and is governed by strict platform rules.

If a client does not manually release escrow within a predefined timeframe (e.g., 7 to 14 days), the system automatically finalizes the state and disburses the funds, preventing asset lockup.

Certain transaction models leverage 2-of-3 multi-signature addresses, requiring cryptographic cooperation between the client, the provider, and a platform arbiter to authorize the movement of funds.

Clock synchronization issues or aggressive node cycling can cause validation to fail. Re-establishing a new circuit and ensuring precise system time synchronization typically resolves these anomalies.

A predefined mnemonic seed phrase, uniquely generated during initial registration, serves as the sole cryptographic method for resetting access credentials. Administrative recovery bypasses do not exist.

Blockchain network congestion and the required number of confirmation blocks dictate deposit visibility. Monero deposits typically require 10 network confirmations before synchronization with internal platform ledgers.