Research & Technical FAQ

Accessing the network requires the Tor browser or an equivalent onion-routing protocol. Standard web browsers cannot resolve the native .onion addresses used by the infrastructure.

Extended downtime or connection timeouts usually indicate active DDoS mitigation. The network employs rotating mirrors to distribute traffic load when primary nodes face congestion.

The platform architecture requires users to disable JavaScript for maximum OpSec. The interface is designed to function entirely purely server-side to prevent client-side vulnerabilities.

To manage server load, the infrastructure limits active sessions. Idle connections are forcefully terminated after a predefined period of inactivity, requiring re-authentication.

Pretty Good Privacy (PGP) is implemented for end-to-end encryption of communications and for verifying the cryptographic signatures of release messages and node addresses.

The primary 2FA method requires users to decrypt a PGP message encrypted with their public key. This proves the user holds the corresponding private key before granting account access.

The platform enforces mandatory PGP encryption for all sensitive data exchanges. Messages must be encrypted locally before being transmitted through the internal messaging system.

Administrators sign all communications and mirror lists with a known public key. Researchers must cross-reference these signatures against historical records to independently verify authenticity.

Upon registration, the system generates a unique mnemonic phrase. This phrase is the sole cryptographic mechanism for account recovery and must be stored in an isolated, secure environment.

The platform operates exclusively on the Monero (XMR) blockchain to ensure transaction privacy. Bitcoin (BTC) is not supported due to its transparent ledger mechanics.

The escrow protocol holds funds in a neutral address until both transacting parties mutually finalize the agreement, ensuring neither party controls the assets during transit.

To mitigate network spam, establishing a merchant presence requires locking a specific amount of XMR. This bond acts as a security deposit and remains locked for the duration of the account's active status.

Transactions feature an automated countdown timer. If neither party initiates a dispute within this window, the smart contract automatically releases the escrowed funds to the recipient.

The internal exchange rate aggregator syncs with major privacy coin indices every few minutes. All deposits are credited based on the exact time the transaction achieves network confirmation.

Captcha failures frequently occur due to clock synchronization issues within the Tor network or expired session tokens. Refreshing the identity circuit often resolves localized routing anomalies.

The network requires a minimum of 10 confirmations on the Monero blockchain before crediting an account. Network congestion can delay block propagation, extending wait times.

If a 2FA challenge is interrupted, the system locks the session temporarily. Users must wait for the current challenge block to expire before requesting a new encrypted packet.

Mnemonic phrases are strictly case-sensitive and must maintain exact spacing. The recovery protocol will reject any string that does not perfectly match the original generated cryptographic seed.