Tor Mode & Advanced Access (Coming Soon)

Nyxen.vip is accessible through both standard browsers and Tor. This dual-access architecture ensures that users can choose the level of anonymity and network trust appropriate for their context. This page explains how Nyxen interacts with Tor, what changes in onion mode, and how builders can configure it safely.

---

1. Access Layers Overview

Access Type	Domain	Description	Recommended Use
Clearnet	https://nyxen.vip	Standard HTTPS deployment via Cloudflare / AWS	Everyday use, normal latency
Onion Service	http://nyxenxyz12345.onion (placeholder)	Self-hosted Tor hidden service	High-sensitivity use, traffic obfuscation

[!NOTE] Both endpoints serve identical functionality. The only difference is the transport layer and routing visibility.

---

2. Architecture Diagram

[User (Clearnet)] → [TLS 1.3] → [Nyxen Relay (CDN Front)]  
[User (Tor)]      → [Onion Circuit] → [Nyxen Relay (Tor Bridge)]  

Both paths connect to the same logical backend, enforcing the same encryption, TTL, and burn rules.

---

3. Why Tor Integration Matters

• Some Nyxen users operate in network environments where metadata is the risk.

• Tor mode provides:

  • IP obfuscation through onion routing

  • DNS-level privacy

  • optional hidden service entry (no DNS records)

This allows Nyxen users to:

• access Dead Drops or Boards without visible endpoints

• coordinate in Capsules without clearnet traces

• separate operational footprints between different devices or teams

---

4. How Tor Mode Works

Dual-Entry Design

Nyxen’s backend relays can accept traffic from both TLS and Tor simultaneously. Sessions are logically isolated, meaning a Tor-originated Capsule never leaks to a clearnet route.

Simplified Flow

Tor Browser
   ↓
Tor Circuit
   ↓
Nyxen Onion Relay
   ↓
Encrypted Payload (AES-GCM)
   ↓
Nyxen Application Layer (no plaintext)

Every encryption rule remains identical; Tor simply adds an additional anonymizing network layer.

---

5. Operational Differences

Feature	Clearnet	Tor Mode
Latency	Low	Higher (multi-hop routing)
Reliability	Stable	Can fluctuate depending on Tor circuit health
Speed	Suitable for Spectre Voice	May impact live audio (packet delay)
Metadata Visibility	Minimal	None (no direct IP visibility)
TLS Termination	Standard	Inside onion circuit
Session Persistence	Normal	Isolated per Tor session

[!WARNING] Spectre Voice is not fully reliable over Tor due to bandwidth and latency limits. Text-based primitives (Dead Drops, Boards, Files) are unaffected.

---

6. Tor Mode Access Setup

Step 1 — Generate Onion Key

tor --service create nyxen_relay

Step 2 — Configure Hidden Service

In torrc:

HiddenServiceDir /var/lib/tor/nyxen/
HiddenServicePort 443 127.0.0.1:443

Step 3 — Deploy

Restart Tor to publish the .onion address. You’ll receive something like:

nyxenxyz12345.onion

Step 4 — Mirror API Endpoints

Serve the same REST and WebSocket endpoints from the onion relay as on clearnet.

Example:

Endpoint	Description
/api/capsule	Create capsules
/api/relay	Message relay
/api/burn	Burn context

---

7. Mixed Mode Usage

Users can mix clearnet and onion sessions under the same encryption domain.

Use Case	Behavior
Capsule created via Tor	Stays in Tor circuit; participants on clearnet must enter via onion mode.
Dead Drop on clearnet	Can invite Tor participants if relay policy allows mixed connections.
File Drops	Allowed in both, but Tor recommended for sensitive material.

[!TIP] Encourage critical operations (Spectre Voice, Capsules, File Drops) to remain mode-consistent (all-Tor or all-clearnet). Mixed sessions can increase metadata exposure.

---

8. User Experience in Tor

• Nyxen detects Tor user-agent headers and automatically:

  • disables analytics/tracking pixels

  • removes all external CDN calls

  • serves local versions of scripts and fonts

Visual Indicator: A faint violet “Onion Active” badge in the header when connected via .onion.

Tooltip:

“You’re in onion mode — routes are anonymized, TTL rules unchanged.”

---

9. Security Considerations

Benefits

✅ No IP visibility ✅ Resistant to DNS and routing surveillance ✅ Identical encryption and TTL guarantees

Limitations

⚠️ Slower connections, especially for large file transfers ⚠️ Spectre Voice unstable due to Tor latency ⚠️ Browser fingerprinting still possible at the endpoint

[!WARNING] Tor protects network identity, not endpoint integrity. If your device or browser is compromised, Nyxen cannot shield that activity.

---

10. Recommended Practices

Goal	Action
Maximum anonymity	Use Tor-only access and disposable devices.
Speed-sensitive ops	Use clearnet with VPN or trusted relay.
Critical coordination	Keep all peers in one network layer.
Redundancy	Run your own private Nyxen relay for internal ops.

---

11. Optional Tor Integration for Teams

Teams can self-host private onion relays connected to Nyxen’s public backbone.

Benefits:

• Internal segmentation

• Custom TTL policies

• Independent relay metrics

Example config snippet:

{
  "relay_mode": "private-onion",
  "ttl_policy": "strict",
  "burn_policy": "cascade",
  "trusted_keys": ["..."]
}

---

12. Visual Flow

[Tor Client] ───► [Onion Relay] ───► [Nyxen Relay Layer] ───► [End User]
                 (Hidden Service)     (No plaintext ever)

---

Tor Mode gives Nyxen users a second tunnel of privacy without changing how encryption, TTL, or burn work. Clearnet is faster. Onion is quieter. Both are equally encrypted, equally temporary, equally blind to their content.