Anchor Protocol

VeilNet's next-generation transport layer — a post-quantum, multi-hop, self-healing protocol with WebRTC integration, reinforcement-learning routing, and automatic network forwarding for cloud-native systems.

VeilNet Anchor Protocol

The Anchor Protocol is VeilNet’s next-generation transport layer — a post-quantum, multi-hop, self-healing protocol purpose-built for cloud-native, distributed, and AI-driven systems. It replaces the static, tunnel-centric design of traditional VPNs with an adaptive, invisible, and intelligent networking fabric.

Post-Quantum Cryptography

Anchor uses Kyber KEM and Dilithium DSA to secure all communication without exposing plaintext headers, public keys, or endpoint metadata at any stage of negotiation or transmission. Nothing identifying leaves the device:

  • No plain handshake header
  • No exposed pub/priv key pairs
  • No observable metadata
  • No fingerprintable traffic patterns

Because all control and data are wrapped in post-quantum cryptography with no leaked metadata, Anchor traffic is effectively unobservable, resistant to surveillance, and secure against future quantum decryption.

Full WebRTC Integration

Anchor integrates WebRTC directly into its transport layer for zero-configuration connectivity across any environment. This includes ICE negotiation, STUN/TURN traversal, multiplexed data channels, and congestion-aware delivery.
Anchor can also aggregate multiple connections into a single high-availability link, providing:

  • Higher throughput
  • Lower latency
  • Instant failover
  • Path diversity for security

This makes Anchor extremely resilient and ideal for mobile, multi-cloud, or unstable network conditions.

Stream, Router and Tether — Layered and Shareable Resources

Anchor decomposes communication into three shareable components:

  • Streams — independent, encrypted data channels
  • Routers — local routing logic and path selection units
  • Tethers — persistent link abstractions used by routers and streams

This layered architecture enables Anchor to:

  • Provide one independent secure stream per destination, not a single shared tunnel
  • Optimise each stream individually based on conditions and RL feedback
  • Reuse routing structures without duplicating tunnel state
  • Expose all of the host’s networks automatically

Because each destination has its own independent stream and Anchor sits beneath the OS routing layer, VeilNet can automatically forward all networks attached to the host — LAN interfaces, containers, bridges, virtual networks — with zero sub-routers, no NAT chains, and no manual routing rules.

Reinforcement-Learning and Non-IP Routing

Anchor is not restricted to IP-address-based routing. It supports non-IP identifiers, enabling routing that is identity-driven rather than address-driven. A reinforcement-learning engine continuously evaluates:

  • Latency
  • Congestion
  • Link health
  • Hop stability
  • Historical performance
  • Path diversity

Routing then adapts instantly, improving performance and resilience without user intervention.

Native Multi-Hop Multi-Path

Anchor natively constructs multi-hop paths and multi-path flows without requiring mesh topology or pre-defined peer lists. Traffic can simultaneously:

  • Split across multiple paths
  • Recombine dynamically
  • Reroute around failures
  • Prefer faster or healthier hops

All of this happens transparently in the background.

Self-Recovery

When a node, hop, or network path becomes unstable, Anchor automatically:

  • Rebuilds the routing graph
  • Reassigns streams to new tethers
  • Migrates flows to healthier paths
  • Repairs links without interrupting active sessions

This ensures application-level stability even in heavily degraded environments.

Full MTU Size and Compatibility

Anchor supports full-size MTU transmission without fragmentation issues. Unlike legacy tunnels, Anchor aligns with:

  • VXLAN
  • Cilium
  • Kubernetes CNIs
  • Cloud overlay networks
  • Multi-layer virtualisation setups

This makes it universally compatible with modern infrastructure while maintaining optimal throughput.