LoRa Mesh Networks and the Laws of Network Value

Meshtastic, MeshCore, and the Allee Threshold — an Evidence Review for a LoRa Mesh Community by Perplexity for The MeshDirectory.org

Research date: October 24, 2026. Scope: publicly available studies, protocol documentation, operator reports, and community analyses through October 2026. “All studies” is operationalized here as the material discoverable across academic, technical, and community sources; no claim of exhaustive coverage is made. arXiv items are preprints unless otherwise verified.

Executive Summary

The reviewed evidence suggests that LoRa mesh growth depends on useful local connectivity, relevant participants, infrastructure continuity, and shared-airtime management — not worldwide node count alone. It does not establish a LoRa-specific quadratic or exponential valuation law, a universal node ceiling, or a measured Allee threshold. For a startup, the named theories are useful hypotheses for testing deployment strategy, retention, reliability, and unit economics; they are not substitutes for those measurements.

The strongest findings, with confidence labels:

Node count alone is an inadequate valuation or performance model for a LoRa mesh (high confidence). Capacity depends on message generation rates, packet airtime, retransmissions, topology, interference, firmware, and regulation — not on registrations (MeshAtlas). Theoretical work on multihop wireless networks shows per-node throughput declining as networks grow under stated assumptions (Gupta–Kumar, via Berkeley EECS-2013-230), and community-observed congestion in dense Meshtastic deployments is consistent with that direction — but reported node-count guidelines (~40–60 nodes) are deployment-specific heuristics from firmware behavior and operator guidance, not universal limits.
Local participation plausibly creates a critical-mass problem (moderate confidence, hypothesis). Coverage tests with no nearby nodes received nothing (raspberry.tips); a two-radio network can still deliver substantial value to an existing pair or work team without any wider network. The reviewed material does not identify a numerical Allee threshold or demonstrate an Allee-type adoption-and-churn process for Meshtastic or MeshCore — that is a hypothesis a pilot must test with longitudinal activation and retention data.
Congestion and shared-medium contention are real, observed phenomena (high confidence). Bay Area operators report 15–20% channel utilization and congestion-driven migration to a different preset (r/meshtastic); a production packet capture estimated at least 11.6% regional channel utilization in an evening hour including observed relaying, with separate validation work measuring peaks near 36% (Loomwave case study).
MeshCore’s architecture is a deliberate bet on separating user adoption from relay load (documented design fact; the capacity benefit is a claim, not a measurement). The project’s documentation states that companion radios “don’t relay traffic for anyone else” and repeaters “are the only nodes that actually forward other people’s traffic,” with flood-once-then-direct routing and support for up to 64 hops (MeshCore FAQ, MeshCore scaling analysis); whether it scales further in practice is not independently measured in the reviewed material.
Adjacent mesh products illustrate crisis-driven adoption, consumer-product discontinuation, and possible retention risks (documented events; causes not established). FireChat saw crisis-driven spikes (~500,000 downloads during the 2014 Hong Kong protests) but stopped updates in 2018 and died by 2020; a post-mortem attributes this to having “no business model behind a tool people only opened in emergencies” (rip.so) — an interpretation, not a demonstrated cause. goTenna discontinued its consumer line in 2024 while its professional/government line continues (Nelos). Download spikes alone do not demonstrate sustained usage or a viable business model, and the reviewed evidence does not establish the causes of these business outcomes.
Surviving community networks professionalized operations (high confidence). guifi.net (35,000 nodes, two decades) runs a common-pool-resource governance model in which paid professionals are contractually obligated to contribute to the network — with annual turnover of millions of euros and dozens of direct jobs (SIGCOMM guifi paper); NYC Mesh recently received an $898,035 municipal grant and serves 1,500+ households (NYC Mesh).

Evidence Landscape

No direct empirical tests of Metcalfe’s, Reed’s, or Sarnoff’s laws against Meshtastic or MeshCore were found in this review. What exists falls into three classes:

Evidence class	Examples
Research studies and preprints	Zürich field experiments (PDR/range), a Budapest multi-hop simulation, a gateway-free peer-to-peer LoRa mesh design, LoRa mesh scalability analysis for linear infrastructure, theoretical multihop capacity limits, empirical fits of value laws to internet platforms; arXiv items are preprints and the publication status of repository-listed items was not verified
Primary operational evidence	Meshtastic firmware behavior and DEF CON stress test, MeshCore protocol design and map statistics, production packet captures
Community observations	Bay Area congestion management, Russian community growth, regional buildout reports, adoption commentary

