Introduction

Communication with this hub follows strict operational security protocols. There is no phone number, no physical office, and no real-time chat support. These absences are intentional. To minimize exposure, all inquiries go through encrypted channels or asynchronous email. Keep your messages concise and relevant to the mirror links or site functionality.

PGP

For sensitive topics or technical feedback, use PGP encryption. The public key required for encrypting your messages is available on the mirrors page. Do not expect a dedicated key for every minor query, but if you are reporting a broken link or a security concern, encryption is recommended. Ensure your message body includes a clear subject line so the operator can prioritize it among other technical tasks.

Email

An email address is provided for general questions. However, do not expect instant replies. The average response time ranges from one to three days. This delay is part of the workflow. Messages are processed in batches to maintain consistency in how issues are handled. If your question is urgent, consider checking the mirrors page first to see if the issue has already been resolved.

What not to send

  • Do not send your seed phrase, private keys, or recovery codes.
  • Do not attach screenshots showing your balance or transaction IDs unless necessary for a specific bug report.
  • Avoid writing to market vendors that "this is the official site." This hub manages the mirrors, not the vendor relationships.

Sending personal financial data increases your risk profile without helping the operator fix a technical issue.

Response time

Expect a reply within one to three business days. Not every question receives an answer. Minor typos or duplicate reports may be acknowledged briefly or ignored if the fix is already deployed. The priority is maintaining the integrity of the mirror list. Patience is part of dealing with any independent darknet resource.