Access & Connectivity
How does the network process .onion routing?
The platform utilizes the Tor network's hidden service protocol. Traffic is encrypted through multiple relay nodes before reaching the destination server, ensuring complete structural anonymity for both the user and the host infrastructure.
What causes intermittent connection timeouts?
Connection interruptions generally stem from Distributed Denial of Service (DDoS) mitigations or routine backend synchronization. The platform load-balances across multiple verified archive addresses to maintain structural uptime.
Which browser configurations are necessary?
Access strictly requires the Tor Browser. To ensure maximum operational security, JavaScript must be disabled globally (Safest security level), as the interface is designed to function entirely without client-side scripts.
Are alternative routing networks like I2P supported?
Currently, analysis of the infrastructure indicates exclusive reliance on the Tor network (.onion V3 addresses). I2P integration has not been observed in the public routing tables.
Security Architecture
How does the architecture implement PGP for authentication?
Accounts can mandate Two-Factor Authentication (2FA). Upon login, the system encrypts a unique challenge string with the user's public key. The user must decrypt this locally and submit the raw string to proceed.
What is the procedure for cryptographic signature verification?
All internal communications and critical announcements are cryptographically signed by the administration's primary key. Users utilize local software (e.g., Kleopatra or GnuPG) to verify these signatures against the canonical public key archived in our database.
How are session variables managed by the host?
The platform enforces stateless, heavily encrypted session cookies that expire automatically upon inactivity or manual logout. No persistent identifying metrics are retained after the session ends.
Internal Functionality
How is the escrow mechanism structured?
Funds are held in a neutral, centralized smart-contract equivalent until the consumer finalizes the transaction. If a dispute arises, moderators review encrypted communications before arbitrarily releasing the ledger balance.
What defines the auto-finalize timetable?
Transactions automatically settle and release funds to the merchant after 14 days for physical transit and 48 hours for digital transit, assuming no dispute has been instantiated by the consumer.
How does the internal ledger process Monero (XMR)?
Monero is the primary processing pair. Deposits are isolated for each user, maintaining the inherent ring-signature and stealth-address obfuscation of the Monero blockchain.
What are the required blockchain confirmations for deposits?
The system requires 10 network confirmations on the Monero blockchain before a deposit is credited to the internal user interface, typically averaging 20 minutes.
How is a merchant bond initiated and held?
Distributors wishing to list goods must lock a specific USD-equivalent amount of cryptocurrency into a structural bond. This acts as collateral against deceptive practices and is non-refundable in the event of administrative termination.
Diagnostics & Troubleshooting
How are persistent CAPTCHA challenges resolved?
The clock skew on the local machine must be synchronized. Advanced DDoS protection layers will repeat the CAPTCHA if the connection latency is excessively high or if the Tor circuit is unstable.
What dictates the resolution of uncredited ledger balances?
Users must verify the transaction hash on a block explorer. If confirmations exceed the threshold but the balance remains null, a signed message containing the TXID must be submitted to the internal support mechanism.
Is account recovery possible if mnemonic data is lost?
No. The architecture generates a mandatory mnemonic seed phrase upon registration. If this phrase and the login credentials are lost, the account and associated ledger balances are cryptographically unrecoverable.
What variables cause withdrawal processing delays?
Withdrawals are processed in batches from a cold wallet to mitigate hot-wallet exposure. This security protocol can introduce a delay ranging from 30 minutes to 12 hours depending on queue volume.