Mesh Memory

What Is Mesh Memory?

Mesh memory is the capability that makes Blackout Comms fundamentally different from every other civilian mesh communication system available today.

In a standard mesh network, devices communicate with each other in real time. When a device goes offline — battery dead, powered off, out of range — it disappears from the network. The other devices don't know where it went. They don't know where it was. From the network's perspective, it simply ceases to exist.

Blackout Comms works differently. Every node in a Blackout Comms cluster continuously retains and propagates the last known state of every other device in the cluster. That state includes the device's last known GPS position, heading, speed, and battery level. When a device powers off, that information doesn't vanish — it remains alive in the mesh, carried and shared by every node that's still active. The network remembers what the device last reported, and it keeps that memory available to every cluster member, including ones that come online later.

That is mesh memory.

What the Network Remembers

When any device in your cluster goes offline, the following data is retained and distributed across all active nodes:

Last Known Position: the GPS coordinates of the device at the moment it last communicated with the cluster. Displayed as a pinned location on the Blackout Comms Live map.
Last Known Heading: the direction the device was traveling when it last reported. Tells you not just where it was, but where it was going.
Last Known Speed: how fast the device was moving at last contact. Combined with heading and time elapsed, this gives a coordinator a meaningful search corridor if the device needs to be located.
Last Known Battery Level: the battery percentage at last contact. Tells you whether the device went dark by choice or by necessity - a 4% battery reading tells a very different story than an 87% reading.
Last Known Temperature: temp as reported by the device (if it's capable of measuring temp)
Last Detected Motion: If device is equipped with doppler-based motion / presence sensor
RF Signal Strength: the measured signal strength between every observed device pair in the cluster, in both directions. Updated continuously as devices move and conditions change. Used by Blackout Comms Live to render connection lines and by the firmware to evaluate link quality for routing decisions.
Link Reliability: the consistency and dependability of every RF link in the cluster, tracked directionally. A link that delivers 95% of packets is treated very differently from one that delivers 60%, even if their signal strength readings are similar. This reliability data is part of what the firmware uses to prefer robust paths over merely available ones.

All of this data is encrypted at all times. It is never transmitted or stored in plaintext. Only devices within your authorized cluster can read it.

The Network Knows How Well It's Connected

Most mesh networks route messages opportunistically — a packet arrives at a node, and that node forwards it to whoever it can reach, hoping it eventually finds its destination. The network has no persistent knowledge of which paths are reliable, which links are weak, and which routes are most likely to deliver a message successfully. Every routing decision is made with incomplete information.

Blackout Comms takes a fundamentally different approach.

RF connectivity data - the signal strength and link reliability between every pair of devices in the cluster, measured in both directions - is part of what mesh memory carries and propagates. Every node in the cluster continuously monitors the quality of its connections to every other node it can reach: how strong the signal is, how consistently messages are getting through, and whether the link performs equally well in both directions. That connectivity data is not kept locally. It is distributed through mesh memory to every node in the cluster, just like location data and trust credentials.

The result is that every device in your cluster carries a continuously updated picture of the entire network's RF topology - not just its own immediate neighbors, but the connection quality between every pair of devices the mesh has observed. This is the data that powers the connection lines you see in Blackout Comms Live: their presence, their color, and their weight all reflect real measured link quality propagated through the mesh.

But the more significant application is what the firmware does with that information when it needs to move a message between two devices that cannot reach each other directly.

How a Device Joins an Operation Already in Progress

This is where mesh memory becomes genuinely remarkable — and where it has no parallel in any competing system.

Imagine a Blackout Comms communicator that has been powered off since before an operation began. It was not present when supply runners left. It did not receive any of the broadcasts from the field. It has no knowledge of what happened during the operation.

You power it on.

Within moments of joining the cluster, that device receives the full retained state of every other cluster member — active and inactive. It knows the last known positions of every device that has communicated with the cluster. It has received every broadcast message that was sent while it was offline. It has the same operational picture as a device that was present for the entire operation.

This is not a sync from a server. There is no server. This is the mesh itself carrying that knowledge, node to node, and delivering it to any new member that joins. The cluster is the database.

Why This Matters in Practice

For supply run coordination: A runner goes quiet — device powered off to conserve battery, or deliberately dark for operational security reasons. The coordinator watching Blackout Comms Live doesn't lose them. Their last known position, heading, and speed remain on the map. The coordinator knows where they were, which direction they were going, and how much battery they had. That's a decision framework, not a blank screen.

For search and rescue: A hiker's device dies in the backcountry. Any other device in the cluster — including one that wasn't even online when the hiker's device last reported — can receive the last known position the moment it joins the cluster. Search begins from a known point, not a general area.

For distributed teams: A new team member joins the operation mid-way. Their device powers on and immediately has the full picture — every active node, every offline node's last known state, every broadcast from the operation so far. They are immediately operational. No briefing. No catch-up. No gaps.

For long-term caching: A supply cache is established at a remote location with a communicator. The communicator is powered off after broadcasting confirmation of the cache. Weeks later, any cluster device — including ones that have never been near the cache — powers on and knows exactly where it is. The cluster remembered.

Encrypted at Every Stage

Mesh memory is not just persistent — it is private.

Every piece of retained state data is encrypted before it is transmitted between nodes. The last known position, heading, speed, and battery level of every device in your cluster are encrypted at all times — in transit, at rest within the mesh, and when delivered to a newly joined device.

This means that even if someone intercepts the radio traffic from your cluster, they cannot read what the network knows. The positions of your people, the routes your runners took, the locations of your caches — none of it is readable without authorization from within the cluster.

No plaintext positions. No readable broadcasts. No exposed operational data. The network's memory belongs only to the people inside it.

Why No Other System Has This

Meshtastic, GoTenna, and every other civilian mesh communication platform operate on the same fundamental model: real-time relay. Devices pass messages and position data to each other as long as they are online. When they go offline, that data is gone. The network has no persistent memory of what a device last reported, and no mechanism for delivering historical state to devices that join later.

This is not an oversight. It is a fundamentally different architectural choice. Building a distributed, encrypted, propagating memory layer into a mesh network — one that survives node failures, powers-off, and new arrivals — requires a different approach to how the firmware manages state across the cluster.

Blackout Comms was built with this capability from the ground up. It is not a feature that can be added to existing mesh systems through a firmware update. It requires the entire network protocol to be designed around the assumption that knowledge must persist and propagate, not just pass through.

That is why no other system has it. And that is why, in a real grid-down scenario where devices go dark and people need to stay found, Blackout Comms is in a category of its own.

Mesh Memory + Blackout Comms Live

The Blackout Comms Live Android app makes mesh memory visible. Connect any Android device to your Blackout Comms communicator via Bluetooth and you have a live map of your entire cluster - active nodes moving in real time, offline nodes pinned at last known position, mesh graph lines showing the live connections between every device.

The connection lines visible in the Mesh Graph overlay are not decorative. Each line represents a real, measured RF link between two cluster devices - its presence, strength, and reliability all drawn from the connectivity data that mesh memory carries across the cluster. A strong, reliable direct link looks different from a marginal or intermittent one. Nodes that are communicating through intermediate hops are shown differently from nodes in direct contact. The map you are looking at in Blackout Comms Live is a live rendering of the cluster's actual RF topology - the same topology the firmware is consulting in real time to route messages through the network as efficiently and reliably as possible.

When a node goes dark, its icon remains on the map. Tap it and see its last known heading, speed, and battery. Watch the timestamp telling you exactly when it last reported. When it comes back online, the icon animates back to life and resumes live tracking.

Mesh memory is what makes that possible. And it is encrypted, distributed, and entirely independent of any infrastructure outside your cluster.

Summary

Mesh memory means your network never forgets where your people were, never loses track of who belongs, and never requires two devices to have physically met in order to trust each other. A device that joins late arrives fully informed — positions, broadcasts, certificates, and keys — ready to operate immediately. All of it encrypted. None of it dependent on infrastructure outside your cluster.

No cell towers. No internet. No servers. No central authority. No other system.

This is Blackout Comms.