Murm brings the radio family together with the native peer carriers and conversation service imported from Mere. Retinue remains the Reticulum crate; all existing crate names and source histories are preserved. The canonical repository is merely-made/murm. See the family move plan for the receiving-build and consumer-cutover status.
The radio workspace stays at the root. The separate native/ workspace contains
murm, mere-transport, and mere-webrtc-carrier. The independent wire/
workspace provides murm-wire, the reusable one-hop HTTP/1-2-3 and raw
WebSocket engines. All use Rust 1.99.1 for development and declare a shared
MSRV of 1.97.1. Build the native libraries with
cargo test --manifest-path native/Cargo.toml --lib and the wire engine with
cargo test --manifest-path wire/Cargo.toml.
Original Genet source ancestry is preserved for the wire import. Netfetcher's browser policy and public crate identity stay in Genet, while hosts select trust, pooling and limits. Stickleback stays in Mere. Cross-target and live network qualification retain their own lanes; see MOVE5 in the family plan.
Signalman's desktop Messages face now routes its versioned text-over-LXMF
profile through the shared Comms adapter and the same durable application
journal. With SIGNALMAN_STATION_PORT and the existing Djinn custody service,
its attended station actor carries queued intents and persists authenticated
receive events. An unambiguous public identity from saved history supports
offline drafts; transmission still requires the station's current grant.
The face reports recorded queue, handoff, receive and failure facts. This is
software-qualified integration; wider LXMF bodies, other protocol adapters,
real-radio and headed acceptance retain their own gates.
Embedded Rust implementations of three mesh protocols, a shared radio interface layer, operator apps, and firmware that runs on my limited subset of hardware.
So: what's the idea? Why all three? I wanna make the three more like channels that are triggered by a given announce, allowing a node to configure a persona/address for each protocol and route traffic correctly. It just seemed like much of the LoRa radio hardware had the memory space to do that. And the name: a retinue of protocols, working together, letting people use each for what they're each good at. There aren't that many good names that begin with reti-...
On the host side, this is possible with existing projects, but on the embedded side, not with Rust, my preferred language ever since I first heard of Servo in 2018. The path of many such attempts, of late, for good reason. So to be clear, this is not a reference implementation of Reticulum, Meshtastic, or Meshcore: it's an experimental implementation.
I use LLMs because I have come to truly enjoy leveraging my English degree in increasingly esoteric and elaborate ways. I develop to standards so I can verify functionality, but the engineering of these projects must and will definitely be improved with time before I would release it. If you need reliable protocol implementations, consider the reference implementations.
Each crate has its own README with more detail, and here's a generated overview.
| Crate | What it is | crates.io |
|---|---|---|
murm |
Peer conversation service in native/crates/murm; immutable Git source, package identity preserved. |
Git |
mere-transport |
Native peer carriers in native/crates/transport. |
Git |
mere-webrtc-carrier |
Portable WebRTC core with optional browser/native adapters. | Git |
retinue |
Reticulum protocol: identity, announces, links, requests, Resources, routing. no_std + alloc core with a tokio shell. |
published |
outrider |
LXMF: message codec, direct and opportunistic delivery, propagation client and server. | published |
postilion |
Shared radio-host library: a Station wraps one identity, one board, an announce cadence and a peer table. | published |
seneschal |
Board-management contract: signed control requests and replies, owner and configuration journal. | published |
tulle |
Radio interface layer: serial modem control, direct PHY, medium access. | published |
selvage |
LoRa PHY profiles shared by host and firmware. | published |
sennet |
Meshtastic-compatible mesh. | published |
tucket |
MeshCore interop. | published |
radio-face, radio-hand, radio-mirror |
On-device UI, board runtime, and the UI's browser (wasm) realization. | workspace only |
retinue-sim |
In-process multi-node route-trace harness. | workspace only |
tinyssb-core |
Allocation-free tinySSB v0 feed verifier. | workspace only |
Apps: linkboy (inspects, plans and flashes firmware packages), signalman
(runs a household radio from a serial port), and signalman-desktop (its
desktop face, rooted in its own workspace). Firmware for Heltec V4 and Heltec
T114 boards is in firmware/, with flashable packages in firmware/packages/.
- Releases. On 2026-10-06, retinue and outrider 0.3.0 were published, the first releases under the Reticulum License (see License). postilion 0.3.0 and seneschal 0.2.0 were published with them; they stay MPL-2.0 and move to retinue 0.3. Earlier releases are MPL-2.0.
- Reticulum. The live oracle is pinned to RNS 1.5.7 and LXMF 1.2.0. The
repin receipt passed every
lane in a single run: 13 live, 7 LXMF, 12 Resource and 3 routing gates.
Routing decisions are identical to 1.5.6. The intermittent
interop_ifacfailure seen on 1.5.4 and 1.5.6 did not recur in 14 runs on the new macOS host. Two held RNS-side defects persist. The 0.2.0 link lifecycle work landed: route learning,open_link(now), link-request expiry, and own-echo and duplicate filtering. These results cover the measured local-TCP scopes; they are not full upstream parity. - Sennet and Tucket. The current receipt covers September 30 exchanges with identified stock radios. MeshCore 1.17.1 passed endpoint traffic, ACKs, fallback and one-repeater routes at all three path widths. Meshtastic 2.7.26 passed bidirectional encrypted text, rebroadcast, node association and duplicate suppression. Maximum-size stock acceptance, multiple repeaters and broader roles remain open.
- Firmware. T114 bounded transport has an on-air receipt from August 13. The firmware refresh and its follow-up installed clean-pin V4 and T114 images with preserved settings. They passed selected RF traffic, a 1024-byte exchange and signed announces across soft resets. Resident cancellation is not yet reliable: one isolated run passed and one timed out. Full resident, fault and unattended-operation acceptance remain open.
- Signalman desktop collects observations from identified V4 and T114 boards, with keyboard export and reload verified. Clipboard, scrolled accessibility, physical cancellation and synchronized coverage remain open.
- Power. MC5 shared-radio power measurement is pending; wiring, supply isolation and measurement qualification remain open.
The canonical index links exact receipts and open criteria. Historical plan queues and older README summaries are not current execution orders.
cargo test -p retinue # or any host crate by name
# Flashing tool
cargo run -p linkboy -- list
cargo run -p linkboy -- flash <device> <package>
# Radio host app
cargo run -p signalman -- <port> [name] [bw_khz] [phy|rnode]
# Firmware (workspace member, not a default member)
cargo build -p tulle-t114-phy --release --target thumbv7em-none-eabihf
# Desktop GUI (own workspace root)
cargo build --manifest-path apps/signalman-desktop/Cargo.tomlsignalman::survey::scene::survey_scene revalidates an admitted Survey and
exports a shared terrain/coverage recipe. GPX tracks become source guide paths,
with separate paths for separate segments; their endpoints are explicitly
labelled track samples. Radio identities from captures remain unplaced. No
observer/track association, RF time join, terrain inference or propagation
model is invented. The plane is marked unmeasured and has no coverage tiers.
The local equirectangular frame uses metres with north up and a 10 m margin;
its reference latitude and northwest corner are disclosed in the title.
Polar, antimeridian and over-budget extents are refused.
The exporter accepts a revalidated survey archive or bounded original files, without opening a radio or obtaining credentials:
cargo run --features portable-scenes -p signalman --bin signalman-survey-scene -- \
survey.json terrain.scene.json
cargo run --features portable-scenes -p signalman --bin signalman-survey-scene -- \
--gpx track.gpx terrain.scene.json capture.jsonThe optional capture uses the existing survey-capture JSON schema. The direct GPX form supplies no clock mappings; its join settings are unused. Both forms refuse an existing output file. Graphshell's Portable scenes imports the result with the shared renderer and inspection controls. These are application model and file-export paths, not a new native survey panel or a radio qualification.
The portable-scene API is integrated in Mere's canonical main source.
The committed lockfile pins the shared scene cohort, so the commands above
need no temporary local source patches. Earlier local-cohort receipts remain
historical evidence; ordinary checks use --locked and portable-scenes.
Mozilla Public License 2.0 (LICENSE) for the workspace, except
crates/retinue, crates/outrider, crates/tulle and crates/radio-hand.
Those are under the Reticulum License (retinue and
outrider from 2026-10-05, tulle and radio-hand from 2026-10-09), so that the
reference implementations can be read and adapted into them. Releases through
retinue and outrider 0.2.0 and tulle 0.1.0 remain MPL-2.0.
Anything that links them carries the Reticulum License's notice and conditions
for those portions. That includes the apps and the firmware images, which are
therefore not GPLv3. See the
decision record.
Vendored third-party forks under vendor/ (lora-phy, embedded-graphics,
embedded-graphics-core) keep their own MIT/Apache-2.0 terms.
THIRD_PARTY_NOTICES.md aggregates derivations;
per-crate NOTICE and PROVENANCE files record specifics.
We (me and a gaggle of robots with any training data settings off) acknowledge Mark Qvist and the Reticulum contributors for the protocol, its documentation, and the reference implementations. See the notices.
tulle, sennet, and tucket merged into this workspace on 2026-07-23 with
history preserved; their standalone repositories are archived.
Retinue was first built from the public-domain Reticulum protocol using two v4s and a T114, the manual, and packet captures from the reference implementations, which were run as black-box oracles like the other protocols. Comparative review of RNS source began on 2026-09-26. Nothing was copied or translated before or after. My perspective is, if you can derive the protocol from the wire, then you should do that as a control and functional baseline. The goal is verifiable interoperability with reference implementations, after all.
On 2026-10-05 retinue and outrider moved to the Reticulum License so that the reference
implementations can be adapted into them; tulle and radio-hand followed on 2026-10-09 for the
RNode host. Adaptations are listed in each crate's NOTICE.
The rest of the workspace remains MPL-2.0, and RNode firmware source stays unread.
This README was generated by AI and has/will be edited by the author upon release.
Signalman's Comms path also supports Meshtastic channel text and MeshCore
private text through the existing resident radio runtime. The Messages face
keeps protocol-specific addresses and observed delivery facts; a host supplies
its commissioned public journal and authorized runtime. The standalone face
can reopen an existing journal with SIGNALMAN_RADIO_JOURNAL. See R3 in
design_docs/2026-10-13_murm_family_move_plan.md for the software qualification
and the separate physical and headed acceptance gates. R4 adds stock
Meshtastic Stream API and MeshCore USB companion connections: select the
protocol in Messages, enter its serial port, realm and public journal path,
then Connect. The device supplies its public identity and owns radio keys and
execution. Queue acceptance and protocol acknowledgements remain distinct;
MeshCore contact prefixes must resolve to a unique full key. See the same
plan's R4 section for startup settings and the software-only qualification.