NHMesh 2026: The Dual-Protocol Infrastructure Strategy

NHMesh is officially transitioning to a dual-protocol infrastructure model. While Meshtastic has built our community's foundation, MeshCore offers unique technical advantages for high-reliability backbone links and resilient off-grid communication.

Our mission for 2026 is to provide a robust physical infrastructure that supports both projects, allowing members to choose the firmware that best fits their specific needs. Whether you are running a mobile node for hiking or a permanent rooftop repeater, our solar-powered sites are being engineered to handle the unique demands of both ecosystems simultaneously.

NHMesh 2026 Roadmap

Our development for the coming year is divided into three primary phases:

Phase 1: Winter / Q1 2026

Foundation and Backend Integration Focus is primarily on backend technology work to ensure our core infrastructure fully supports the MeshCore protocol alongside Meshtastic. Physical build-outs will be minimal during this period.

Phase 2: Spring / Q2 2026

Infrastructure Expansion and Bridging With the return of favorable weather, we will begin a major MeshCore build-out. A primary technical goal is the implementation of Meshtastic-to-MeshCore bridging, allowing seamless communication between users regardless of their chosen protocol.

Phase 3: H2 2026

Regional Mesh Development The second half of the year will focus on northward expansion, establishing regional meshes to connect local communities into a cohesive New Hampshire-wide backbone.

Protocol Comparison

Understanding the differences will help you decide which protocol to use for your specific hardware.

Feature	Meshtastic	MeshCore
Primary Use Case	Community, Mobile, Ad-hoc	Backbone, Fixed Infrastructure, Reliability
Routing	Managed Flood (Dynamic)	Static / Predictive
Ideal For	Hikers, Pilots, End-Users	Repeaters, Solar Sites, Core Links
User Experience	Feature-rich App (iOS/Android)	"Set and Forget" Infrastructure

---

Standardizing the Meshtastic Network: "NHMesh" on Medium Fast

To ensure network reliability as our node density increases, we are moving to Medium Fast as the official default channel preset for the Meshtastic side of the network. Additionally, we are transitioning away from the generic "LongFast" channel name to a custom primary identifier: NHMesh.

Why This Change is Necessary

As a mesh grows, the standard "Long Fast" setting becomes increasingly congested. Transitioning to the NHMesh channel on Medium Fast offers several critical benefits:

1. Higher Throughput: Medium Fast offers roughly three times the data rate (3.52 kbps) compared to Long Fast (1.07 kbps), meaning packets spend significantly less time occupying the airwaves.
2. Reduced Collisions: By shortening the transmission window, we effectively increase the "capacity" of the mesh and reduce the likelihood of overlapping packets.
3. Automatic Frequency Slotting: Using the custom name NHMesh shifts our communication to a unique sub-frequency. This creates a logical barrier that prevents unconfigured or non-local nodes from polluting our optimized backbone.

[!NOTE] Changing to MEDIUM_FAST on Meshtastic can begin at any time, however most infrastructure nodes will be changed on a best effort basis.