Introduction

What is VeilNet Conflux?

VeilNet Conflux is the connector/client/server/peer/node of the VeilNet network.
It is the software that runs on your device—whether as a system service, desktop/mobile application, or container—to join and participate in the VeilNet overlay.

Why the name Conflux?

Conflux behaves very differently from connector software in conventional overlay networks:

No Coordination Server

VeilNet has no central coordination server.
Conflux instances must self-organize, cooperate, and discover routes dynamically.
They are not passive clients waiting for updates—they are active agents contributing to the global network fabric.

Not WireGuard

Conflux is not a wrapper around WireGuard.
It is a completely new protocol and architecture designed for security, scalability, and cloud-native elasticity.

• On Windows, Conflux uses wintun to create a TUN interface.
• On Linux/macOS, it creates native kernel TUN interfaces.
• Its transport, encryption, routing, discovery, and identity logic are entirely original, not dependent on WireGuard semantics.

Horizontally Scalable

Conflux scales naturally in Kubernetes and distributed systems.

Because VeilNet is a non-IP network, Conflux:

• does not modify host routing tables
• does not require subrouters
• treats IP addresses as compatibility surfaces, not as core identity

Horizontal scaling simply means: add more Conflux instances → more capacity.

Native Multi-Hop & Multi-Path

Conflux instances automatically form multi-hop, multi-path, multi-channel routes using VeilNet’s reinforcement-learning routing algorithm.

Conflux can:

• discover optimal paths
• avoid congestion and unstable links
• use other nodes as intelligent jump-off points
• bypass restrictive networks

(It can be abused if misused—one reason the Anchor Protocol is not open-sourced yet.)

Why Conflux?

Because it is neither a “peer” nor a “client,” and not merely a connector—it is a junction of multiple realms, bridging distributed compute, networks, and identities.
Inspired by D&D, the name reflects how Conflux brings together independent islands of networks into one fabric.

How does it work?

Conflux establishes ephemeral data channels through three independent layers:

1. Stream – independent logical streams to each destination
2. Route – dynamic, intelligent route selection
3. Tether – underlying transport binding (WebRTC, QUIC, etc.)

Each layer is:

• independent
• shareable between streams
• hot-swappable during transmission

A stream can change its route or tether at any moment, as long as the destination can be reached.

These combinations become the actions of the reinforcement-learning (RL) algorithm:

• State = queue conditions, existing channels, link quality, congestion, historical performance
• Policy = the learned strategy for selecting stream/route/tether combinations
• Reward = successful, timely delivery of data
• Environment = the network topology, live node performance, and channel feedback

Conflux continuously executes this RL loop to optimise routing:

This is how VeilNet achieves:

• autonomous route construction
• congestion avoidance
• path recovery & self-healing
• efficient multi-hop multi-path routing
• dynamic, intelligent link selection without human configuration

In essence: every Conflux node is an intelligent router, not a passive client.