d882458885
- switch the Reticulum announce from a plain "archy.messh" destination to "lxmf.delivery" so the bridge shows up as a messageable contact in Reticulum/LXMF clients; app_data is the display name "Archy-Messh" - name_hash/dest_hash construction verified byte-identical to RNS.Destination.hash(id, "lxmf", "delivery") - bump R-window LoRa preamble 16 -> 18 to match RNode firmware Note: an RNode peer (.116) is not yet demodulating the bridge's R-PHY TX (rxb stays flat) though the bridge decodes the RNode's announces fine and the bridge's TX works on the MeshCore PHY — an asymmetric RadioLib-TX/RNode-RX issue still to chase. Receiving LXMF message *content* is a further build. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
archy-messh
Research + firmware project exploring a single LoRa device that can speak, relay, and repeat between three independent mesh networking protocols:
- Meshtastic
- MeshCore
- Reticulum (via RNode-style modem firmware)
Goal: one ESP32-based device that acts as a tri-protocol repeater/bridge —
not a fork of any single project, and not affiliated with or dependent on
the archy (Archipelago) codebase. This repo is intentionally standalone.
Status
Architecture phase done — see docs/ARCHITECTURE.md for the protocol
research, hardware constraints (target: Heltec WiFi LoRa 32 V3), and
phased plan. Phase 0 (host-side bridge across 3 separate stock-firmware
boards) is written — see host-bridge/ — but not yet hardware-tested; no
LoRa boards have been attached to the dev machine this was written on.
Layout
docs/— protocol research notes and architecture/design docshost-bridge/— Phase 0: Python bridge relaying text between real Meshtastic/MeshCore/RNode-Reticulum boards over each project's official client protocolfirmware/— Phase 1+ embedded firmware (once Phase 0 is validated on hardware)hardware/— reference hardware notes / board selection
Non-goals (for now)
- Not reimplementing any of the three protocols from scratch in v1
- Not targeting non-ESP32 hardware initially
- Not touching/depending on the
archy(Archipelago) repo in any way