Meshtastic — selected stack
Meshtastic firmware v2.8.1.8e6a88d Alpha (commit 8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c); standalone LoRa mesh, radio/region preset agreed locally, ordinary CLIENT relaying; no MQTT, Wi-Fi/Ethernet network or Internet bridge; trusted local serial client. PKI-capable build, direct messages with independently confirmed endpoint public keys; private channel key, STRICT signature policy, no licensed plaintext mode. Store-and-forward module disabled. No claim that this Alpha is a production recommendation; radio nodes are the cryptographic endpoints. C04 witness fixes ordinary CLIENT rebroadcast_mode=ALL; private-channel key and STRICT signature policy retained. Unknown-channel opaque forwarding is included, not CLIENT_MUTE/NONE. F16 administrative witness: headless CLIENT, KNOWN_ONLY plus STRICT, locally provisioned authorized User records/full keys only, no remote administrative authority for ordinary peers; store-forward off, persisted ignore policy and completed restart for revocation. Separate from C04 CLIENT/ALL probe witness. C06 witness: native meshtasticd/Portduino with real LoRa radio, separately provisioned full contexts, explicit distinct General.MACAddress values, independent keys/names/preferences and no shared identifier-bearing telemetry. No automatic embedded-device rotation claim or UDP radio transport. C08: native Linux meshtasticd with real SPI/USB LoRa, ordinary CLIENT/ALL relaying, full writable virtual filesystem on verified private tmpfs with noswap; host swap/hibernation/dumps and persistent log/export/backup paths disabled. Restore only clean static identity/radio/trust provisioning at cold start, never learned NodeDB/history. No flash-device default or live-memory secrecy claim. F39-only witness: native Linux meshtasticd at the selected firmware commit, with a real SPI/USB LoRa radio and a distinct local client process using the native TCP Client API on loopback (port 4403). This explicitly replaces the serial attachment for this witness only; it adds no remote IP transport, MQTT or Internet bridge. Address a daemon-hosted module service by node number and application port, using the same ToRadio/MeshPacket interface for the local node and a remote LoRa node. NodeInfo is an existing request/response service; allow its normal response policy and throttling. Other criterion-specific serial and security configurations remain unchanged.
Official project website · Logo credits · Methodology and limits