Measurement caveats that recur: map-visible nodes, downloads, sales, and active users are different quantities; map counts include only position-sharing nodes with internet links and can include stale entries, so they are neither strict lower bounds on current activity nor activity counts (MeshAtlas, raspberry.tips). Community sources are anecdotes with self-selection bias; vendor and competitor content is labeled as such.

Theories Tested Against the Evidence

Sarnoff’s Law — broadcast value

The law: the value of a one-to-many broadcast network is proportional to the number of people reached, $V = N$ V=N, with value to advertisers rising with audience size (MITRE Value of Networking).

What the evidence supports: a production capture of a North Georgia Meshtastic network found roughly 89% of unique packets were network self-description (NodeInfo 42.9%, Position 26.7%, Telemetry 18.9%) and 1.3% human text locally, 2.0% regionally — the authors characterize the channel as “full of presence, not messages” (Loomwave). That is a traffic-composition finding from one metro deployment on one preset; it does not by itself establish that Meshtastic economically follows Sarnoff’s Law or that text messages carry the most user value.

A relevant nuance: in a broadcast channel, additional passive receivers do not consume additional airtime — additional transmitting sources and relays do. So a Sarnoff-style information feed (telemetry, alerts) grows its audience more cheaply than a peer-to-peer messaging load, which is a design consideration, not a valuation result.

Metcalfe’s Law — peer-to-peer value

The law: network value based on possible one-to-one connections, $V_N = n(n-1)$ VN=n(n−1), treating all connections as equally valuable (MITRE).

What the evidence shows, in two separate threads:

Throughput thread. Theoretical results (Gupta–Kumar, validated experimentally for 802.11-based meshes under stated assumptions about traffic, geometry, and interference) show per-node capacity declining toward zero as a multihop wireless network grows, with channel contention the primary mechanism (Berkeley EECS-2013-230). Community observations point the same direction: Meshtastic’s firmware lengthens telemetry and position intervals in networks with more than 40 active nodes, and developers describe LongFast as overwhelmed with more than about 60 nodes in close proximity (raspberry.tips); auto-generated codebase documentation describes bottlenecks beyond ~60 devices and channel utilization above 65% as congestion requiring intervention (DeepWiki); a MeshCore-oriented technical analysis puts the failure region above about 50 active nodes in a single collision domain (MeshCore scaling analysis). These are deployment-specific heuristics and opinions from different sources, not a validated universal ceiling. Larger deployments have been reported — the Bay Area across multiple presets, DEF CON at 2,000+ nodes — but the reviewed sources do not establish the mechanism by which they function, and different presets should not automatically be treated as independent collision domains.

Value thread. Declining per-node throughput does not disprove Metcalfe’s claim about aggregate economic value — they are different dependent variables. The theoretical critique that does bear on value is Odlyzko and Tilly’s: N² assumes all possible connections are equally valuable, which is false — interaction value falls with distance and follows roughly Zipf-distributed ranks, yielding $V \approx n \log n$ V≈nlogn as their proposed correction, and the historical resistance to network interconnection is inconsistent with the huge gains N² implies (Odlyzko & Tilly). A metro LoRa mesh is an extreme case of their locality argument: reachable partners are bounded by RF physics.

Verdict: Node count alone is an inadequate performance and valuation model for a LoRa mesh. Congestion can offset connectivity benefits; the resulting value curve for a specified usefulness metric under specified traffic assumptions is plausibly an inverted-U per collision domain, but that curve has not been measured here — it is a hypothesis.

Reed’s Law — group-formation value

The law: value including group formation, $V_N = an + bn^2 + c\,2^n$ VN=an+bn2+c2n with $a \gg b \gg c$ a≫b≫c, the subgroup count $2^n$ 2n dominating at scale (MITRE).

What the evidence shows: one empirical study of network value (US platforms 2002–2021, value proxied by annual revenue) characterizes the original Reed formulation $2^N$ 2N as an upper bound that has never been observed in real-network data. Its model selection between a generalized exponential $V \propto e^{\rho N}$ V∝eρN and a power law was generally inconclusive (an exponential pattern in the US, a power law elsewhere), with the estimated $\rho$ ρ extremely small (~10⁻⁹), which the authors interpret as the probability that a user determines a new marketable group being extremely small (Nature Scientific Reports). That study concerns internet platforms, not mesh networks. In LoRa meshes specifically, MeshCore’s room-server firmware had roughly three serious bugs that hampered room adoption, and room usage “remained relatively rare” in its first year (MeshCore Year in Review) — a product-adoption observation, not a refutation of group-forming effects.

Verdict: Possible group count is not demonstrated economic value, and shared airtime constrains simultaneous group activity. Active, valuable groups could improve retention; treat group features as retention levers, not as a value-scaling law.

