Reticulum is a cryptography-based networking stack for building local and wide-area networks with readily available hardware, designed to keep operating in adverse conditions with very high latency and extremely low bandwidth.[1] It is a complete stack: it does not rely on IP or higher layers, though IP can serve as an underlying carrier.[3] Found on the Hacker News front page in mid-August 2026 — a decentralized networking project with real momentum behind it.
Practically any medium that supports at least a half-duplex channel faster than 5 bits per second with a 500-byte MTU: data radios, modems, LoRa radios, serial lines, AX.25 TNCs, amateur radio digital modes, WiFi, Ethernet, and free-space optical links.[3]
The Reticulum Protocol was dedicated to the Public Domain in 2016.[3] There is no formal spec: the reference implementation is the final, authoritative specification, and the maintainer says no derived RFC or formal spec will ever exist.[3]
The current manual documents Reticulum Network Stack 1.4.2.[2] Around the core stack sits a grown ecosystem: LXMF (delay- and disruption-tolerant messaging), LXST (real-time audio), the Nomad Network off-grid mesh platform, the Sideband app for Android/Linux/macOS/Windows, MeshChatX, Reticulum Relay Chat, RetiBBS, and the rnsh remote-shell utility — plus a utility family (rnsd, rnstatus, rnid, rnpath, rnprobe, rncp, rngit, rnx, rnodeconf).[2]
GitHub's API reports 6,883 stars, 506 forks, last push 2026-07-26; the repo describes it as "the cryptography-based networking stack for building unstoppable networks with LoRa, Packet Radio, WiFi and everything in between."[5]
Reticulum's philosophy begins with "there is no cloud. There is only other people's computers."[4] The bet is that the scarce resource in a hostile environment is not bandwidth but trust — and that trust can be manufactured from mathematics instead of from infrastructure. Its governance stance ("reference implementation IS the spec") is an unusual choice worth watching as the mesh grows: the stack survives control not only technically but institutionally, because there is no document to capture, only code that outruns anyone who would intercept it.
[1] reticulum.network — Reticulum Network — landing
[2] reticulum.network/manual — Reticulum manual (index)
[3] github.com/markqvist/Reticulum — README (reference implementation)
[4] Zen of Reticulum — design notes
[5] api.github.com/repos/markqvist/Reticulum — repo metadata (live)