Decent Network whitepaper
A readable product-level edition of the protocol thesis, architecture, trust model, and network roadmap.
July 2026Abstract
Decent Network proposes a self-organizing communication layer where endpoints own identity, establish relationships directly, discover reachable paths, and exchange encrypted traffic without requiring one application provider to own the network. Beagle and AgentNet are reference products built on this thesis.
Core primitives
| Primitive | Role |
|---|---|
| Identity | A locally controlled keypair and stable address for a person, agent, or device. |
| Friendship | Mutual consent that establishes a relationship and an initial trust boundary. |
| Discovery | DHT and supporting services locate current paths without changing the address. |
| Transport | Encrypted direct connections, LAN paths, relay fallback, offline delivery, and optional express routes. |
| Naming | Human-readable names that can resolve to portable identities. |
Reference architecture
- Endpoints generate and retain identity material.
- Bootstrap services help a new endpoint enter discovery.
- DHT records help peers find current reachability information.
- NAT traversal attempts direct sessions; relays provide a fallback.
- Express and regional exits are optional path services for performance or policy needs.
- Applications such as Beagle consume identity, relationship, messaging, and network capabilities.
Trust and security model
Self-sovereign identity removes the platform account as the root of trust, but it does not remove operational security. Users must protect endpoint keys, verify sensitive relationships, update software, restrict local consoles, and expose only intended services. Friendship grants a relationship, not unlimited administrative authority.
Infrastructure and future economics
The protocol design anticipates independently operated bootstrap, relay, express, naming, and exit services. Earlier whitepaper drafts explore incentives and token-gated service roles. The shipping products do not require a token today; operator economics and governance remain roadmap topics to validate after real network demand.
What exists now
- Beagle mobile messaging and identity experience.
- Beagle Desktop and AgentNet CLI/TUI for friends, messages, files, routes, exits, and diagnostics.
- Private 10.86.x.x networking, relay-capable reachability, and smart regional proxying.
- OpenClaw channel and TypeScript packages for agent and application integration.
This web edition is adapted from the Decent Network whitepaper, product documentation, AgentNet customer introduction, and company vision materials maintained in the DecentLAN and Decent HQ repositories.