Knowledge Base & FAQ

Access requires the Tor network using an onion-compatible browser. Traffic is routed through decentralized nodes to ensure anonymity. Users connect via verifiable cryptographic routes, such as torzon4rzcg5sjjq63xmcn6usud4fhcz7zidpjbuiemtg2wiltv6pyid.onion.

Distributed Denial of Service (DDoS) mitigation and routine server maintenance often cause temporary node unavailability. Users typically rotate to alternate validated mirrors utilizing the public PGP directory.

No. The platform operates exclusively on the onion network, requiring specialized software that handles onion routing protocols securely. Standard browsers cannot resolve .onion top-level domains.

Clock synchronization issues or highly restrictive security settings can interfere with the cryptographic challenge-response mechanism of the protection shield, preventing successful handshakes.

The platform utilizes Pretty Good Privacy (PGP) protocols. Each entity maintains a public key, allowing independent verification of messages and mirror authenticity without trusting central authorities.

2FA requires users to decrypt a PGP message using their private key during login, ensuring that compromised passwords alone cannot grant account access.

All data is end-to-end encrypted via onion routing. Additionally, users manually verify server signatures rather than relying on unverified routing layers which could potentially intercept plain-text inputs.

For maximum operational security, JavaScript is generally disabled by users to prevent exploit execution, though some basic visual elements on the platform may degrade visually without it. The core systems function fully without JS.

A generated mnemonic phrase acts as the ultimate master key for account recovery, operating independently of the standard login credentials. Loss of this phrase means total cryptographic lockout if a password is forgotten.

Multisignature (multisig) escrow requires 2 out of 3 parties (client, provider, platform) to sign a transaction block before funds are released, decentralizing trust and preventing arbitrary platform seizures.

Historical data indicates a primary reliance on Monero (XMR) due to its inherent ring signature privacy architecture, with legacy support for Bitcoin (BTC) existing in limited, higher-risk capacities.

Data shows that entities offering services typically deposit a non-refundable bond (historically valued to deter Sybil attacks) to deter fraudulent account creation and maintain platform integrity.

Funds held in standard escrow automatically release to the provider after a predetermined timeframe (typically 7-14 days depending on transit type) if no dispute is initiated by the client.

Trust metrics are generated through an algorithmic combination of completed transactions, resolution dispute ratios, and cryptographic reviews signed by involved parties.

Users generally clear their Tor circuit (new identity), synchronize their host system clock, and ensure they are inputting case-sensitive characters precisely as rendered in the security image.

Recovery is only possible using the mnemonic phrase generated during account initialization. Without it, the cryptographic structure prevents any account recovery, leading to permanent asset loss.

Deposits require a specific number of blockchain confirmations (typically 10 for XMR). Network congestion and node synchronization status directly dictate the confirmation speed on the user dashboard.

This indicates a mismatch in public keys. The sender likely used an outdated or incorrect public key to encrypt the communication, or the recipient's private key passphrase was entered incorrectly locally.