ZERO SAAS COORDINATION • POST-QUANTUM MESH

Route through a mesh, not a company.

Your network shouldn't depend on another company's login page, central auth server, or closed control plane. Global Ghost Net is an autonomous Rust daemon linking servers, homelabs, and remote devices into a sovereign, erasure-sharded WAN tunnel with RAM-locked post-quantum encryption.

Zero Central Servers
Raw UDP beacons + self-seeded DNS
ML-KEM-512 + X25519
Quantum-resistant dual key exchange
RS(2,1) Multi-Path
Any 2 of 3 shards reconstruct payload
Hardware RAM Pinned
VirtualLock / mlock zero-swap paging

Why Engineers Choose Global Ghost Net

Built for teams and individuals who refuse to route infrastructure secrets through third-party SaaS coordinators or tolerate central points of failure.

HOMELAB & REMOTE ENGINEERS

Direct LAN-over-WAN Tunneling

Access your internal home subnets, hypervisors, and storage pools from cellular or untrusted hotel Wi-Fi. No port forwarding on your router, no exposing SSH or Web UIs to the public internet, and zero corporate telemetry.

Solution: Native SOCKS5 proxy or virtual TUN tunnel back to your home exit hub.
CLOUD & BARE-METAL ARCHITECTS

Zero-SaaS Node Interconnect

Interconnect multi-region VPS instances and off-site edge servers into a unified peer-to-peer fabric. Nodes discover one another via decentralized signed UDP beacons or custom DNS seeds with automated failover.

Solution: No third-party control plane. If our website goes down, your mesh never notices.
SECURITY PRACTITIONERS & PRIVACY ADVOCATES

Deep Packet Inspection Invariance

Adversaries intercepting internet links see only fixed-width 512-byte datagrams with random trailing jitter. Payloads are fragmented into RS(2,1) shards routed over divergent IP paths; single-path taps capture meaningless noise.

Solution: Harvest-Now-Decrypt-Later defense via lattice ML-KEM-512 + RAM locking.

Architected for Uncompromising Secrecy

Built from ground up in memory-safe Rust to resist adversary state machines, traffic correlation, and quantum factoring.

01 / CRYPTOGRAPHIC ENGINE

Dual-Layer Post-Quantum KEM

Handshakes simultaneously compute classical ECDH (X25519) and lattice-based ML-KEM-512. Session keys are derived through dual-phase HKDF-SHA256, rendering stored network traffic immune to future quantum decryption.

02 / PHYSICAL MEMORY ISOLATION

Locking Secrets in Physical RAM

Long-term private keys and ephemeral pre-shared keys are pinned into physical hardware memory via VirtualLock (Windows) and mlock (POSIX). Pages cannot leak to swap or crash dump files.

03 / TRAFFIC INVARIANCE

512-Byte Constant Sizing

All Global Tunnel Frames (GTF) are padded to uniform 512-byte boundaries with ChaCha20-Poly1305 AEAD and trailing cryptographically random jitter. Packet sniffers observe no packet length signatures.

04 / DISPATCH RESILIENCE

Adaptive Multi-Path Sharding

Payloads are encoded into Reed-Solomon RS(2,1) GF(256) shards and dynamically routed across disparate mesh paths. Dropped links recover without retransmission as long as two shards arrive.

05 / BYZANTINE TOLERANCE

Poisson Anomaly Isolation

Mesh nodes model incoming peer timing against expected Poisson arrival distributions. Misbehaving nodes injecting malformed PDUs or replaying counters are quarantined in real-time.

06 / IDENTITY ANCHORING

Ed25519 Cryptographic Trust

Nodes have no IP-based identity. Every peer is anchored to an Ed25519 public key fingerprint with issuer-signed cryptographic revocation lists. IP roaming preserves authenticated sessions.

Reed-Solomon RS(2,1) over GF(256)

Mathematical erasure coding running directly in your browser. Click any shard to drop it; observe the remaining two recover the exact payload.

Shard 0 • Data 1
Shard 1 • Data 2
Shard 2 • GF Parity
Reconstructed Payload (GF(256) Inversion)

Global Tunnel Frame (GTF) Wire Layout

Rigorous, fixed-width structure ensuring zero metadata leakage and constant-time parsing verification.

Offset (Bytes) Field Length Cryptographic / Functional Purpose
0x00 … 0x03 Session Token 4 Bytes Truncated session identifier, also mixed into the ChaCha20-Poly1305 AEAD nonce to eliminate cross-session collision.
0x04 … 0x07 Packet Counter 4 Bytes Monotonic sequence counter checked against an atomic sliding replay window. Duplicate or late datagrams are rejected in constant time.
0x08 … 0x08 Shard Index 1 Byte Reed-Solomon shard index: 0x00 (Data 0), 0x01 (Data 1), or 0x02 (GF(256) parity shard).
0x09 … 0x09 Control Flags 1 Byte Frame control flags: Bit 0 signals bulk 1472B frames, Bit 1 indicates unordered tunnel datagram routing.
0x0A … 0x1F3 Encrypted Shard 486 Bytes Ciphertext carrying the payload shard, encrypted with ChaCha20 authenticated encryption.
0x1F4 … 0x203 Poly1305 Tag 16 Bytes 128-bit Poly1305 MAC. A single altered bit across header and payload fails constant-time authentication.
0x204 … + Jitter Padding 0 – 64 Bytes Cryptographically random trailing noise injected per-packet to frustrate downstream statistical packet length correlation.

Deploying Nodes & Mobile Tunnels

No account creation, no certificates from third-party CAs. Run directly as a daemon or system service.

01 Install the Daemon

Compile from verified Rust source or download the signed static binary onto your exit hub and remote devices:

# Linux / macOS
curl -sSf https://ggn.kellersystems.dev/install.sh | sh

# Windows PowerShell
irm https://ggn.kellersystems.dev/install.ps1 | iex

02 Configure Mutual Pre-Shared Key (Optional Hardening)

Generate a 256-bit symmetric pre-shared key. When configured, handshakes will drop unauthorized peers before consuming handshake compute:

# Generate 32-byte hex secret
openssl rand -hex 32

# Set on all participating nodes
export GHOST_PSK=e7f9a204b18c...09df

03 Start Exit Hub (Home LAN)

Run the node on your home network to bridge traffic to the local subnet:

GHOST_BIND=0.0.0.0:2271 \
GHOST_EXIT_ALLOWLIST=<remote_peer_fingerprint> \
vantablack

Replace allowlist with any for open mesh routing among PSK holders. Port 2270 is reserved for UDP discovery beacons.

04 Connect Mobile Client / Laptop (LAN-over-WAN)

Connect from cellular or public Wi-Fi directly to your exit hub. All machine traffic routes through the encrypted post-quantum tunnel:

# Connect via SOCKS5 local proxy
GHOST_SOCKS5=1 GHOST_SEEDS=home.yourdomain.com:2271 vantablack

# Or enable full TUN interface routing (requires elevated privileges)
GHOST_ENABLE_TUN=1 GHOST_SEEDS=home.yourdomain.com:2271 vantablack