VX6VX6

Documentation

Looking for app-development guidance? Start with the SDK and App Builder Guide.

Protocol Core

VX6 protocol/runtime components that power identity, discovery, service routing, and encrypted peer transport.

Identity and signed records

Each node holds a persistent cryptographic identity and publishes signed endpoint/service records.

DHT + registry discovery

Name and service lookups use DHT-backed keys plus local registry sync for fast repeated access.

Direct, relay, hidden, and localhost bridge flows

Connections can run direct peer-to-peer, through multi-hop relay paths, hidden alias routing, and localhost-to-localhost service bridging.

TCP + QUIC transport modes

VX6 supports transport selection via abstraction so operators can run either TCP or QUIC depending on environment and policy.

SDK and App Layer

How product teams build apps on top of VX6 without coupling protocol internals to frontend code.

Shared backend contract (`vx6d`)

A local backend service contract lets every UI team (desktop/mobile/web) call the same VX6 runtime API.

Desktop + mobile tracks

Tauri desktop is active and Android/iOS integrations are in progress over the same backend behavior.

Comms app architecture

VX6 Comms uses peer-first messaging/file/call workflows where local data ownership stays with users.

Independent UI contribution model

Frontend contributors can build by platform while backend maintainers keep protocol/runtime compatibility stable.

Operations and Enterprise

Operational controls needed for production usage, including release gating, policy routing, observability, and governance.

Stable release branch

A dedicated stable branch is intended for only validated merges with cross-platform and conformance gates.

SD-WAN adoption direction

VX6 can evolve into identity-driven branch overlay networking with policy routing and failover controls.

Observability and diagnostics

Operational posture includes runtime status, DHT visibility, relay health checks, and deployment guides for teams.

Cross-platform runtime management

Linux, Windows, and macOS operators can run aligned protocol behavior while mobile app layers continue to mature.