MeshCore

P2P Infrastructure

A lightweight, open-source (MIT) C++ library and firmware ecosystem enabling multi-hop mesh networking over LoRa and other packet radios without internet or cellular infrastructure. Designed for developers building custom embedded communication systems (off-grid messaging, emergency response, IoT sensor networks, tactical communications). Optimized for long-distance multi-hop reliability, low power consumption, and ESP32-class hardware. Three firmware roles: Companion (personal messaging node), Room Server (persistent message store), Repeater (relay/router). Growing rapidly in Europe (868 MHz ISM band, license-free).

Fully P2P Community Low capture risk

Details

License MIT
Dev Status WIP
Owner meshcore-dev (Andy Kirby, primary developer / maintainer); community-driven with no institutional backing identified
Country UK
Start Year 2024
Stack C, PlatformIO build system, Flutter, Bluetooth Low Energy for device-phone pairing, WebSerial, LoRa radio hardware
Funding Community
Last Investigated Mar 10, 2026

Use Case Domains

Communication Platform Evolution & Sovereignty

Affordances

Works offline / mesh End-to-end encrypted

P2P Infrastructure Attributes

P2P Architecture Fully decentralized mesh — each node is peer and potential relay; three node roles: Companion (endpoint), Room Server (message store), Repeater (relay); no central server required; network self-heals via alternative routing
Overlay Network None — operates directly over LoRa radio layer; no IP overlay; no internet dependency
Content Addressing No — messages addressed by node unique address (not content hash)
Local-First Yes — fully offline by design; no internet connection required; Room Server enables store-and-forward for delayed delivery when recipients are offline
E2EE Yes — end-to-end encrypted; repeater nodes relay encrypted packets without ability to read content; only intended recipient can decrypt
Byzantine Fault Tolerance No formal BFT — mesh routing self-heals around failed nodes; no cryptographic consensus
Signature Implicit (via E2EE key pairs per node/device); unique node address for routing
Permissions MIT License — open; no access control in protocol beyond encryption (recipient-keyed); Room Server and Repeater management via Remote Management feature in mobile app
Infrastructure Function Off-grid mesh radio networking — multi-hop LoRa message relay; emergency/disaster communication; IoT sensor data relay; tactical communication; outdoor/remote area messaging
Threat Model Designed for: infrastructure outage (no cellular/internet); surveillance/monitoring of communications (E2EE); range limitations (multi-hop relay extends coverage). Not designed for: high-bandwidth; adversarial RF jamming; quantum-resistant crypto; anonymity (node addresses are identifiers)
Volunteer / Node Model Community-run repeaters and room servers (volunteer hardware); companion nodes are user-owned personal devices; no incentive mechanism — entirely altruistic node operation
Traffic Visibility Metadata partially visible — node addresses and hop routing visible to relay nodes; message content E2EE; GPS location sharing is user-controlled (opt-in)
Active Deployment Scale Rapidly growing — European community expanding significantly on 868 MHz ISM band; US deployment smaller; specific node count not publicly tracked; dozens to hundreds of repeater nodes in UK/Europe as of early 2026