HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
markqvist
Reticulum
Python2022–2026
markqvist / Reticulum

Reticulum

The cryptography-based networking stack for building unstoppable networks with LoRa, Packet Radio, WiFi and everything in between.

33Distinct people
41Mentions
0Explicit recommenders
7.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The cryptography-based networking stack for building unstoppable networks with LoRa, Packet Radio, WiFi and everything in between.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year41 dated mentions

Observed mentions: 2022-03-31 17:49:57 UTC to 2026-07-02 08:07:08 UTC.

0510152022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 14 mentions; 3 submissions, 11 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC211
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC321
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC12111
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC1019
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC14311

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Reticulum Network Stack WarningA significant number of hastily launched, incorrect, dubious, directly harmful and, in most cases, entirely LLM-generated fakes of Reticulum implementations, "documentation", "guides" and user-facing applications are currently being marketed under polished, but ultimately misleading or outright deceptive claims. For more detailed information, see the relevant sections of the Brandolini's Reference chapter of the manual. Known good community implementations are listed in the Community Implementations section of this readme. For software and projects recognized by the Reticulum community, see the Programs Using Reticulum chapter of the manual. Machine-generated content derived from the RNS source code or documentation (such as "implementations", "guides" for sale, et cetera), are in several, well-documented cases violating the open source licenses that granted rights of copying and distribution. Any claimed assertion of copyright or grant of license (Apache, GPL, et cetera) that such projects are making are void grants. Both the violators themselves, and all downstream projects using the infringing derivatives, are directly and personally liable for the legal consequences. Do not use these "projects", they are a hazard to the entire ecosystem we have been carefully building over the last ten years. This repository is a public mirror. All development is happening elsewhere. To understand the foundational philosophy and goals of this system, read the Zen of Reticulum. Reticulum is the cryptography-based networking stack for building local and wide-area networks with readily available hardware. It can operate even with very high latency and extremely low bandwidth. Reticulum allows you to build wide-area networks with off-the-shelf tools, and offers end-to-end encryption and connectivity, initiator anonymity, autoconfiguring cryptographically backed multi-hop transport, efficient addressing, unforgeable delivery acknowledgements and more. The vision of Reticulum is to allow anyone to be their own network operator, and to make it cheap and easy to cover vast areas with a myriad of independent, inter-connectable and autonomous networks. Reticulum is not one network. It is a tool for building thousands of networks. Networks without kill-switches, surveillance, censorship and control. Networks that can freely interoperate, associate and disassociate with each other, and require no central oversight. Networks for human beings. Networks for the people. Reticulum is a complete networking stack, and does not rely on IP or higher layers, but it is possible to use IP as the underlying carrier for Reticulum. It is therefore trivial to tunnel Reticulum over the Internet or private IP networks. Having no dependencies on traditional networking stacks frees up overhead that has been used to implement a networking stack built directly on cryptographic principles, allowing resilience and stable functionality, even in open and trustless networks. No kernel modules or drivers are required. Reticulum runs completely in userland, and can run on practically any system that runs Python 3. Read The Manual The full documentation for Reticulum is available at markqvist.github.io/Reticulum/manual/. You can also download the Reticulum manual as a PDF or as an e-book in EPUB format. For more info, see reticulum.network and the FAQ section of the wiki. Notable Features Coordination-less globally unique addressing and identification Fully self-configuring multi-hop routing over heterogeneous carriers Flexible scalability over heterogeneous topologies Reticulum can carry data over any mixture of physical mediums and topologies Low-bandwidth networks can co-exist and interoperate with large, high-bandwidth networks Initiator anonymity, communicate without revealing your identity Reticulum does not include source addresses on any packets Asymmetric X25519 encryption and Ed25519 signatures as a basis for all communication The foundational Reticulum Identity Keys are 512-bit Elliptic Curve keysets Forward Secrecy is available for all communication types, both for single packets and over links Reticulum uses the following format for encrypted tokens: Ephemeral per-packet and link keys and derived from an ECDH key exchange on Curve25519 AES-256 in CBC mode with PKCS7 padding HMAC using SHA256 for authentication IVs are generated through os.urandom() Unforgeable packet delivery confirmations Flexible and extensible interface system Reticulum includes a large variety of built-in interface types Ability to load and utilise custom user- or community-supplied interface types Easily create your own custom interfaces for communicating over anything Authentication and virtual network segmentation on all supported interface types An intuitive and easy-to-use API Simpler and easier to use than sockets APIs, but more powerful Makes building distributed and decentralised applications much simpler Reliable and efficient transfer of arbitrary amounts of data Reticulum can handle a few bytes of data or files of many gigabytes Sequencing, compression, transfer coordination and checksumming are automatic The API is very easy to use, and provides transfer progress Lightweight, flexible and expandable Request/Response mechanism Efficient link establishment Total cost of setting up an encrypted and verified link is only 3 packets, totalling 297 bytes Low cost of keeping links open at only 0.44 bits per second Reliable sequential delivery with Channel and Buffer mechanisms Community Resources The references listed here are not run, managed or moderated by the Reticulum project or its maintainer. They are provided by dedicated, independent volunteers in the community, for the benefit of anyone interested in learning more about Reticulum. Reticulum Community Wiki RNS Recipes RNS Moscow RMAP.world If you find anything that is no longer accurate, incorrect or simply not quite up to date, do no
Read the full README on GitHub

What Hacker News says

2 sources
answer from the Reticulum creator: “My knowlegde about Meshtastic is a bit limited, so I might get some details wrong, but from what I understand, Meshtastic is more or less an application. It is focused on carrying out a single task well, in a way that is easy to understand and deploy, but that also means that it will not really do anything else than that task, and stop working well if you push it close to, or outside, its intended operational domain. Reticulum itself is a general purpose communications stack. It will handle any sort of digital communication for you, from sending a single data packet to sending messages or streaming a video call, to serving a library of all human knowledge. But it will not do so itself. Someone will have to write the applications that utilise Reticulum to do those tasks. This also means that Reticulum, i
Read the rest
n itself, will not allow anyone to have a chat with someone else. You need an application using Reticulum for that, and a Reticulum network. Right now, only a handful of programs and applications exist that use Reticulum. One of those systems is LXMF, a distributed messaging protocol that enables direct (and offline) messaging between users and machines. There is currently several LXMF clients available that people can use on mobile devices and computers. This is similar to Meshtastic, in that they both serve the same end-goal, of sending messages between users. I don't know how open or interoperable the Meshtastic protocol is, but I do know that LXMF is very open and easy to integrate in other system, and messages passed with LXMF can be transported over any number of mediums, such as LoRa, WiFi, packet radio or over the Inernet. And you can mix and match the mediums as you please. This is possible since the messaging system is built on top of Reticulum (a general purpose networking stack), and it then gains all the capabilities of it (such as efficient multihop routing, global addressing, strong encryption, good privacy and so on). I hope this clarifies it a bit. If not please ask away and I will try to answer as best I can!“ https://github.com/markqvist/Reticulum/discussions/77#discus...
In Meshtastic is an encrypted communications platform for the Lora RF protocol

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.