The Allee Effect and the Allee Threshold

The ecological definitions: an Allee effect is a positive association between average individual fitness and population size over some finite interval; component Allee effects on fitness components can produce a demographic Allee effect (positive association between per-capita growth rate and population size); effects are strong when they create a critical population size below which the population cannot persist, and weak when they do not (Nature Scitable: Allee Effects).

The business mapping: a16z maps this to networks — below a tipping point, shrinking value drives churn that compounds (“as the user base shrinks, each remaining user is more likely to leave”), with carrying capacity (saturation) as the upper bound; their density framing explicitly favors small dense networks over large sparse ones (a16z: Beyond Metcalfe’s Law). The economics literature formalizes the same structure as critical mass: with strong network externalities, fulfilled-expectations demand can slope upward at small sizes, so small positive networks are not stable equilibria — the network “either has substantial coverage or does not exist” (Economides: Critical Mass and Network Evolution).

What the LoRa evidence supports: a German reviewer’s two-node setup with the nearest mapped node 20–30 km away received no foreign nodes on an indoor antenna (raspberry.tips) — a coverage limitation, not evidence of participation-driven decline. Russian operators describe a network that “once had no one on it” before reaching 190 nodes (nemoskva.net) — growth, not an identified threshold. Adjacent mesh products show the churn-compounding pattern: “when usage falls, the network gets worse for everyone, which makes churn compound quickly” (Sacra) — analyst commentary, not measured retention data.

Verdict: Local connectivity and participation create a plausible critical-mass problem for LoRa meshes. This review did not identify a numerical Allee threshold or establish an Allee-type adoption-and-churn process for Meshtastic or MeshCore. Note also the critical distinction: the congestion region (~dozens of active nodes per collision domain, per the sources above) is a capacity limit, not an Allee threshold — though the two can interact if congestion-driven churn drops a network back below its usefulness floor. A pilot would need longitudinal activations, retention, and departures against local participation to test the hypothesis.

Other Notable Frameworks

Framework	What it says about LoRa meshes	Evidence and limits
Odlyzko $n \log n$ nlogn	Connection value is local and rank-distributed; most theoretical pairs are never used	Theory (Odlyzko & Tilly); consistent with the 89% presence-traffic composition finding, which does not prove it
Gupta–Kumar capacity	Per-node throughput declines with multihop network growth under stated assumptions	Theoretical + 802.11 experimental validation (Berkeley EECS-2013-230); not a LoRa measurement
Commons / congestion	The shared channel is a common-pool resource; default-on telemetry is overuse by design, not user misbehavior	Loomwave traffic mix; EU firmware duty-cycle defaults (10% rolling hourly for EU_433/EU_868) are a legal transmitter limit, not a capacity target (MeshAtlas)
Empirical value-law fits	Real platforms fit $V \propto N^\gamma$ V∝Nγ with $\gamma$ γ often above 2; original Reed $2^N$ 2N described as an unobserved upper bound, with generalized exponential vs power-law fits generally inconclusive	Internet platforms 2002–2021, revenue proxy (Nature Scientific Reports); not mesh networks
Coverage-edge behavior	PDR does not degrade gracefully — it falls off a cliff at maximum range	Zürich tests: ~85% PDR at 1,250 m then abrupt zero (arXiv 2509.22568, preprint)
Infrastructure economics	Who funds and maintains repeaters determines survival	guifi.net CPR model with contractual professional obligations (SIGCOMM)

Growth and Collapse Cases

Meshtastic

Scale: 9,806 map-visible nodes worldwide (Oct 2, 2026), 3,235 on EU_868; major European cities show 15–58 nodes within 30 km (raspberry.tips). The Bay Area community reported ~650 active nodes across presets, with 246 on one MediumSlow list (r/meshtastic).
Stress test: DEF CON 2025 drew 2,000+ nodes — described as the largest known Meshtastic network, usable after routing improvements; the event exposed NodeDB spoofing and the ~100-node NodeDB cycling limit (Meshtastic blog).
Congestion management: Bay Area operators moved to MediumSlow (a higher-data-rate preset than LongFast, per the preset table in DeepWiki) and adopted norms like ~2-hour minimum message spacing; typical LongFast utilization reported at 15–20% (r/meshtastic). Note the region “scales” by splitting into separate presets/domains — an observed community response, not a formally documented scaling mechanism.
Crisis-driven demand: Russia’s community roughly doubled (5,000→9,000 Telegram subscribers) after October 2025 amid mobile-internet outages; even enthusiasts call it “a very unreliable means of communication” for daily use (nemoskva.net).
Field performance (preprints and studies): Zürich tests found 868 MHz LongFast delivering 92% PDR to ~1.27 km with an abrupt cliff beyond (arXiv 2509.22568); a Budapest simulation found high delivery reliability with latency and energy rising predictably per hop (BME repository); a Colombian campus deployment sustained a 2.47 km link at −110 dBm RSSI with a 4-node mesh (arXiv 2605.20379).

