Reticulum Guide
AlphaInteractive explainers that keep the Zen of Reticulum in mind: sovereign networks, destinations not addresses, encryption by default.
This guide is alpha. Steps, interactives, and wording may change and may not always be accurate. Prefer the official Reticulum manual and project docs when you need a definitive reference.
Zen and design goals
Why Reticulum exists: permissionless networks, medium agnosticism, and encryption by default.
Destinations, not addresses
How Reticulum names endpoints with 16-byte destination hashes and destination types.
Identities and keys
How a Reticulum identity becomes a portable cryptographic self you can take offline.
Announces and multi-hop paths
How public keys and reachability spread through signed announces, hop by hop.
Cryptography by default
Primitives and the identity-encryption flow used for private single-destination traffic.
Packets across hops
How encrypted packets move hop by hop, and why plain traffic stays local.
Links and sessions
How encrypted links turn a destination into a reliable session for requests and transfers.
Messaging and LXMF
How chat-style apps sit on Reticulum destinations, announces, paths, and encrypted delivery.
Interfaces and carriers
Reticulum rides any digital carrier. Learn what that means and what Reticulum-Go supports today.