# Mesh Network Deployment Guide # NodeZero --- ## Overview This document covers the deployment, configuration, and operations of the NodeZero mesh network across , . --- ## 1. Network Design ### 1.1 Coverage Plan municipality covers ~75 km2 (urban center ~12 km2). **Zone Structure:** | Zone | Area (km2) | Nodes | Description | |------|-----|-----|---|----------| | Zone A (Center) | 2 | 60 | Historic center, marina | | Zone B (West) | 3 | 50 | Industrial, residential | | Zone C (East) | 3 | 50 | Commercial, tourism | | Zone D (South) | 2 | 40 | Port, warehouses | | Zone E (North) | 2 | 40 | Residential, schools | | Zone F (Surrounds) | 3 | 60 | Outskirts, approach roads | | Total | 15 | 300 | Core mesh coverage | ### 1.2 Node Deployment Strategy **Core Archival Nodes (20 units)** - Deployed at strategic elevation points - Connected to fiber backbone - Each serves 4-6 zones - Located: municipal buildings, telecom centers, elevated sites **Edge Archival Nodes (80 units)** - Deployed at neighborhood level - Connected via WiFi mesh to gateways - Each serves ~1 km2 area - Located: community centers, schools, commercial buildings **Gateway Nodes (14 units)** - Internet uplink points - Connected to fiber and cellular backhaul - Strategically distributed across the city - Redundant links (2+ providers per gateway) **Micro Nodes (86 units)** - Specialized by service area - Low-power, edge computing - Deployed at business locations, delivery hubs - Service-specific: health, commerce, logistics nodes --- ## 2. Deployment Procedures ### 2.1 Node Installation Checklist - [ ] Site assessment complete (power, network, elevation) - [ ] Node hardware unboxed and tested - [ ] Node flashed with OS image - [ ] Node powered on and boot confirmed - [ ] Network connectivity established - [ ] Mesh join confirmed (gossip protocol) - [ ] Data storage formatted and RAID status OK - [ ] Solar/UPS power system connected - [ ] Node certificate issued and verified - [ ] Node visible in network dashboard ### 2.2 Mesh Bootstrap Sequence 1. **Gateway nodes** connect to fiber/cellular backhaul 2. **Core nodes** form primary mesh backbone (fiber-connected) 3. **Edge nodes** connect to gateways via WiFi mesh 4. **Micro nodes** join via LoRa or WiFi 5. **Service mesh** establishes connections between layers 6. **Monero wallet** initialization and test transaction 7. **Node registry** populated with all nodes 8. **Monitoring** systems come online ### 2.3 Zone Deployment Priority 1. Zone A (Center) - first 2 weeks 2. Zones B and C - weeks 3-4 3. Zones D and E - weeks 5-6 4. Zone F - weeks 7-8 5. Full mesh connectivity verification - weeks 9-10 --- ## 3. Monitoring and Operations ### 3.1 Monitoring Components - **Node health:** CPU, RAM, disk, power, temperature - **Network health:** link quality, latency, packet loss - **Mesh health:** node count, routing table, gossip status - **Service health:** uptime per service, availability - **XMR network:** wallet balance, tx rate, node fee income ### 3.2 Alert Levels | Level | Condition | Response | |-------|----------|---|-------| | INFO | Normal | Logged | | WARN | Degraded | Monitor, schedule maintenance | | ERROR | Partial | Dispatch, <15 min response | | ALERT | Critical | On-call response, <5 min | | DOWN | Node offline | Auto-failover initiated | ### 3.3 Maintenance Schedule - **Daily:** Automated node health checks - **Weekly:** Mesh route optimization - **Monthly:** Battery/UPS health checks - **Quarterly:** Full node diagnostics - **Annually:** Hardware inspection, firmware updates --- ## 4. Network Configuration ### 4.1 Key Network Parameters | Parameter | Value | Notes | |-----------|------|-----| | Mesh SSID | NodeZero | WiFi mesh | | IPv6 Prefix | fd00:funchal::/48 | | | LoRa Frequency | 868 MHz | EU | | Mesh Port | 9001 | | | Bootstrap Port | 9002 | | | Beacon Interval | 500ms | | | TTL | 64 | | | MTU | 1492 | | | DNS | mesh.local | Internal | | External DNS | 1.1.1.1, 8.8.8.8 | | ### 4.2 Power Management - Solar panels: 200W per node - Battery: 24V 100Ah LiFePO4 - UPS capacity: 8 hours autonomy - Power management: automatic sleep/wake cycles - Low power mode: nodes enter sleep during low activity --- ## 5. Mesh Services Integration ### 5.1 Service Discovery Each node registers available services. Discovery uses mesh gossip: - Service announcement on startup - Periodic heartbeat updates - TTL-based expiration - Cross-service dependency resolution ### 5.2 Message Routing - **Direct routes:** Known nodes, shortest path - **Mesh routes:** Fallback via Gossip - **External routes:** Through gateways - **Routed services:** Rides, Housing, Commerce, etc. ### 5.3 Redundancy Strategy ``` Primary path: Node -> Local Gateway -> Fiber -> Internet Fallback 1: Node -> Local Gateway -> Cell -> Internet Fallback 2: Node -> Neighbor Gateway -> Fiber -> Internet Fallback 3: Node -> Satellite (if equipped) -> Internet ``` - Automatic failover between paths - Link quality monitoring (every 10 seconds) - Bandwidth pooling across available paths --- *Mesh Guide Version 1.0 - June 2026*