One GitHub Account Built 21 Repositories for an Offline Mesh Network in Five Months

Ratspeak is a messaging client for Reticulum, a mesh network that runs over Bluetooth, LoRa radio, WiFi and plain internet with no server or account required. Its GitHub organisation has grown from 18 repositories to 21 in the week since coverage here on 27 August, which also reported a token on Base trading under the project's name. That token has since fallen 73% from its $6.0m high to a $1.78m market capitalisation, according to CoinGecko data read September 3, a useful reminder that a project's shipping pace and its token's price are two different facts that do not move together. What follows is the state of the project since: what has shipped, who is building it, and what a reader evaluating Ratspeak should be checking that a price chart does not show.

What shipped while the price fell

Three repositories in the github.com/ratspeak organisation did not exist when the earlier piece ran. rsReticulumLite and rsLXMFLite are stripped-down, no_std ports of the network stack and its messaging layer, built for microcontrollers too constrained to run the full implementation. ratspeak-handheld unifies the firmware across three LoRa handhelds the organisation already supported. All three were created August 31, four days after the token's peak and while its price was already down more than half from that high. The flagship client has not tagged a new release since v1.0.31 on 27 August, but its repository still received commits through August 30, and the organisation now counts 21 public repositories against 18 a week earlier.

The rest of the ecosystem

The earlier piece named rsReticulum and rsLXMF, Rust implementations of the network stack and its messaging layer, alongside rsDeck and rsCardputer, firmware for two LoRa handhelds, and rathole, a transport node. The organisation's remaining repositories cover ground that piece did not reach: ratkey, which ties a Reticulum identity to a YubiKey; LXMFace, a deterministic visual-identity generator for mesh addresses; lrgp-py and lrgp-rs, a turn-based gaming protocol built to run over the mesh in both Python and Rust; revanity-go, a vanity address generator for Reticulum and LXMF identities, the mesh equivalent of a custom address rather than a cryptocurrency wallet tool; rsPager, firmware for a third LoRa handheld; rsLXST, an experimental voice layer; and C6-Reticulum-ASM, pure assembly firmware for a low-power microcontroller. Rathole's own README describes it as "PoC only".

The protocol underneath

Reticulum, the network stack all of this runs on, was not built by this organisation. It was created by Mark Qvist and has existed since 2018; the original Python implementation carries 7,137 stars and 529 forks on GitHub, read the same day as the figures above. Ratspeak's Rust implementation, rsReticulum, describes itself as a reimplementation aimed at interoperability rather than a fork of Qvist's codebase, which means a client built on it is a bet on a shared protocol rather than on one team's branch of it.

How it compares

Ratspeak is not the first client built for Reticulum, and Reticulum is not the only mesh protocol trying to solve this problem. The table below sets it against Mark Qvist's own official Reticulum clients, the LoRa mesh project with by far the largest community, and two Bluetooth-first mesh messengers built on separate networks entirely, using GitHub's own figures, read September 3.

Two things stand out. Every other project in the table is older and has more outside contributors than Ratspeak, including the two clients built by the person who wrote the protocol it runs on. And the project that drew the most attention for solving a version of the same problem, Bitchat, did it in fourteen months with fifty-six contributors and 36,122 stars, an order of magnitude beyond anything else here. Ratspeak's distinguishing ground against Sideband and NomadNet is narrower than the surrounding attention suggests: platform coverage neither of Qvist's clients has, Windows and iOS, voice calls, and a Rust rewrite in place of Python.

Why the rewrite is in Rust

The distinguishing detail in that comparison, a Rust implementation instead of Qvist's Python, is not stylistic. Reticulum's original implementation needs a Python interpreter, which puts it out of reach of the smallest microcontrollers the organisation's firmware targets: the ESP32-class chips inside the T-Deck, the T-Pager and the Cardputer, and the bare no_std ports in rsReticulumLite and rsLXMFLite. Rust compiles to a standalone binary with no interpreter and no garbage collector, which is what lets the same protocol run inside kilobytes of memory on hardware Qvist's own client cannot target at all. On the desktop, where Python already runs Reticulum without trouble, Rust's advantage is narrower: memory safety enforced by the compiler rather than by discipline, useful for software handling untrusted network input and cryptography, at the cost of a smaller pool of people who can read and contribute to the code. That trade-off shows up in the numbers above. Qvist's Python projects have drawn more outside contributors over more years than anything on the Rust side of this organisation has in five months.

What running offline actually requires

Reticulum treats an internet connection as one of several interchangeable transports rather than a requirement, and the practical version of that claim is worth stating plainly. Over an ordinary internet connection, the client behaves like any encrypted messenger, carrying traffic over TCP with no radio hardware involved. Remove the internet and it falls back to whatever transport two people actually share: devices within Bluetooth range, or on the same local WiFi network, including one with no working internet uplink at all, can still reach each other directly. Beyond that range, reaching someone requires LoRa radio on both ends, the class of hardware the T-Deck, T-Pager and Cardputer firmware in the organisation's repositories targets, relaying over kilometres of unlicensed spectrum without a carrier. What the software does not do is create a path where none exists. Without a shared network, a radio in range, or a chain of nodes relaying between two users, there is nothing to route a message over, whatever the identity and encryption layers can do. The offline claim is real, and it is bounded by exactly that physical requirement.

Who is building it

GitHub's contributor data names the work: the handle defidude has 604 commits on the flagship client and 378 on rsReticulum, both effectively unchanged from the 603 and 378 recorded a week earlier, and the same handle wrote 262 of the commits on the project website and the majority or entirety of the commits on rathole, ratkey and most of the hardware firmware. The one repository with meaningfully distributed authorship is rsDeck, the T-Deck firmware, which has drawn six contributors. The client is AGPL-3.0-or-later, describes its own status as alpha, and lists macOS and Windows builds as unsigned, with signing for Windows BLE peering support still in progress.

What to watch

The token's price is a separate story, already told. What the software side asks a reader to track is different: whether an independent security audit of the client or the protocol implementations is ever published, since none currently is; whether the unsigned macOS and Windows builds move to signed releases; whether rathole's own proof-of-concept label is lifted as the code matures; and whether a second repository starts to look like rsDeck, with contributors beyond the one account that wrote nearly everything else in the organisation.