MeshCore

What is MeshCore?

MeshCore is a next-generation mesh networking protocol that pushes the boundaries of what’s possible over LoRa radio links. While Meshtastic pioneered the open-source LoRa mesh space, MeshCore takes a different approach to solve some of the hardest problems in low-bandwidth mesh networking.

MeshCore is designed from the ground up for efficiency — every byte matters when you’re communicating at kilobits per second over radio. The protocol uses optimized binary encoding, intelligent flood management, and room-based messaging to deliver reliable communication even on congested or low-quality links.

MeshCore isn’t a replacement for Meshtastic — it’s a complementary evolution. Different tools for different aspects of the mesh networking challenge.

Core Design Principles

Managed Flood Mesh

Traditional mesh flooding rebroadcasts every packet through every node. This works well for small networks but can create congestion as meshes grow. MeshCore implements managed flooding — intelligent packet routing that:

Limits unnecessary retransmission — nodes make smart decisions about whether to rebroadcast
Reduces channel congestion — critical for dense urban networks like Orlando
Preserves battery life — fewer transmissions means less power consumption
Maintains reliability — important packets still reach their destinations

Binary Protocol Efficiency

MeshCore uses compact binary encoding for all protocol messages:

Smaller packets = faster transmission = less air time
Efficient headers minimize overhead per message
Optimized for the 256-byte LoRa payload constraint

Room-Based Messaging

Instead of simple broadcast channels, MeshCore introduces rooms — encrypted group conversations with membership management:

Create named rooms with unique encryption keys
Invite specific nodes/users to rooms
Messages only propagate to room participants
Multiple concurrent rooms per node
Room history and message ordering

This model is closer to how people actually communicate — in groups, with context, with membership control.

Hardware Compatibility

MeshCore runs on the same hardware as Meshtastic — ESP32 or nRF52 boards with LoRa radio. This includes:

Heltec WiFi LoRa 32 (V2/V3)
LilyGO T-Beam (all versions)
RAK WisBlock (4631 core)
Seeed Wio Tracker 1110
And most other Meshtastic-compatible boards

Technical Architecture

Protocol Stack

┌─────────────────────────────┐
│   Application Layer         │  Rooms, messages, telemetry
├─────────────────────────────┤
│   MeshCore Protocol         │  Managed flood, routing
├─────────────────────────────┤
│   Encryption Layer          │  AES-256, per-room keys
├─────────────────────────────┤
│   LoRa Physical Layer       │  915 MHz ISM, spread-spectrum
└─────────────────────────────┘

Packet Types

MeshCore defines several efficient packet types:

TEXT — Encrypted text messages within rooms
ACK — Delivery acknowledgment
ANNOUNCE — Node presence and capability broadcast
POSITION — GPS coordinates and altitude
TELEMETRY — Sensor data (battery, environment)
ROUTE — Mesh topology information

MeshCore vs. Meshtastic

Both platforms serve the mesh networking community, but they optimize for different things:

Aspect	Meshtastic	MeshCore
Maturity	Established, large community	Newer, rapidly developing
Routing	Simple flood mesh	Managed flood with intelligence
Messaging	Channels with PSK	Room-based with membership
Protocol	Protocol Buffers	Compact binary encoding
Ecosystem	Full app suite (iOS/Android/Web)	Growing tooling
Best for	General mesh, GPS tracking, simplicity	Dense networks, efficiency, groups
Congestion handling	Hop limits, duty cycle	Intelligent retransmission

When to Use Each

Choose Meshtastic when:

You want the easiest setup experience
You need polished mobile apps
GPS tracking is a primary use case
You’re building a small-to-medium network
Community support matters most

Choose MeshCore when:

You’re building a dense urban network
Channel congestion is a concern
You want room-based group messaging
You care about maximum protocol efficiency
You enjoy cutting-edge technology

MeshCore in Orlando

MeshCore’s managed flooding is particularly well-suited for Orlando’s mesh ambitions:

Dense suburban areas benefit from reduced congestion — not every node needs to rebroadcast every packet
Room-based messaging lets neighborhood groups, emergency teams, and social groups communicate without stepping on each other
Efficient protocols mean the limited LoRa bandwidth goes further, supporting more nodes on the same channel
Dual-stack operators can run both Meshtastic and MeshCore nodes, covering both ecosystems

As the Orlando mesh grows from dozens to hundreds of nodes, MeshCore’s congestion management becomes increasingly valuable. It’s an investment in the network’s scalability.

Getting Involved

MeshCore is actively developed and welcomes contributors:

MeshCore Website
MeshCore GitHub
MeshCore Documentation
Community channels and forums — check the website for current links

The MeshCore community is smaller but technically deep. If you’re the kind of person who reads RFCs for fun, you’ll feel right at home.