Off-Grid Mesh Messaging: Final Ranking, Scoring & Analysis

1) Final Ranking

2) Criteria & Weights (Final Set)

Scores are 0–100 per criterion, multiplied by weights, then summed to a composite. Two explicit design choices dominate the model: (1) defaults matter more than best-case hardening, and (2) capture-resistance (cloud/AI/weaponization pathways) is treated as a first-class axis.

3) Score Matrix (0–100)

Each score is a deliberately adversarial reading of defaults, protocol trust structure, and capture pathways.

4) Composite Calculations

Composite score is the weighted sum: Composite = Σ(score × weight). Weights are decimals (e.g., 18% → 0.18).

Reticulum stack — 93.3 / 100

Meshtastic — 68.8 / 100

MeshCore — 64.1 / 100

5) Reticulum stack — 93.3 / 100

Role in the landscape

Reticulum is a cryptography-based networking stack designed to operate under adverse conditions (very low bandwidth, very high latency), enabling local and wide-area networks across heterogeneous carriers. LXMF provides end-to-end encrypted store-and-forward messaging on top, with clients such as Sideband, NomadNet, and MeshChat. See: Reticulum Manual (PDF), Reticulum Manual (HTML).

1) Core Cryptography & Protocol Soundness — 96

• Crypto-native architecture with end-to-end encryption and forward secrecy described as core properties (manual).
• Uses standard primitives and emphasizes cryptographic identity and transport semantics rather than optional “bolt-on” encryption (documentation hub).
• Main penalty: no widely published full third-party audit; score reflects design strength with audit uncertainty.

2) Default Privacy & Metadata Posture — 94

• Encryption and cryptographic addressing are baseline; no “public default PSK” compatibility mode is structurally equivalent to Meshtastic’s “AQ==” default key.
• Design philosophy explicitly centers on the reality that architecture determines political outcomes (Zen of Reticulum).

3) Decentralisation & Topology Antifragility — 95

• Multi-carrier interfaces are a first-class concept (LoRa/RNode, serial links, IP transports, etc.) (Using Reticulum).
• No mandatory broker, cloud service, or global infrastructure requirement; networks can remain local, partitioned, and still functional.

4) FOSS / Auditability — 85

• Protocol documentation and manual are openly published (manual PDF, manual HTML).
• Reference implementation is source-available and forkable, but license is not OSI-free due to ethical restrictions (license text).

5) Anti-Capture & Anti-Synthetic-Stack Stance — 98

• Explicit prohibitions against use in systems designed to harm humans and against AI/ML/language-model training datasets (license).
• Philosophical framing states that “a tool is intent, crystallized,” and treats architecture as politics (Zen).

6) Operational Maturity & Ecosystem — 85

• Mature docs and ongoing releases and maintenance (GitHub releases).
• Multiple client paths exist (messaging and general networking); ecosystem is smaller than Meshtastic but coherent and aligned.

7) Hardware Flexibility & Supply Independence — 90

• Operates on general computers and multiple interface types; not locked to a single vendor device class (interfaces overview).

8) Deep Telos Fit — 98

• Telos alignment is encoded simultaneously in architecture (crypto-first), documentation, and license-based resistance to extractive/weaponized capture (Zen, license).

6) Meshtastic — 68.8 / 100

Role in the landscape

Meshtastic is a large LoRa mesh ecosystem (firmware + apps + integrations) optimized for usability and broad adoption. It offers encryption mechanisms, but the default posture is explicitly documented as insecure for adversarial environments. See: Encryption docs, Configuration tips, MQTT integration.

1) Core Cryptography & Protocol Soundness — 70

• Payload encryption is documented (AES variants) and direct messaging uses modern key exchange primitives in newer versions (encryption).
• Main penalty: history of architecture-level security assumptions (identity/trust choices) and the existence of insecure default modes.

2) Default Privacy & Metadata Posture — 30

• Default primary channel uses the known PSK “AQ==” (explicitly documented) (encryption).
• Official configuration tips state that leaving “AQ==” unchanged causes location to be shared with all nodes in range on the default channel (tips).
• Headers remain unencrypted for routing reasons (documented), enabling metadata and traffic analysis at the RF level.

3) Decentralisation & Topology Antifragility — 75

