lfg2025/archy-messh

Go to file

Dorian a284c91848 feat: RTC rebrand + on-chip Meshtastic decode + acid display

- Rebrand to RTC (Reticulum / meshTastic / meshCore); Meshtastic row = T.
- On-chip Meshtastic decode (mbedtls AES-128-CTR + protobuf) surfacing text
  and node short-names, mirroring firmware/tools/meshtastic_decode.py.
- Device identity 'Reticutasticore' / 'RTC' (DEVICE_NAME) baked in for all
  three networks; boot splash shows it.
- Trippy OLED: acid smiley with a periodic spinning-striped freak-out
  (googly eyes + gaping mouth), punk 'bubble' RTC header, three live network
  rows (counts + RX blips), last-decoded line.
- Hardware-confirmed: Meshtastic + MeshCore both received (0x12 MeshCore
  sync word guess validated); Reticulum still placeholder.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-01 16:23:45 +01:00

docs

Add protocol research synthesis and phased architecture plan

2026-06-30 19:54:40 -04:00

firmware

feat: RTC rebrand + on-chip Meshtastic decode + acid display

2026-07-01 16:23:45 +01:00

host-bridge

fix: close relay loop from prefixed dedup mismatch

2026-07-01 15:31:52 +01:00

.gitignore

feat: Phase 1 firmware — time-multiplexed tri-protocol RX scanner

2026-07-01 15:45:36 +01:00

README.md

Add Phase 0 host-bridge: relay text across Meshtastic, MeshCore, Reticulum

2026-06-30 20:32:38 -04:00

README.md

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 docs
host-bridge/ — Phase 0: Python bridge relaying text between real Meshtastic/MeshCore/RNode-Reticulum boards over each project's official client protocol
firmware/ — 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