MeshCore

Trajectory: map grew from 1,000 nodes (first month, May 2025) to 5,000 (summer 2025), 10,000 (December 2025), 30,000 (April 2026) (MeshCore blog); more than 40,000 identified users reported by mid-2026 (LWN.net). First-year daily activity: ~4,500 unique active nodes, ~4,400 public messages, ~80K unique packets (MeshCore Year in Review). Map registrations are cumulative observations and are not current-activity counts.
Architecture: the project’s documentation states that companion radios “don’t relay traffic for anyone else” and that repeaters “are the only nodes that actually forward other people’s traffic,” with flood-once-then-direct routing that reuses learned paths and a 64-hop maximum (versus Meshtastic’s maximum of 7 hops, default 3) (MeshCore FAQ). A technical analysis claims roughly 60% airtime savings for a 10-message conversation versus flooding every message (MeshCore scaling analysis), and retailer commentary describes the same role split (hexaspot). Caveats: adding companions adds no relay-capable devices, but their originated messages still consume airtime and repeater forwarding; more repeaters do not proportionally add capacity, since placement and shared-channel contention still bind. Adoption is reported as especially strong in the Netherlands, with hundreds of community repeaters (hexaspot) — retailer content.
Key-person concentration: Victoria, Australia’s statewide coverage was built largely by a handful of volunteers placing mountain-top repeaters (MeshCore Year in Review); Australian growth continues via volunteer solar hilltop infrastructure (WIA).
Governance risk materialized: a March 2026 trademark filing by early promoter Andy Kirby, alongside his proprietary MeshOS app and website changes, produced an open dispute with the core developers, who rebuilt the project’s public-facing site (LWN.net) — a documented governance and identity-control risk for community mesh projects, distinct from any network collapse.

Other LoRa Mesh Systems

A gateway-free peer-to-peer LoRa mesh design study (ESP32/SX1276, ~$20 nodes) demonstrated multi-hop range extension with a 255-node addressing limit tied to its routing-table memory — an implementation constraint, not a medium limit (PMC8272137). Research on LoRa meshes for linear infrastructure derives scalability and coverage bounds under EU duty-cycle constraints (1% for the studied band) and proposes RSSI/hop-aware routing (Glasgow eprints). These studies address throughput and coverage, not network-value laws.

Collapse and Survival Cases (Adjacent Mesh Products)

Case	What happened	Source quality

Case	What happened	Source quality
FireChat (2014–2020)	~500,000 downloads in days during the 2014 Hong Kong protests; 131,000 sessions in Catalonia (2015); updates stopped 2018; cloud services off by February 2020. Interpretation: “no business model behind a tool people only opened in emergencies”	Timeline from rip.so post-mortem (rip.so); the cause of disappearance is an attribution, not established by the fetched evidence (fromjason.xyz)
goTenna (consumer)	Consumer Mesh line support discontinued in 2024; company had announced the professional Pro line in 2017 and raised $24M in 2019 for the public-sector move; acquired by Forterra in October 2025; Pro line continues	Competitor-written guide (Nelos)
Bridgefy	Downloads reportedly rose almost 4,000% during the 2019 Hong Kong protests; hundreds of thousands of new downloads within hours of Myanmar’s 2021 coup; comparable surges reported in Belarus, Thailand, Nigeria, Zimbabwe, Lebanon	Journalism (ORF)
Mesh messaging category	Analyst view: retention, not the radio link, is the bottleneck; “survival in the category depends more on habit density than novelty”; survivors narrow their use case or become SDKs	Analyst commentary, no retention data (Sacra)
guifi.net (survivor)	35,000 nodes over two decades; common-pool-resource governance; professionals contractually obligated to contribute; millions of euros annual turnover and dozens of jobs	Research paper (SIGCOMM, Resilient Comms)
NYC Mesh (survivor)	Serves 1,500+ households; $898,035 municipal grant (July 2026) to connect at least 500 low-income households and hire first full-time staff	Press release (NYC Mesh)
Community networks, pre-positioning	Cross-cutting lesson from the case-study hub: pre-existing infrastructure outperforms emergency deployment; community ownership supports sustainability	Case-study hub (Resilient Comms)

LoRa Mesh and The Laws of Network Value