OSHI vs Reticulum: Sideband, NomadNet and RNode
OSHI is a free, open-source, end-to-end encrypted messenger for iOS and Android that uses Bluetooth and Wi-Fi mesh networking to send messages without Internet or cellular service. Reticulum is not an app but a cryptography-based networking stack; people message over it with Sideband, Nomad Network or MeshChat, often through an RNode LoRa transceiver. This page compares the two honestly, using reticulum.network and the project's GitHub as sources.
What Reticulum is
Reticulum's own definition: "the cryptography-based networking stack for building local and wide-area networks with readily available hardware." It runs on "practically any system that runs Python 3", needs no kernel modules, and works over almost any medium with "greater throughput than 5 bits per second, and an MTU of 500 bytes". Supported interfaces include LoRa via RNode (open firmware you flash onto common LoRa boards, or a handheld unit sold by the author), TCP and UDP over IP, I2P, Wi-Fi and Ethernet, serial ports and packet-radio TNCs. The protocol was dedicated to the public domain in 2016; the reference implementation is under the Reticulum License.
You do not "install Reticulum" as a messenger. You install a client: Sideband (Android, Linux, macOS, Windows; CC BY-NC-SA 4.0), Nomad Network (terminal-based, also hosts propagation nodes) or MeshChatX (browser-based LXMF client). They exchange messages with the LXMF protocol, which is delay- and disruption-tolerant: a message can wait on a propagation node until the recipient appears.
Feature comparison: OSHI vs Reticulum
| Feature | OSHI | Reticulum + Sideband / NomadNet |
|---|---|---|
| Kind of thing | A messenger app | A network stack plus separate client apps |
| Hardware required | None for the phone mesh; optional LoRa node (Heltec V3 verified) | None over IP/Wi-Fi; an RNode LoRa transceiver for off-grid radio links (dev board flashed with RNode firmware, or a handheld from unsigned.io) |
| Phone app | iOS 17.5+, macOS 14.5+, Android APK | Sideband on Android, Linux, macOS, Windows. iOS: no official client listed on reticulum.network or the Sideband repository (checked 2026-09-07) |
| Encryption model | X3DH + AES-256-GCM, Curve25519. The Double Ratchet, and with it forward secrecy, runs in the v3 session format only — the older v2 format does not ratchet and most of the installed base is still on v2 (status). Adds X-Wing (ML-KEM-768 + X25519) hybrid post-quantum key agreement where both ends support it. The LoRa air link is not encrypted by OSHI | "X25519 encryption and Ed25519 signatures as a basis for all communication", AES-256-CBC, HMAC-SHA256; "all encryption keys are ephemeral, and communication offers forward secrecy by default"; unencrypted communication is impossible on any transport, LoRa included |
| Addressing / identity | Keypair on the device, no phone number; contacts by QR code, link or pasted key | Self-sovereign, portable addresses derived from keys; no source addresses in packets |
| Group / channel model | Groups; names and member lists visible to OSHI's server on the Internet path | LXMF is peer-to-peer message transfer with propagation nodes for store-and-forward; group chat semantics: not verified |
| Range over LoRa | 2–5 km city, 5–15 km suburban, 15–50+ km open terrain (OSHI field figures) | No official figure published; depends on terrain and antenna — measure |
| What can be sent | Text, photos, voice notes, files, live location, calls when an IP path exists | Sideband: text, files, images, voice messages, real-time voice calls (LXST), telemetry and maps; throughput limited by the slowest link |
| Works over the Internet too | Yes, automatically, including Tor | Yes — TCP/UDP and I2P interfaces; a network can mix LoRa and Internet links |
| Open source | Crypto core, mesh layer, bot SDK under MIT; app shell not published | Stack: public-domain protocol, Reticulum License implementation. Sideband: CC BY-NC-SA 4.0 |
| Setup effort | Install the app; pair a node in four steps | Configure interfaces (a text config file), optionally flash RNode; the terminal is part of the experience |
Sources: reticulum.network (home and manual), github.com/markqvist/Reticulum, github.com/markqvist/Sideband, unsigned.io/rnode (read 2026-09-07); oshi-messenger.com/lora/; OSHI App Store listing v1.0.39.
Where Reticulum genuinely wins
- Encryption on every link, including LoRa. Reticulum cannot send plaintext. OSHI's LoRa link relies on the node firmware and the App Store listing states the link is not encrypted by OSHI.
- Transport independence. One network can span LoRa, packet radio, I2P and plain TCP, with routing done by the stack. OSHI has three fixed paths: Internet/Tor, phone mesh, LoRa node.
- Infrastructure you own. Propagation nodes and transport nodes are yours; there is no project-run server anywhere in the design. OSHI's Internet path goes through OSHI's relay, which cannot read messages but does see sender and recipient public keys, timestamps, message sizes, and group names and membership.
- Open protocol and implementation with a long public history and a broad ecosystem of clients and tools.
Where OSHI is different
- iPhone. OSHI runs on iOS today. Reticulum lists no iOS client. For a mixed group of iPhone and Android users that alone decides it.
- Zero setup and zero hardware for the common case. Two phones with OSHI open find each other over Bluetooth. Reticulum expects you to define interfaces, and off-grid links need an RNode.
- Phone-to-phone mesh. Reticulum on a phone talks to an RNode or to the Internet; it does not turn a crowd of phones into a Bluetooth/Wi-Fi mesh. OSHI relays across up to five phones with store-and-forward.
- Consumer features: offline OpenStreetMap maps with routing, view-once media, on-device AI, steganography, a bot API.
Can they be used together?
Not as one network. OSHI's node speaks Meshtastic's Bluetooth service; an RNode speaks Reticulum's. Nothing documented bridges them. What you can do is run both on the same Android phone and use each for what it is best at — Reticulum for the encrypted long-haul radio link, OSHI for everyone nearby and for the Internet path.
Who each suits
Choose Reticulum if you want a network you fully control, need strong cryptography on the radio link itself, are comfortable with configuration files, and your people are on Android or desktop. Choose OSHI if your group includes iPhones, you want rich messages and calls, and you want offline and online messaging in a single app with no setup. See every LoRa messenger compared.
Related pages
LoRa messenger app explainedLoRa messengers compared (2026)OSHI vs MeshtasticOSHI vs MeshCoreOSHI vs BriarWhat is TorAll comparisonsFrequently asked questions
Is Reticulum a messenger app?
No. Reticulum is a networking stack. You message over it with a client such as Sideband, Nomad Network or MeshChatX, using the LXMF message protocol.
Does Reticulum run on iPhone?
No official iOS client is listed on reticulum.network or in the Sideband repository as of September 2026. Sideband supports Android, Linux, macOS and Windows. OSHI runs on iOS 17.5+ and macOS.
Is Reticulum's LoRa link encrypted?
Yes. Reticulum states that unencrypted communication is impossible: every link uses X25519 key exchange, Ed25519 signatures, AES-256-CBC and ephemeral keys with forward secrecy. OSHI's LoRa link is not encrypted by OSHI; OSHI's end-to-end encryption applies between OSHI phones.
What hardware does Reticulum need for LoRa?
An RNode: either a common LoRa development board flashed with the open RNode firmware, or a handheld RNode sold by the author. Over Wi-Fi or the Internet no extra hardware is needed.
How far does Reticulum reach over LoRa?
The project publishes no range figure. Range depends on terrain, antenna and allowed transmit power; measure your own links. OSHI publishes field figures of 2–5 km in cities up to 15–50+ km in open terrain for its node.
Can OSHI talk to a Reticulum network?
No. Nothing documented bridges OSHI and Reticulum. You can run both apps on one Android phone and use each for different links.
Try OSHI free
Encrypted messaging with no phone number, offline Bluetooth and Wi-Fi mesh, an optional LoRa node, offline maps and on-device AI.