PRIVACY BY DEFAULT • SECURITY FIRST

Prove the network exists.
Prove nothing else.

The world's first coverage map that shows real mesh activity without ever revealing node locations, owners, or traffic patterns.

1km grid precision
Ephemeral Node IDs
Aggregate-only telemetry
GLOBAL COVERAGE
187 regions
across 41 countries
ACTIVE NODES (EST.)
12,847 –14,203
fuzzy range • updated live
MESSAGES RELAYED (24H)
2.84 million
aggregate only • no timing leaks
NEEDED REPEATERS
312
Priority gaps identified

Live Coverage Map

1km grid squares • Heatmap density • No pins. No owners. No exact locations.

Active Coverage
Needed Areas
Exact GPS never leaves device
LEGEND
Active coverage (1km grid)
Priority gap / Needed repeater
Click any area to simulate adding coverage
DATA IS AGGREGATED • REFRESHED EVERY ~15 MINUTES • NO INDIVIDUAL NODE DATA EVER PUBLISHED
CORE PRINCIPLE

What the map shows — and what it deliberately never can.

A public map of exact node locations would be an attack surface. This map is engineered to be the opposite: a trust signal that strengthens the network while protecting every participant.

PUBLIC • SAFE TO SHOW
✓
Approximate coverage area (snapped to 1km grid squares)
✓
Node count per broad region (ranges only, never exact)
✓
Total messages relayed (global & regional aggregates, no timing)
✓
Mesh density overlay (heatmap style, no hop lines or paths)
✓
Needed repeater target squares (grid only — “Active” when filled)
NEVER PUBLISHED • HARD REJECTED
✕
Exact node GPS coordinates — physical security risk
✕
Node owner identity or wallet — defeats anonymity
✕
Individual node uptime or stats — fingerprinting / targeting risk
✕
Live traffic timing or patterns — traffic analysis vector
✕
Persistent Node ID across months — long-term tracking
✕
Hop-by-hop paths or RSSI per node — reveals topology

Priority Areas Needing Repeaters

Target 1km grid squares. When covered, status flips to “Active”. No names. No owners.

GRID • 51.48, -0.01
London East • Tower Hamlets
NEEDED
Low mesh density • 3+ repeaters would close major gap for East London events & river communities.
Click to focus on map →
GRID • 40.71, -74.01
New York • Lower Manhattan
NEEDED
High foot traffic area with poor existing coverage. Strong candidate for event & emergency use.
Click to focus on map →
GRID • 52.52, 13.40
Berlin • Mitte & Kreuzberg
NEEDED
Cultural hub with growing community interest. Gap between existing clusters.
Click to focus on map →

How a node contributes to the map — without ever leaking location

Everything happens locally on the device first. The map service only ever sees a 1km grid square + signed aggregates.

STEP 01 — LOCAL ONLY
Device generates ephemeral Node ID
Random 128-bit ID created at boot. Rotates automatically every 30 days. Never reused. No link to wallet or owner.
STEP 02 — LOCAL ONLY
GPS snapped to 1km grid square
Exact coordinates never leave the ESP32. Simple rounding math produces grid ID. Exact location is discarded immediately.
STEP 03
Sign aggregate attestation
Device signs uptime + messages relayed using its private key tied to PLSC device-bound license.
STEP 04
Submit grid + aggregates only
Only grid_id + stats + signature is sent. Map backend aggregates and discards identifiers.
INCENTIVES WITHOUT COMPROMISE

PLSC rewards stay private too.

Coverage and uptime earn PLSC. But the reward system is deliberately designed so the map and the blockchain cannot be correlated to physical locations.

01
Uptime & relay stats are attested locally and submitted directly to the PLSC smart contract — never through the public map service.
02
Rewards are paid to the license holder address. No reliable way to connect a reward payout to a specific grid square.
03
Future: Zero-knowledge proofs for coverage claims so even the aggregator learns nothing about location.