Research & FAQ Database

It operates as a decentralized hidden service on the Tor network utilizing onion routing to encrypt and anonymize network traffic. The infrastructure is designed to mitigate external surveillance through multi-layered encryption protocols inherent to the Tor environment.

It encrypts network traffic through multiple relays globally, masking the origin IP address of the participant interacting with the infrastructure. Each node in the circuit only knows the preceding and succeeding nodes, ensuring end-to-end obfuscation.

Nodes frequently undergo maintenance or experience automated DDoS mitigation protocols. During these events, primary relays may drop connections, requiring participants to utilize cryptographically signed failover nodes to maintain connectivity with the main database.

Only specialized browsers configured for the Tor network can resolve .onion addresses and handle the cryptographic handshake required. Standard clearnet browsers cannot route traffic to hidden services by design.

Participants use Pretty Good Privacy (PGP) cryptographic keys to decrypt dual-factor challenge messages, verifying their identity cryptographically. This ensures that even if credentials are intercepted, the account remains secure without the corresponding private key.

2FA adds an architectural layer requiring a decrypted PGP token alongside standard authentication credentials. This implementation severely limits unauthorized access vectors by requiring physical access to the user's local PGP keychain.

PGP signed messages from recognized administrative keys validate the cryptographic signature of the node. Participants verify these signatures locally to ensure they are communicating with genuine infrastructure, preventing interception by malicious third-party nodes.

Funds are held in a multi-signature smart contract until the transaction is finalized by both participants or a cryptographic dispute is resolved. This eliminates the need for preemptive trust between distributing entities and receiving elements.

The infrastructure primarily routes transactions via Monero (XMR) due to its inherent ring-signature privacy features, and Bitcoin (BTC). All internal transactions run through automated mixing processes to obscure chain analysis attempts.

Participants generate unique, single-use wallet addresses for each transaction. Reusing addresses is systemically discouraged by the platform's architecture to preserve anonymity and prevent blockchain heuristics from mapping entity clusters.

Distributing entities must deposit a refundable cryptographic bond to establish trust, deter sybil attacks, and provide a penalty mechanism for protocol violations. This bond is held in cold storage for the duration of the entity's operational lifecycle.

Escrow contracts automatically release held funds after a predetermined timeframe (e.g., 7 to 14 days) if no dispute is raised by the receiving participant. This ensures network liquidity is maintained without manual intervention.

Algorithmic captchas prevent automated botnets from exhausting server resources. They function as the primary layer of DDoS mitigation, dynamically adjusting in complexity based on current node load and traffic patterns.

Participants experiencing looped captchas must refresh their Tor circuit to obtain a new exit node. Furthermore, ensuring JavaScript execution is completely disabled is required for proper visual rendering of the security images.

A unique mnemonic phrase generated during registration is the sole method for account restoration. Architectural parameters prevent administrative entities from resetting passwords manually, preserving zero-knowledge access principles.