Meshtastic
P2P Protocol
Community
Details
License Open source (GPL-3.0 for firmware); github.com/meshtastic — multi-repo organization: firmware (C++/ESP32/nRF52/RP2040), Meshtastic-Android, Meshtastic-Apple, python CLI/SDK, protobufs (Protocol Buffer definitions), web client
Dev Status 🟢 Active
Dev Status Detail Production / Active (firmware v2.7.x; 6,871 GitHub stars, 2,044 forks on firmware repo; 100+ supported device models; ~40,000 active nodes globally; 26 LoRa regions supported; 39 languages; Android, iOS, web, CLI clients; active daily development)
Owner Meshtastic LLC (registered trademark); founded by Kevin Hester (geeksville); firmware development led by Ben Meadors (thebentern); community-driven open-source project with 100+ contributors
Governing Body Company-controlled (Meshtastic LLC — registered trademark holder) | None (protocol defined by the community protobufs repository; no standards body)
Country USA
Start Year 2020
Stack C++ (firmware for ESP32, nRF52840, RP2040/RP2350, Linux); Protocol Buffers (communication backbone); Kotlin (Android app); Swift (Apple app); Python (CLI/SDK); TypeScript (web client); Bluetooth LE (device-to-phone pairing); WiFi (configuration/MQTT bridge)
Funding Community donations via Open Collective (opencollective.com/meshtastic); hardware vendor sponsorships (Heltec, RAK Wireless, Seeed Studio, Elecrow, LilyGo, M5Stack, MuziWorks, NomadStar, Hexaspot); sponsored by Vercel, Datadog
Last Investigated Jan 15, 2026
P2P Protocol Attributes
Origins Off-grid communication (Kevin Hester conceived the project for outdoor communication during hobbies without reliable internet; evolved from maker/hobbyist roots into emergency preparedness and disaster response tool; community-driven grassroots development)
Database N/A (stateless message forwarding; no persistent database — store-and-forward relay with configurable hop limits; messages are ephemeral packets relayed through mesh)
Query Language N/A (no query interface; Protocol Buffer-defined message types for text, position, telemetry, admin commands)
Data Formats Protocol Buffers (all message serialization); AES-256-CTR encrypted payloads; LoRa chirp-spread-spectrum modulation (Semtech SX1262/SX1276/SX1278); configurable spreading factors and bandwidth; JSON (MQTT bridge output)
Collaborative Live Editing No (text messaging only; no document collaboration — designed for short messages, GPS coordinates, and telemetry data)
Rich Text Editing No (plain text messages with emoji support; bandwidth limitations constrain message size)
Mobile Support Yes (native Android app via Google Play / F-Droid; native iOS/iPadOS/macOS app via App Store; Bluetooth LE pairing with nodes; standalone on-device UI (MUI) since v2.6)
Web Support Yes (web client at client.meshtastic.org; web-based flasher at flasher.meshtastic.org; MQTT bridge for internet connectivity)
Native Apps Yes (Android, iOS/iPadOS/macOS, web client, Python CLI/SDK, Linux daemon meshtasticd; standalone device UI on compatible hardware with keyboards/displays)
Terms Open source (GPL-3.0 firmware; Apache-2.0 protobufs); free to use; operates on license-free ISM bands (no ham license required); Meshtastic® is registered trademark of Meshtastic LLC
Funds Not publicly disclosed (community-funded via Open Collective donations; no venture capital; hardware sponsorships provide in-kind support)
Based On LoRa (Semtech chirp-spread-spectrum modulation); ESP32 (Espressif microcontroller); nRF52840 (Nordic Semiconductor); Protocol Buffers (Google serialization); AES-256 (encryption); Curve25519/Ed25519 (public-key DM encryption); MQTT (internet bridge protocol)
P2P Architecture Flooding mesh (every node simultaneously client and repeater; messages rebroadcast by all receiving nodes until destination reached or hop limit exhausted; stateless forwarding; configurable max hop count; up to ~100 concurrent devices per mesh)
Overlay Network LoRa radio mesh (operates on ISM bands — 868 MHz EU, 915 MHz US, etc.; independent of IP networks; optional MQTT bridge connects mesh to internet; can bridge distant meshes via internet gateway)
Content Addressing No (messages addressed by node ID / destination address; no content-based addressing)
Local-First Yes (fully offline-capable; no internet or cellular infrastructure required; all communication via direct LoRa radio; store-and-forward for delayed delivery)
E2EE Partial (AES-256-CTR symmetric encryption on channels — all channel members share key; public-key encryption for direct messages using Curve25519; headers remain visible for mesh routing; admin actions use PKI)
CRDTs Lib No (no CRDT implementation; stateless message forwarding protocol)
Byzantine Fault Tolerance Limited (flooding mesh is inherently resilient to node failure — messages take multiple paths; no formal BFT consensus; vulnerable to network congestion with many nodes; hop limit prevents infinite loops)
Signature Ed25519 (for public-key direct messages and admin channel authentication; channel messages use shared symmetric key without per-message signatures)
Permissions Channel-based (primary/secondary channels with shared encryption keys; admin channel with PKI for device configuration; no granular role-based access control beyond channel membership)
Semantic Web Compatibility No
Smart Contract No
Protocol Stack Position
Asset / Value Embedding None — Meshtastic is an open-source LoRa mesh radio project with no native token or economic layer. The project is donation-funded (Open Collective) and operated entirely on volunteer/cooperative principles.
Protocol Maturity / Standardization De Facto Standard (no formal standards body involvement; protocol defined by Protocol Buffer definitions in meshtastic/protobufs repository; versioned releases; wide de facto adoption with ~40,000 active nodes; community-driven development without formal specification process)
Relationships
How this tool connects to other tools and organizations, from relationships reviewed by the OpenHaven data steward. They describe how projects connect, not how good they are.
- Basis for