Meshtastic patch preserves node identity during 2.7 to 2.8 upgrades

A Meshtastic firmware pull request opened on July 3 aimed at a problem every mesh operator notices fast: a radio that comes back from an upgrade should not suddenly look like a stranger. The open change in meshtastic/firmware is titled “fix: preserve established NodeNum across 2.72.8 upgrade (gate createNewIdentity),” and the patch is aimed at keeping an established NodeNum intact instead of letting the device generate a fresh identity during the upgrade path.

That matters because Meshtastic treats identity as a live part of the network, not just a label in a settings screen. The project’s security docs say node identity uses Trust On First Use, so the first public key heard for a given NodeNum is the one bound to that node going forward. Each node also has its own public-private key pair, and direct messages are encrypted and signed with that identity. If an upgrade changes the NodeNum unexpectedly, maps, contacts, message history and any external tracking built around a specific radio can all fall out of sync at once.

The timing also fits a wider 2.8 transition. GitHub’s Meshtastic firmware pull-request list shows another open item called “Develop 2.8 merge to master,” which signals that the next major line is actively moving through the repo. Meshtastic’s 2.7 preview post, published June 21, 2025, described 2.7 as a preview and “not quite production-ready,” a reminder that the edges of firmware transitions are where identity bugs tend to surface.

Meshtastic has already run into related state-preservation problems elsewhere. In v2.7.14, PR #8292 introduced an option to preserve favorite nodes on NodeDB reset. Another feature request asks to preserve old keys after a device reset because previously learned nodes can get stuck with old keys when a device is wiped and rejoined. Taken together, those changes show a consistent pressure in the project: keep the node you already know, keep its keys aligned, and do not make a router, tracker or handheld behave like a new radio just because the firmware moved forward.

For operators with rooftop nodes, vehicle relays, trail gear or off-grid handhelds, that is the kind of upgrade fix that prevents a lot of cleanup later. A patch that blocks createNewIdentity during the 2.7 to 2.8 jump keeps the mesh from losing track of itself at the exact moment it should be getting more stable.