• RF mesh is decentralized, but the ecosystem strongly encourages MQTT bridging and integrations that can become choke points and observation layers (MQTT docs).

4) FOSS / Auditability — 95

• Broad open source footprint across firmware and tooling; high auditability and forkability in classical FOSS terms.

5) Anti-Capture & Anti-Synthetic-Stack Stance — 55

• No built-in legal or cultural constraints against AI extraction; MQTT/cloud bridges create natural ingestion pathways (MQTT docs).

6) Operational Maturity & Ecosystem — 94

• Dominant ecosystem advantage: large community, wide device support, extensive documentation, and mature integrations.

7) Hardware Flexibility & Supply Independence — 95

• Runs on a wide range of inexpensive LoRa boards across vendors; supply diversity is high.

8) Deep Telos Fit — 65

• Functional for off-grid civil use cases, bridging, and broad adoption, but defaults and integration culture require aggressive de-clouding and hardening to approach a sovereign posture.

7) MeshCore — 64.1 / 100

Role in the landscape

MeshCore is a lightweight hybrid routing system for LoRa and other packet radios, with companion devices, repeaters, and room servers. See: GitHub repo, FAQ, project site.

1) Core Cryptography & Protocol Soundness — 50

• A publicly filed security report flags ECB mode usage and padding weaknesses in MeshCore encryption implementation (Issue #259).
• External technical writeups describe AES-ECB in the cryptography path (independent analysis; treat as secondary evidence) (MeshCore cryptography deep-dive).
• Score reflects “known crypto design debt” rather than “unknown crypto risk.”

2) Default Privacy & Metadata Posture — 40

• Default operational posture is degraded by reliance on companion devices and clients; critical components being proprietary is a persistent trust sink (OpenELAB comparison, field notes (client closed-source frustration)).

3) Decentralisation & Topology Antifragility — 80

• Supports multi-hop routing and server roles (repeaters/room servers), enabling autonomous nodes, but those roles can become chokepoints in adversarial settings.
• Server/role administration is explicitly part of typical deployments (example guidance) (server administration guide).

4) FOSS / Auditability — 75

• Core routing library and much of firmware are open and MIT-licensed (repo).
• Closed-source reality for official clients and some firmware is widely noted by observers and comparisons (OpenELAB, field notes, community discussion (apps closed)).

5) Anti-Capture & Anti-Synthetic-Stack Stance — 55

• MIT licensing provides no friction against AI/cloud surveillance reuse; closed clients provide an easy telemetry hook surface.

6) Operational Maturity & Ecosystem — 80

• Active development and growing tooling surface; practical deployments documented by third parties (field notes, Hackaday review).

7) Hardware Flexibility & Supply Independence — 88

• Works across common LoRa dev boards; the ecosystem also promotes “certified devices” and official app compatibility (official store, apps page).

8) Deep Telos Fit — 70

• Off-grid mesh intent and practicality are real, but crypto debt + closed clients + chokepoint roles keep it from being a primary sovereign substrate without refactoring.

8) Condensed Comparative View

Reticulum stack — 93.3 / 100

• Identity & crypto: crypto-native design with E2EE and forward secrecy as core claims (manual).
• Defaults: privacy is baseline, not optional.
• Capture resistance: explicit bans on AI/ML training datasets and harm-systems (license), reinforced philosophically (Zen).
• Role: primary sovereign communications substrate.

Meshtastic — 68.8 / 100

• Ecosystem: strongest adoption and maturity.
• Defaults: explicitly insecure in adversarial terms (default PSK “AQ==”) (encryption), and location sharing risk is warned (tips).
• Capture pathways: MQTT/cloud bridges are a standard integration vector (MQTT docs).
• Role: civil/off-grid utility mesh and bridge layer under strict hardening.

MeshCore — 64.1 / 100

• Routing: practical role-based topology with repeaters and room servers; useful but chokepoint-prone.
• Crypto debt: ECB/padding issues explicitly raised (issue #259) and discussed externally (analysis).
• Auditability gaps: closed client reality is repeatedly reported (OpenELAB, field notes).
• Role: tactical/local component inside a carefully controlled perimeter; not a primary substrate without cryptographic and client openness fixes.