Roadmap

From single-use drops to a full ephemeral communications network.

Nyxen will ship in three phases. Each phase is scoped around implementable, verifiable milestones, moving from simple primitives → hardened infrastructure → distributed privacy network.

---

Phase I — Core Ephemeral Stack

Goal: Prove Nyxen’s model with a minimal, reliable, production-ready core. Focus: Things we can build and ship fast without exotic infrastructure.

Deliverables

1. Nyxen.vip Web & App

   • Landing page, docs, and dapp shell

   • Direct access to all core utilities

   • No accounts, no tracking

2. Dead Drops (v1)

   • Key-based ephemeral rooms

   • Client-side AES-GCM encryption

   • Fixed TTL selection + manual burn

   • Small group support, minimal UI

3. Secure Links (v1)

   • One-time / few-time encrypted notes

   • Link + TTL + view limit

   • Auto-burn on consumption or expiry

4. File Drops (v1)

   • Client-side encrypted small file transfer

   • Single-download or low-count

   • Tight TTLs, enforced deletion

5. Ephemeral Boards (v1)

   • Simple shared note surfaces

   • Basic list/section layout

   • Bound to TTL and burn events

6. Signals & Ghost Codes (v1)

   • Lightweight in-context signals (READY, BURN, etc.)

   • Local codebook-based Ghost Codes

   • No history, seconds-level TTL

7. Capsules (v1)

   • Group Dead Drops, Boards, and Drops under one TTL

   • Single key, single burn action

   • UI clearly scoped per Capsule

8. Relay & TTL Engine (v1)

   • Single-region relay cluster

   • Strict TTL enforcement + purge

   • No plaintext, minimal metadata

9. Token Integration (v1)

   • Read-only $NYXEN balance checks

   • Basic rate-limit tiers (free vs holder)

   • No staking, no complex mechanics

10. Security & Docs

    • Public smart contract verification

    • Initial threat model, problem/solution, comparison docs

Outcome: Nyxen is live, usable, and aligned with its doctrine: encrypted, ephemeral, no archives.

---

Phase II — Advanced Privacy Infrastructure

Goal: Harden Nyxen into serious operational infrastructure and introduce more complex primitives. Focus: Tor, APIs, self-hosting, more nuanced features that require stronger engineering.

Deliverables

1. Tor / Onion Access (Production)

   • Official .onion endpoint for Nyxen

   • Full functional parity with nyxen.vip

   • No external CDNs in onion mode

2. Capsules (v2)

   • Better internal linking between components

   • Context-aware UI (incident capsules, deal capsules, etc.)

   • Advanced burn policies (auto-burn on inactivity, etc.)

3. Ephemeral Boards (v2)

   • Real-time encrypted collaboration

   • Simple role controls (who can burn / edit)

   • Better visual structure for operational use

4. Relay Federation (v1)

   • Support for multiple relays (regions)

   • Encrypted relay-to-relay forwarding

   • Operator-level metrics without content visibility

5. Developer API & SDK (v1)

   • Limited, well-documented REST/WS

   • For integrating Drops, Links, Capsules into:

     • internal dashboards

     • SOC tools

     • incident response platforms

6. Token Utility (v2)

   • Tiered access mapped cleanly:

     • higher daily actions

     • priority relay routing

     • access to Capsules & advanced tools

   • Still no speculation framing; pure functional gating

7. Audit & Verification

   • First external review of:

     • relay logic

     • TTL enforcement

     • key handling

   • Publish hashes + methods in Legal & Transparency

Outcome: Nyxen matures from “MVP privacy tool” to infrastructure-grade ephemeral layer fit for teams, desks, and security orgs.

---

Phase III — Network-Grade Nyxen

Goal: Turn Nyxen into a distributed, verifiable, high-assurance privacy network. Focus: Harder R&D-heavy features: Spectre Voice, self-hosted relays, PQ options, governance over infra (not money), advanced capsules.

Deliverables

1. Spectre Voice (Stable)

   • Encrypted, time-bound voice sessions

   • Clean integration into Capsules and Drops

   • Voice distortion profiles (where legal)

   • Hard duration caps, no recordings

2. Self-Hosted Relays

   • Packages for organizations to run:

     • Private Nyxen relays

     • With same TTL/burn guarantees

   • Optional peering with public network

3. Onion-Only & High-Security Modes

   • Capsules restricted to Tor-only

   • Policies: high paranoia, stricter TTLs, enforced split-key

4. Advanced Cryptography

   • Hybrid PQ key exchange (research-based)

   • Hardware-backed keys (WebAuthn / secure enclaves)

   • Stronger key attestations for enterprise use

5. Transparency & Integrity Ledger

   • On-chain anchoring of:

     • build hashes

     • relay binaries

     • audit reports

   • Public verification guidelines

6. Ecosystem Integrations

   • Plugins / SDKs for:

     • SOC platforms

     • legal/compliance tools (for lawful ephemeral lanes)

     • privacy-oriented browsers / OS environments

7. Extended Governance (Non-financial)

   • Framework for:

     • relay operator standards

     • protocol change proposals

   • No token-voting; based on cryptographic + operational proofs

Outcome: Nyxen evolves into a modular privacy fabric: a network where serious users, teams, and infrastructures can rely on time-bound, verifiable, zero-archive communication.