Skip to main content
Pitch In Subscribe

MeshCore Protocol Overview

MeshCore is ana open-sourceLoRa mesh networking protocolplatform builtdeveloped by Scott at Ripple Radios. This overview is based on verified information from the official MeshCore documentation, FAQ, and source code.

What Makes MeshCore Different

Most LoRa radio hardware. It was designed as a next-generation alternative to flooding-based mesh protocols,platforms prioritizinguse efficient routing, battery life, and reliable message delivery.

The core idea: path discovery overpure flooding

Many mesh protocols work by flooding: when a message is sent,— every devicenode inre-broadcasts theevery networkmessage. rebroadcasts it, and the message eventually reaches (or fails to reach) its destination. This is simple but wasteful — it generates heavy radio traffic and drains batteries.

MeshCore instead uses path discovery: before sending a message,flood-first, direct-route-after approach:

    The first message to any destination is flood-routed (all repeaters in range re-broadcast) The destination returns the path it identifiesreceived anthe efficientflood routethrough from(PAYLOAD_TYPE_PATH senderpacket) All subsequent messages to recipient,that thendestination transmitsuse alongdirect thatrouting, embedded with the specific repeater path only.— only those repeaters forward it

    This means:dramatically reduces channel utilization in busy networks once paths are established.

    Encryption

    • LessSymmetric redundantencryption: radioAES-128 traffic(ECB onmode)
    Message authentication: HMAC-SHA256 (2-byte truncated, encrypt-then-MAC) Key exchange: ECDH via X25519 (Ed25519 identity keys transposed) Identity signing: Ed25519 — advertisements signed to prevent spoofing

    Firmware Types

      Companion — your personal node; connects to the networkMeshCore app via BLE, USB, or WiFi SignificantlyRepeater lower— powerinfrastructure consumptionnode; forwards messages, no user interface MoreRoom reliableServer delivery,— especiallystores onand busydelivers missed messages; hosts community "rooms"

      Frequency

        USA/Canada: 910.525 MHz, SF7, BW 62.5 kHz (as of October 2025) EU/UK: 868 MHz band Australia/NZ: 915 MHz band

        Key Capabilities

          Room Servers provide message store-and-forward (last 32 unread messages per client) Path hash modes allow tuning for mobile vs. fixed repeater networks BetterRegional scalabilityscoping asvia ISO country codes prevents cross-region interference 50+ supported devices across the numberRAK ofWisBlock, nodesHeltec, growsLilyGo, and Seeed ecosystems

          EncryptionApp and Tools

            Android/iOS app by Liam Cottle: Google Play (com.liamcottle.meshcore.android) / App Store (id6742354151) Web app: app.meshcore.nz Flasher: flasher.meshcore.io Config tool: config.meshcore.io Python CLI: github.com/fdlamotte/meshcore-cli

            PrivateSource: messages inOfficial MeshCore are end-to-end encrypted by default using AES-256. Only the intended recipient can decrypt the message — not intermediate nodes relaying it, not the network operator, not anyone else. Public channel messages are visible to all nodes in range.

            Self-healing

            If a relay node goes offline, MeshCore automatically discovers an alternative path. There is no single point of failure. The network adapts to changes in topology without any manual intervention.

            Technical specifications

            ParameterValue Frequencyrepository (US/Canada)915meshcore-dev/MeshCore), MHzFAQ, ISMsource bandcode, (license-free)and ModulationLoRameshcore.co.uk. (LongVerified Range) EncryptionAES-256 (private messages, default) Data rate0.3 – 50 kbps (configuration dependent) Transmit powerUp to 1 watt (FCC Part 15 compliant) TopologyMesh with path discovery routing 2026-05-03.
            Back to top