WTF is Reticulum? A Plain-English Overview
This is Part 1 of a 12-part series on building private, resilient communication networks with Reticulum, LoRa, and associated tools.
The Problem
Every message you send — text, email, Signal, whatever — travels through infrastructure you don't own or control. Cell towers, ISPs, cloud servers, DNS resolvers. Every one of those is a chokepoint where your communication can be monitored, throttled, censored, or simply switched off.
What if you could build your own network? One that works over radio, WiFi, the internet, serial cables, or literally anything that can carry data — with strong encryption baked in from the ground up?
That's Reticulum.
What Reticulum Actually Is
Reticulum is a cryptography-based networking stack. Think of it as a replacement for TCP/IP that was designed from scratch with different priorities:
- Encryption is mandatory, not optional. Every packet is encrypted using ephemeral keys. There's no plaintext mode.
- No addresses to manage. There are no IP addresses, no DHCP, no subnets. Nodes generate their own cryptographic identities, and those identities are the addresses.
- Transport-agnostic. Reticulum doesn't care what carries the data. LoRa radio at 300 bits per second? Fine. Gigabit ethernet? Also fine. Both at the same time, bridged together? Absolutely.
- No infrastructure required. No servers, no sign-ups, no accounts, no service providers. Two devices running Reticulum on the same WiFi network will automatically discover each other and communicate.
- Sender anonymity by default. Packets don't include a source address. An observer can see where a packet is going, but not where it came from.
Reticulum works with as little as 5 bits per second of throughput and a 500-byte packet size. It's been designed to function over the worst links imaginable.
The Ecosystem
Reticulum is the networking layer. On top of it, several applications provide actual user-facing functionality:
| Component | What It Does |
|---|---|
| Reticulum | The core networking stack. Handles encryption, routing, transport. |
| LXMF | Lightweight Extensible Message Format. A messaging protocol built on Reticulum. Think of it as "email for mesh networks." |
| NomadNet | A terminal-based client for messaging and hosting decentralized pages (like tiny websites) over Reticulum. |
| Sideband | A graphical LXMF messaging app for Android, Linux, and macOS. The easiest way to send encrypted messages. |
| MeshChat | A browser-based Reticulum chat client. Lowest barrier to entry for new users. |
| RNode | An open hardware platform that turns cheap ESP32 LoRa boards into radio modems for Reticulum. |
| rnodeconf | The utility for flashing and configuring RNode firmware on supported hardware. |
You don't need all of these. You can start with just Reticulum and one messaging app, and add hardware later.
How It Compares
Reticulum vs. Traditional Networking (TCP/IP)
| TCP/IP | Reticulum | |
|---|---|---|
| Addressing | Centrally managed IP addresses | Self-generated cryptographic hashes |
| Encryption | Optional (TLS, etc.) | Mandatory on every packet |
| Infrastructure | Requires routers, DHCP, DNS | Zero configuration needed |
| Sender identity | Visible in every packet | Anonymous by default |
| Minimum bandwidth | Needs kbps+ to function | Works at 5 bits per second |
Reticulum vs. Meshtastic
Both use LoRa radios for off-grid communication, but they're fundamentally different:
| Meshtastic | Reticulum | |
|---|---|---|
| Ease of setup | Very easy — flash and go | More configuration required |
| Encryption | Added later, configurable | Core design, always on |
| Transport media | LoRa only | LoRa, WiFi, Ethernet, TCP, I2P, serial, anything |
| Network scale | ~100 devices practical limit | Designed for much larger networks |
| Routing | Simple flood/rebroadcast | Cryptographic multi-hop transport with path discovery |
| Applications | Built-in messaging | Extensible — messaging, file transfer, remote execution, web hosting |
Meshtastic is great for "buy a radio, start chatting." Reticulum is for building actual networks that can span different media and scale.
When Would You Use Reticulum?
- Privacy: You want communication that can't be surveilled, even by the network infrastructure itself.
- Off-grid communication: You need to communicate where there's no cell service or internet.
- Censorship resistance: You're in an environment where communication is monitored or restricted.
- Disaster preparedness: You want a communication system that works when infrastructure fails.
- Community mesh networking: You want to build a local network owned by the people who use it.
- Decentralized services: You want to host content or services without relying on cloud providers.
Key Concepts You'll Need
Before diving into the hands-on guides, here are the terms that will keep coming up:
- Destination: Reticulum's equivalent of an address. It's a hash derived from a node's public key. No two are alike, and no central authority assigns them.
- Announce: How a destination tells the network it exists. Like saying "I'm here, and here's my public key."
- Transport Node: A Reticulum instance configured to relay traffic for others. Like a router, but any node can become one.
- Interface: A configured communication channel — could be a LoRa radio, a TCP connection, a serial port, or local WiFi.
- Identity: A cryptographic keypair that represents an entity on the network. One identity can have multiple destinations.
- Link: An encrypted session between two destinations, established via a Diffie-Hellman key exchange.
What's Next
In the next guide, we'll install Reticulum on your computer, connect to the public testnet, and verify that everything works — no hardware required.
Next: [Part 2 — Your First Reticulum Install (Software Only, No Hardware)]