Chapter 1: Introduction — Communicating Without the Internet
The Axiom of Connectivity
Modern life depends on the internet. We trust fiber cables, cell towers, and data centers to carry a message to a friend, a warning to a neighbor, a photo to family. Yet that infrastructure is not always reliable: natural disasters, censorship, war, and ordinary technical failures can sever the chain for days.
MOSA (Mesh Offline Secure Architecture) is the infrastructure that lets people communicate securely when those disruptions occur. It requires no carriers, no base stations, and no internet. It delivers messaging, voice calls, and file sharing over a self-organizing mesh of smartphones, small handheld devices, and local gateways.
Three Trigger Scenarios
Natural disaster: the 1999 Marmara and 2023 Kahramanmaraş earthquakes each caused communication blackouts lasting hours or days.
Political crises: censorship orders, shutdown decisions, or deliberate network cuts.
Remote geography: mountain villages, small offshore islands, conflict zones.
┌─ Şema: MOSA High-Level View ─┐
[Phone A] ◄─BLE─► [Phone B]
│ │
│ ▼
│ [LoRa Gateway]
│ │
│ ◄──FSK long range──►
▼ │
[LoRa Gateway] ──── [Phone C] (3 km away)
│
▼
[Bridge Plugin] ── When internet is available: relay to WhatsApp/TelegramDesign Principles
MOSA is built on four invariant principles. First, everything works offline; the cloud is an optional accessory only. Second, the default behavior is end-to-end encrypted; plaintext never enters the network. Third, no single actor should be a single point of failure; every device can act as both client and router. Fourth, hardware must be cheap and replicable; military-grade security must not require a military-grade budget.
Book Structure
This book describes how MOSA works as an architecture, not a product. The first four chapters cover the physical and protocol layers (BLE, LoRa, FSK). Chapters five through eight cover cryptography and mobile software. Chapters nine through twelve cover hardware. The final chapters cover operations and deployment.
"Do not design technology for disaster day. Design technology that survives disaster day." — MOSA design guide, principle 1
Chapter 2: Mesh Network Fundamentals
From Star to Mesh
Classic wireless communication relies on star topology: devices communicate through a central hub — a base station or Wi-Fi access point. If the hub goes down, the entire network goes down. Mesh networking breaks that assumption; every node is both end user and router. The failure of one point does not cut the network; traffic finds its way around.
[Tablo: Star vs Mesh Topology]
│ Property │ Star │ Mesh │
│ Single point of failure │ Yes (hub) │ No │
│ Scalability │ Hub-limited │ Self-expanding │
│ Resilience │ Low │ High │
│ Setup complexity │ Low │ Medium │
│ Coverage extension │ Fixed │ Dynamic │
Self-Organizing Network Properties
Mesh networks are elegant but demanding architectures. Four canonical problems must be solved: (1) routing — how a packet reaches the destination; (2) collision management — who transmits and when; (3) mobility — how routes update as nodes move; (4) security — how malicious nodes are filtered out.
Routing Basics: Flooding vs Directed
The simplest routing strategy is flooding: every node rebroadcasts every packet. Flooding guarantees delivery but wastes spectrum. Directed routing uses topology knowledge to forward packets toward the destination. MOSA blends both: it floods for neighbor discovery and route requests, then switches to directed forwarding once a path is known.
MOSA's Three Radio Layers
MOSA uses three complementary radio technologies. BLE Coded PHY handles short-range links between phones and handheld devices, typically 10–200 m. LoRa handles long-range backbone links between gateways, reaching 1–15 km. FSK fills the middle tier — higher data rate than LoRa, longer range than BLE — for urban inter-building links and file transfers.
Addressing
Every device carries a dual identity: a 32-bit short ID used for routing between messages, and a 256-bit Ed25519 public key used for end-to-end authentication. If a user has multiple devices, they are bound under a "user ID" header; messages are distributed simultaneously to all active devices.
[Tablo: Address Hierarchy]
│ Layer │ Type │ Size │
│ Device │ Short ID (rotating) │ 32 bit │
│ Device │ Ed25519 key │ 256 bit │
│ User │ User ID │ 128 bit │
│ Group │ Group ID + AES key │ 128 + 256 bit │
"The measure of a mesh network design is not its coverage but its behavior in doomsday scenarios."