The Internet, Reinvented.

Overview

Reticulum is a hardware‑agnostic networking stack — a full network layer — that treats radios, Wi‑Fi, Ethernet, serial links, etc., as interchangeable interfaces. It focuses on cryptographic identity, privacy, and efficient routing rather than being a single radio protocol.

Key properties

• Identity-by-cryptography: each device generates a crypto identity and addresses are derived from that identity.
• Encryption-by-default and origin‑obscuring design.
• Route discovery with link quality measurement.
• Transport-agnostic: the same Reticulum network can span very slow links (e.g., Morse) to fiber and route large transfers over fast links.

How Reticulum differs from simple radio meshes

• Explicit routing rather than flooding:
  • Packets follow established routes instead of being replicated everywhere; overhead scales roughly linearly with hops.
• Transport-agnostic:
  • A single Reticulum network can include diverse link types and route traffic over the most appropriate interface.
• Cryptographic and privacy focus:
  • Designed for cryptographic completeness and privacy, not just terminating link encryption on each device.

Hardware, builds, and client software demonstrated

Example R-node (Arnode) build

• T‑Beam (LoRa/“Laura”) radio board, Adafruit NeoPixel, small OLED, 3D‑printed case, long‑range antenna.
• Firmware was flashed and modified; the presenter used an IDE to tweak and build for a custom board.
• Cosmetic faceplates (e.g., TC4 titanium) used as design flourishes.

Interfaces and bridging examples

• LoRa peers (sub‑GHz “Laura”) operating without internet.
• Wi‑Fi interfaces: Raspberry Pi / Haven nodes running OpenMANET/OpenWRT and the Morris Micro Wi‑Fi Halo (Morse Micro 802.11ah long‑range card).
• Demonstrated bridging between LoRa-only devices and Wi‑Fi-only devices via a node with both interfaces.

Clients and apps demonstrated

• Mesh Chat (desktop) — used successfully.
• Sideband and Nomad Net — mobile options (Sideband runs a local Reticulum instance on the phone).

Practical demos, performance, and behavior

• Two‑node Wi‑Fi Reticulum: automatic route discovery with a visualizer showing route formation.
• Two LoRa nodes: functioning over 915 MHz as expected.
• Cross‑interface bridging: three‑node topology enabled a LoRa‑only device to exchange messages with a Wi‑Fi‑only device via Reticulum bridging.

Haven + Wi‑Fi Halo experiment

• Reticulum installed on Haven nodes (Raspberry Pi router boards) using the Morse Micro Halo card (configured at 915 MHz).
• Channel widths tested from 8 MHz down to 1 MHz to trade throughput for range.
• Real‑time metrics (RSSI, frequency, packet counts) observable; removal of an antenna changed RSSI live.
• Demonstrated a sovereign, long‑range IP mesh independent of centralized infrastructure.

ATAC (Android Tactical Awareness Kit) over Reticulum

• ATAC normally expects IP/Wi‑Fi/cellular; the presenter bridged ATAC traffic across Reticulum so Android clients could discover and chat with each other.
• Reticulum handled compression, fragmentation (500‑byte MTU), routing, reassembly, and end‑to‑end encryption of ATAC messages.
• Chat and cursor‑on‑target data were demonstrated via a Python bridge script mapping multicast/messaging into Reticulum.

Software tooling, guides, and availability

• Guides and resources:
  • Mark’s Reticulum guide on unsigned.io (walkthroughs and philosophy).
  • The presenter’s complete builder guide on their website (includes gotchas and resoldering/debugging steps).
  • GitHub repo promised with scripts, Python bridge code, and configuration examples (Haven/Reticulum integration, ATAC bridge).
• Clients: Mesh Chat (desktop), Sideband (mobile), Nomad Net (mobile).
• Caveats:
  • Software may not work out of the box — configuration tweaks, resoldering, and debugging were required; the builder guide documents troubleshooting.
  • Channel width, frequency, and antenna choices significantly affect range and link quality (example: 8 MHz channel vs 1 MHz for increased range).

Why it matters

• Enables open, autonomous, sovereign communications without centralized infrastructure or platform permission.
• Bridges disparate modulation techniques and frequencies, allowing communication between devices with completely different radios.
• Scales more efficiently than flooded radio meshes for higher‑hop networks and mixed‑bandwidth scenarios.
• Cryptographic identity and default encryption make it suitable for privacy‑sensitive or tactical applications (search & rescue, off‑grid comms, tactical teams).
• Can interoperate with existing tools (e.g., ATAC, standard Wi‑Fi stacks) when bridged, opening tactical and civilian use cases for off‑grid mesh/IP services.

Useful links / resources mentioned

• Mark’s Reticulum guide: unsigned.io (Reticulum overview/guide).
• Presenter’s builder guide: full build notes and troubleshooting (on the presenter’s website — linked in the video description).
• GitHub repo: code and scripts for Haven + Reticulum integrations, Python ATAC bridge (linked in the video description).
• Client apps: Mesh Chat (desktop), Sideband (mobile), Nomad Net (mobile).
• Projects/hardware referenced: Reticulum, Meshtastic (contrast), T‑Beam, Adafruit components, Morris Micro Wi‑Fi Halo (Morse Micro 802.11ah), Haven nodes (Raspberry Pi / OpenMANET), ATAC (Android Tactical Awareness Kit).

Main speakers and sources

• The video narrator / builder: first‑person presenter who built the R node, ran tests, and published a builder guide and GitHub repo.
• Mark: creator/advocate of Reticulum; gave the “Unstoppable Networks” talk and authored the unsigned.io guide.
• Project communities and contributors referenced: Reticulum project community, Meshtastic, Fry Funk, Meshen NYC, Gyet, Morris Micro (Wi‑Fi Halo), Haven (OpenMANET/Raspberry Pi router builds), ATAC.