649f196171
- try both packet alignments: real RNode transmissions arrive with a 1-byte leading offset vs a raw RNS packet, so parse at offset 0 and 1 and take the alignment whose dest-hash validates - accept on validated dest-hash (SHA256(name_hash||SHA256(pub)[:16])[:16]) and treat the Ed25519 signature as a bonus: announces with large app_data get truncated at the LoRa 255B MTU, which breaks the signature but not the pubkey<->destination binding; report sig ok vs unverified(truncated) - verified end-to-end on real hardware: decoded a live RNS RNode's (.116) announces over the air with sig=ok, dest + display name extracted All three networks now confirmed on real hardware: meshTastic, MeshCore, RNS. 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