PROTOCOL_MANUAL_V2

Network Access Protocol

A comprehensive technical guide for establishing a secure, encrypted connection to the Dark Matter infrastructure. This manual covers environment configuration, PGP key management, and ledger interaction.

01

Environment Configuration

Secure access begins with the correct software environment. The standard protocol requires the use of the Tor Browser to navigate the .onion hidden service network.

  • Download the official Tor Browser package.
  • Navigate to Settings > Privacy & Security.
  • Set the Security Level to Safer or Safest.
CRITICAL: Disabling JavaScript eliminates the majority of browser-based fingerprinting vectors and potential exploits.
02

Verify Connection Integrity

Network integrity is maintained by using only cryptographically signed verify-mirrors. Do not trust external indexes without validating the signature.

Verified Entry Node:
kb3qxip7bvh6rgfre7h7gcxth2bf7ezo5tubp3a5cdef2pboc3bpdtad.onion

Ensure the URL bar matches this address exactly. Character deviations indicate a compromised path (Man-in-the-Middle).

03

Identity Initialization

When initializing a new identity (account), strict adherence to OpSec protocols is required.

1. Credentials

Use a unique username and a randomly generated, high-entropy password. Never reuse credentials from clear-web services.

2. The Mnemonic

The system will generate a recovery mnemonic. Write this down on physical media (paper). It is the ONLY way to recover a lost account.

Immediately after initialization, navigate to user settings and enable 2-Factor Authentication (2FA) via PGP.

04

Cryptographic Encryption (PGP)

Plaintext communication is a security vulnerability. All sensitive data exchange must be encrypted using PGP (Pretty Good Privacy).

  1. Generate a 4096-bit RSA Key pair locally (e.g., using GPA or Kleopatra).
  2. Import the Market's Public Key into your keyring.
  3. Upload your Public Key to your user profile settings.
PROTOCOL: Before sending sensitive data (such as shipping coordinates), encrypt the message using the recipient's Public Key. This ensures only the intended recipient can decrypt the information.
05

Ledger Interaction (XMR)

The infrastructure relies on cryptocurrency ledgers for value transfer. While Bitcoin (BTC) is supported, Monero (XMR) is the recommended standard due to RingCT (Ring Confidential Transactions) and stealth addresses.

Deposit Protocol

Generate a unique deposit address within the wallet tab. Send funds and wait for the required network confirmations (usually 10 blocks for XMR).

06

Transaction & Escrow Logic

Interactions between identities (Merchants and Users) are governed by an Escrow Smart Contract or logic layer.

  • Reputation Analysis: Verify the historical metrics and trust level of the Merchant identity before initiating an agreement.
  • Escrow Hold: Funds are held by the system, not the merchant.
  • Finalization: Only release funds (finalize) once the physical or digital goods have been successfully received and verified.
WARNING: "Finalizing Early" (FE) bypasses the escrow protection. Only utilize FE protocols with Merchants possessing established, high-trust metrics.