Compare commits
No commits in common. "fb00eb335c94c92ff3c19f5d05f25d318d5d8e51" and "d636a105ce2a2db2a044ad7c343779f8a11937c6" have entirely different histories.
fb00eb335c
...
d636a105ce
37
.gitignore
vendored
37
.gitignore
vendored
@ -1,37 +0,0 @@
|
||||
# Dependencies
|
||||
node_modules/
|
||||
*.log
|
||||
*.tmp
|
||||
|
||||
# OS
|
||||
.DS_Store
|
||||
Thumbs.db
|
||||
|
||||
# Build outputs
|
||||
build/
|
||||
dist/
|
||||
*.o
|
||||
*.so
|
||||
*.pyc
|
||||
|
||||
# Config secrets
|
||||
config/*.secret.yml
|
||||
config/*.pem
|
||||
|
||||
# Logs
|
||||
logs/
|
||||
*.log
|
||||
|
||||
# Cache
|
||||
.cache/
|
||||
|
||||
# Generated files
|
||||
*.min.js
|
||||
*.min.css
|
||||
|
||||
# NodeZero local
|
||||
data/
|
||||
*.bak
|
||||
*.swp
|
||||
*.swo
|
||||
*~
|
||||
182
ARCHITECTURE.md
182
ARCHITECTURE.md
@ -1,182 +0,0 @@
|
||||
# Architecture Document
|
||||
# NodeZero - Funchal Archipelago Mesh Network
|
||||
|
||||
---
|
||||
|
||||
## 1. System Overview
|
||||
|
||||
NodeZero is a **multi-layered mesh architecture** deployed across Funchal, Madeira.
|
||||
Each layer operates independently but interlocks with others for resilience
|
||||
and self-healing.
|
||||
|
||||
---
|
||||
|
||||
## 2. Architecture Layers
|
||||
|
||||
### Layer 1: Physical Infrastructure
|
||||
|
||||
```
|
||||
+------ ------------------ ----- +
|
||||
| PHYSICAL LAYER |
|
||||
| [Solar] [UPS] [Fiber] [Cellular Towers] |
|
||||
| [Node1]<->[Node2]<->[FiberHub]<->[CellBackhaul] |
|
||||
| <--- LoRa Mesh (100m-2km range) ---> |
|
||||
+------ ------------------ ----- +
|
||||
```
|
||||
|
||||
**Components:**
|
||||
- **Archival Nodes:** 200 units (20 Core, 80 Edge, 14 Gateway, 86 Micro)
|
||||
- **Mesh Gateways:** WiFi 6/7 access points covering 50m radius each
|
||||
- **LoRa Concentrators:** IoT device connectivity
|
||||
- **Fiber Hubs:** High-bandwidth backbone
|
||||
- **Cellular Backhaul:** MEO, NOS, Vodafone redundancy
|
||||
|
||||
### Layer 2: Network Protocol Stack
|
||||
|
||||
```
|
||||
+------ ------------------ ----- +
|
||||
| APPLICATION PROTOCOLS |
|
||||
| Monero Pay Mesh Auth Service Discovery Routing|
|
||||
+------ ------------------ ----- +
|
||||
| MESH TRANSIT LAYER |
|
||||
+------ ------------------ ----- +
|
||||
| TRANSPORT LAYER |
|
||||
| MQTT CoAP WebSocket gRPC HTTP/3 |
|
||||
+------ ------------------ ----- +
|
||||
| NETWORK LAYER |
|
||||
| IPv6 BGP/MPLS CRDT Sync FEC QoS |
|
||||
+------ ------------------ ----- +
|
||||
| PHYSICAL LAYER |
|
||||
+------ ------------------ ----- +
|
||||
```
|
||||
|
||||
### Layer 3: Service Mesh
|
||||
|
||||
```
|
||||
+----------+ +----------+ +----------+
|
||||
| Rides | | Housing | | Delivery|
|
||||
+----------+ +----------+ +----------+
|
||||
\ | /
|
||||
+----+ v +----+
|
||||
| SERVICE BUS |
|
||||
+--------------------+
|
||||
| |
|
||||
+--+--+ +--+--+
|
||||
| Workforce| |Governance|
|
||||
+----------+ +----------+
|
||||
```
|
||||
|
||||
### Layer 4: Data Layer
|
||||
|
||||
```
|
||||
+-----------+ +---------+ +---------+ +---------+
|
||||
| Core(20) | | Edge(80)| | GW(14) | | Micro(86)|
|
||||
| CRDT DB | | CRDT DB | | CRDT DB | | CRDT DB |
|
||||
| 8-32 TB | | 2-8 TB | | 4-16 TB | | 1-4 TB |
|
||||
+-----------+ +---------+ +---------+ +---------+
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 3. Node Architecture
|
||||
|
||||
### 3.1 Archival Node Spec
|
||||
|
||||
- **CPU:** ARM64 8-core
|
||||
- **RAM:** 32GB DDR4
|
||||
- **Storage:** 8-32 TB RAID1/Btrfs
|
||||
- **Network:** WiFi 6 + LoRa + Cellular + Fiber
|
||||
- **Power:** 24V DC / Solar, UPS 8hr backup
|
||||
- **OS:** Debian Linux with K8s
|
||||
|
||||
### 3.2 Edge Node Spec
|
||||
|
||||
- **CPU:** ARM Cortex-A76
|
||||
- **RAM:** 8GB
|
||||
- **Storage:** 2-8 TB
|
||||
- **Power:** 12V DC
|
||||
- **Form Factor:** 2U
|
||||
|
||||
### 3.3 Gateway Node Spec
|
||||
|
||||
- **CPU:** x86_64 12-core
|
||||
- **RAM:** 16GB
|
||||
- **Storage:** 4-16 TB
|
||||
- **Uplinks:** Fiber, Cell-A, Cell-B, Satellite
|
||||
- **Power:** 48V DC
|
||||
- **Form Factor:** 2U
|
||||
|
||||
### 3.4 Micro Node Spec
|
||||
|
||||
- **CPU:** ARM64 quad-core SoC
|
||||
- **RAM:** 4GB
|
||||
- **Storage:** 1-4 TB
|
||||
- **Power:** 5-12V DC
|
||||
- **Form Factor:** 1U
|
||||
|
||||
---
|
||||
|
||||
## 4. Network Topology
|
||||
|
||||
```
|
||||
+-------+
|
||||
| FIBER |
|
||||
| BACKBONE |
|
||||
+---+---+
|
||||
|
|
||||
+-----------+-----------+
|
||||
| | |
|
||||
+--+--+ +--+--+ +--+--+
|
||||
| GW1 |<-->| GW2 |<-->| GW3 |
|
||||
+--+--+ +--+--+ +--+--+
|
||||
| | |
|
||||
+----+----+ +--+--+ +----+----+
|
||||
| | | | | |
|
||||
+--+--+ +--+--+ +--+--+ +--+--+ +--+--+
|
||||
| N1 |<->| N2 |<->| N3 |<->| N4 |<->| N5 |
|
||||
+--+--+ +--+--+ +--+--+ +--+--+ +--+--+
|
||||
| | |
|
||||
+--+--+ +--+--+ +--+--+
|
||||
| E1 |<-->| E2 |<-->| E3 |
|
||||
+--+--+ +--+--+ +--+--+
|
||||
| | |
|
||||
+--+--+ +--+--+ +--+--+
|
||||
| M1 |<-->| M2 |<-->| M3 |
|
||||
+--+--+ +--+--+ +--+--+
|
||||
|
||||
Key: GW = Gateway N = Core Archival E = Edge M = Micro
|
||||
LoRa Mesh interconnects all nodes
|
||||
|
||||
---
|
||||
|
||||
## 5. Communication Patterns
|
||||
|
||||
1. **Gossip Protocol:** Node discovery and health reporting
|
||||
2. **Event Sourcing:** All state changes as append-only events
|
||||
3. **CQRS:** Command Query Responsibility Separation
|
||||
4. **CRDT Sync:** Offline data sync without conflicts
|
||||
5. **Monero Ledger:** Financial transactions recorded on-chain
|
||||
|
||||
---
|
||||
|
||||
## 6. Security Model
|
||||
|
||||
- **Per-node TLS:** Every node connection encrypted
|
||||
- **Mesh Certificate Authority:** Internal PKI for node identity
|
||||
- **Nostr DIDs:** Decentralized identities bound to Monero addresses
|
||||
- **Key Rotation:** Automatic mesh network key rotation
|
||||
- **Role-based Access:** Service-level permission model
|
||||
|
||||
---
|
||||
|
||||
## 7. Resilience
|
||||
|
||||
- **Redundant Paths:** Each node has >=3 routes to gateway
|
||||
- **Auto-Failover:** Sub-second failover on link/node failure
|
||||
- **Offline Mode:** Mesh continues operating with partial connectivity
|
||||
- **Data Durability:** CRDT guarantees no data loss
|
||||
- **Power Resilience:** Solar + UPS for every node
|
||||
|
||||
---
|
||||
|
||||
*Architecture Version 1.0 - June 2026*
|
||||
184
DEPLOYMENT.md
184
DEPLOYMENT.md
@ -1,184 +0,0 @@
|
||||
# Mesh Network Deployment Guide
|
||||
# NodeZero Funchal
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
This document covers the deployment, configuration, and operations of the NodeZero
|
||||
mesh network across Funchal, Madeira.
|
||||
|
||||
---
|
||||
|
||||
## 1. Network Design
|
||||
|
||||
### 1.1 Coverage Plan
|
||||
|
||||
Funchal 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*
|
||||
116
GOVERNANCE.md
116
GOVERNANCE.md
@ -1,116 +0,0 @@
|
||||
# GOVERNANCE.md
|
||||
# NodeZero Funchal - Governance
|
||||
|
||||
## Overview
|
||||
The governance layer manages the decentralized operations of NodeZero Funchal,
|
||||
combining Monero governance with community-driven mesh services — all identity
|
||||
and attestation handled via Nostr relays.
|
||||
|
||||
## Governance Model
|
||||
### Community Staking
|
||||
- Residents stake tokens (NFTZ) to validate nodes and vote
|
||||
- Voting weight proportional to stake and residency duration
|
||||
- Minimum stake: 100 NFTZ per voting right
|
||||
- Lock-up period: 30 days
|
||||
|
||||
### DAO Council
|
||||
- 13 elected council members
|
||||
- 2-year terms, max 2 consecutive terms
|
||||
- Responsibilities: node deployment, treasury, service fees, disputes
|
||||
|
||||
### Mesh Services Board
|
||||
- 5 technical experts elected for infrastructure governance
|
||||
- Protocol updates, network tuning, hardware standards, security
|
||||
|
||||
## Identity & Relays
|
||||
### Nostr Integration
|
||||
- **DID Resolution:** Decentralized Identifiers via Nostr DIDs (pubkeys)
|
||||
- **Profile Data:** All service profiles stored on Nostr relays
|
||||
- **Attestations:** Peer endorsements and credentials verified through Nostr events
|
||||
- **Relay Redundancy:** Multiple Nostr relins with mesh sync for offline capability
|
||||
|
||||
## Service Layer
|
||||
### Mesh Services
|
||||
| Service | Protocol | Port |
|
||||
|-----|--|
|
||||
| Ride Dispatch | MQTT | 1883 |
|
||||
| Housing Bookings | gRPC | 50051 |
|
||||
| Delivery Routing | gRPC | 50052 |
|
||||
| Commerce Registry | HTTP/3 | 8080 |
|
||||
| Workforce Platform | gRPC | 50053 |
|
||||
| Credential Store | gRPC | 50054 |
|
||||
| Treasury | RPC | 8332 |
|
||||
| Governance | gRPC | 50055 |
|
||||
|
||||
### Service Mesh
|
||||
- Service discovery via mesh gossip
|
||||
- Circuit breakers for fault isolation
|
||||
- Rate limiting per service
|
||||
- Health monitoring with auto-restart
|
||||
- Configuration management
|
||||
|
||||
## Treasury
|
||||
### XMR Treasury
|
||||
- Primary treasury on Monero
|
||||
- CashNet treasury for operations
|
||||
- Stablecoin reserve for volatility hedging
|
||||
- Allocation: Hardware 40%, Operations 25%, Incentives 15%, Expansion 10%, Contingency 10%
|
||||
|
||||
### Treasury Management
|
||||
- Multi-signature wallet for major decisions
|
||||
- Automated monthly distributions
|
||||
- Community proposal system
|
||||
- Nostr-anchored treasury records
|
||||
|
||||
## Voting Mechanisms
|
||||
### On-Ledger Voting
|
||||
- **Method:** Monero via Nostr relay chains
|
||||
- Quorum: 51% of total stake
|
||||
- Pass threshold: >=60% affirmative
|
||||
- Min votes: 1000 participants
|
||||
|
||||
### Off-Chain Voting
|
||||
- Method: Mesh-based poll (for operational decisions)
|
||||
|
||||
### Proposal Types
|
||||
| Type | Scope | Quorum | Vote Time |
|
||||
|------|------|
|
||||
| Standard | Service parameters | 30% | 7 days |
|
||||
| Important | Node deployment, treasury | 51% | 14 days |
|
||||
| Core | Protocol changes, >EUR 100K | 60% | 30 days |
|
||||
|
||||
## Financial Flow
|
||||
### Income
|
||||
1. Node validation fees
|
||||
2. Service mesh usage fees
|
||||
3. Merchant transaction fees (0.1%)
|
||||
4. Tourist mesh passes
|
||||
5. External grants
|
||||
|
||||
### Expenditure
|
||||
1. Hardware procurement (40%)
|
||||
2. Operations & maintenance (25%)
|
||||
3. Community incentives (15%)
|
||||
4. Expansion fund (10%)
|
||||
5. Contingency (10%)
|
||||
|
||||
## Dispute Resolution
|
||||
### Three Levels
|
||||
1. Mediation (Mesh Council) - 7 days, free
|
||||
2. Arbitration (DAO Council) - 14 days, 10 NFTZ fee
|
||||
3. on-ledger Arbitration - 30 days, final binding
|
||||
|
||||
## Evolution Path
|
||||
| Phase | Model | Budget |
|
||||
|-------|--|
|
||||
| Phase 1 | Council-led | EUR 500K |
|
||||
| Phase 2 | DAO transition | EUR 2M |
|
||||
| Phase 3 | Full DAO | Nostr-relay anchored Monero | EUR 10M |
|
||||
| Phase 4 | Autonomous | EUR 25M+ |
|
||||
|
||||
## Key Points
|
||||
- **Identity:** Nostr-registered identities for all residents and services
|
||||
- **Credentials:** Peer-verified, relay-anchored credentials via NIP-xx standards
|
||||
- **Records:** All governance records relayed via Nostr relays on Monero mesh
|
||||
- **Token:** NFTZ token minting and burns on Monero
|
||||
- **Treasury:** Full Monero treasury operational with Nostr event anchoring
|
||||
361
PRD.md
361
PRD.md
@ -1,361 +0,0 @@
|
||||
# Product Requirements Document (PRD)
|
||||
# NodeZero — Funchal Archipelago Mesh Network & Decentralized Economy
|
||||
|
||||
---
|
||||
|
||||
## 1. Purpose & Vision
|
||||
|
||||
NodeZero deploys a complete, decentralized service ecosystem to Funchal, Madeira.
|
||||
The system interlaces mesh networks, archival nodes, and localized services —
|
||||
each powered by Monero (on-ledger + CashNet) — to create a resilient,
|
||||
community-owned micro-economy.
|
||||
|
||||
**Vision:** "A fully decentralized, Monero-integrated town where every service
|
||||
— rides, housing, deliveries, healthcare, education, governance — runs on a
|
||||
self-sovereign mesh network."
|
||||
|
||||
---
|
||||
|
||||
## 2. Scope
|
||||
|
||||
### In Scope (Phase 1 — Funchal Core)
|
||||
|
||||
1. **Mesh Network Infrastructure:** LoRa, WiFi mesh, cellular integration
|
||||
2. **Archival Node Deployment:** 200+ nodes storing local data
|
||||
3. **Internet Access Layer:** Mesh-redundant internet for all services
|
||||
4. **Decentralized Ride-Sharing:** Peer-to-peer transport routing
|
||||
5. **Decentralized House-Sharing:** Distributed booking & ownership ledger
|
||||
6. **Local Delivery Network:** Autonomous + human courier mesh routing
|
||||
7. **Monero-Accepting Businesses:** Point-of-sale + CashNet integration
|
||||
8. **Job Board & Workforce Platform:** Skill verification on-chain
|
||||
9. **Training & Competency Attestation:** Credential system with verifiable tokens
|
||||
10. **Integrated Mesh Services:** Unified service layer across all domains
|
||||
|
||||
### In Scope (Phase 2 — Expansion)
|
||||
|
||||
11. **Madeira Islands Rollout:** Extend to Porto Santo & smaller islands
|
||||
12. **Governance DAO:** Token-based voting & treasury management
|
||||
13. **Healthcare Mesh:** Decentralized health records on mesh
|
||||
14. **Agricultural Services:** Supply chain transparency
|
||||
15. **Tourism Integration:** Visitor services & transient mesh access
|
||||
|
||||
### Future (Phase 3-4)
|
||||
|
||||
16. **Atlantic Archipelago Mesh:** Inter-island connectivity
|
||||
17. **Global Coastal Deployment:** Blueprint exportable to other island towns
|
||||
|
||||
---
|
||||
|
||||
## 3. Detailed Service Requirements
|
||||
|
||||
### 3.1 Mesh Network Infrastructure
|
||||
|
||||
- **LoRaWAN coverage** for IoT devices (sensors, smart meters, deliveries)
|
||||
- **WiFi 6/7 mesh** for high-bandwidth services (video, data transfer)
|
||||
- **Cellular backhaul** (MEO, NOS, Vodafone integration for redundant links)
|
||||
- **Fiber backbone** in Funchal metropolitan center
|
||||
- **Mesh routing protocol** supporting autonomous node discovery & healing
|
||||
- **Edge computing** at each mesh node for local processing
|
||||
- **Service mesh** connecting all applications
|
||||
|
||||
**KPIs:**
|
||||
- Coverage radius: 5km from Funchal center (expandable)
|
||||
- Latency: <20ms mesh internal, <50ms to gateway
|
||||
- Bandwidth: 1Gbps uplink per gateway node
|
||||
- Redundancy: >=3 paths to every node
|
||||
|
||||
### 3.2 Archival Node Deployment
|
||||
|
||||
- **Node type:** ARM64/Intel hybrid, 4U/2U form factors
|
||||
- **Storage:** 8TB-32TB per node (RAID1 for redundancy)
|
||||
- **Uptime:** 99.9% SLA with auto-failover
|
||||
- **Data types:** Mesh logs, service records, job postings, housing contracts,
|
||||
delivery history, merchant transactions, workforce credentials, mesh service logs
|
||||
|
||||
**Node Categories:**
|
||||
| Node Type | Quantity | Role |
|
||||
|-----------|----------|------|
|
||||
| Core Archival | 20 | Primary data storage & routing |
|
||||
| Edge Archival | 80 | Neighborhood data caching |
|
||||
| Gateway | 14 | Internet uplink nodes |
|
||||
| Micro Archival | 86 | Specialized (health, commerce, logistics) |
|
||||
|
||||
### 3.3 Integrated Internet
|
||||
|
||||
- Mesh-local internet: all services reachable even if external internet is down
|
||||
- External connectivity redundancy via >=2 cellular providers + fiber
|
||||
- DNS resolution within mesh
|
||||
- Local CDN for static mesh services
|
||||
|
||||
### 3.4 Decentralized Ride-Sharing
|
||||
|
||||
- **Peer-to-peer:** Residents offer rides to each other
|
||||
- **Mesh-based routing:** Real-time ride data flows through mesh nodes
|
||||
- **Monero/CashNet payments:** Pay-per-ride with instant settlement
|
||||
- **On-chain ride ledger:** Trip history, ratings, disputes
|
||||
- **Supports:** daily commute, tourist transport, elderly mobility
|
||||
- **Features:**
|
||||
- Dynamic pricing (supply/demand algorithm on-chain)
|
||||
- Carpool optimization
|
||||
- Accessible vehicle options
|
||||
- Tourist pass (temporary mesh identity + wallet)
|
||||
|
||||
**KPIs:**
|
||||
- 500+ rides/day by Phase 1 completion
|
||||
- Average dispatch time <3 minutes
|
||||
- 95% on-time rate
|
||||
|
||||
### 3.5 Decentralized House-Sharing
|
||||
|
||||
- **Smart contract leases** for long-term and short-term housing
|
||||
- **Ownership registry** on Monero (via Nostr relays)
|
||||
- **Mesh-based availability:** Real-time room/house availability feed
|
||||
- **Tokenized equity:** Fractional ownership of properties via tokens
|
||||
- **Tenant verification:** On-chain identity + credit scoring
|
||||
|
||||
**Features:**
|
||||
- Host dashboard (local mesh + mobile access)
|
||||
- Auto-scheduling via mesh consensus
|
||||
- Utility billing via CashNet microtransactions
|
||||
- Dispute resolution through decentralized arbitration
|
||||
|
||||
**KPIs:**
|
||||
- 2,000 housing units registered by Phase 1
|
||||
- 30% short-term rental capacity
|
||||
- <5% vacancy rate utilization
|
||||
|
||||
### 3.6 Local Delivery Network
|
||||
|
||||
- **Multi-modal:** Pedestrian, bicycle, drone, vehicular
|
||||
- **Mesh-orchestrated:** Delivery routing computed by mesh nodes
|
||||
- **Monero/CashNet payments:** Per-delivery microtransactions
|
||||
- **Delivery types:**
|
||||
- Food & grocery
|
||||
- Medical supplies
|
||||
- Mail & packages
|
||||
- E-commerce last mile
|
||||
- Emergency deliveries
|
||||
|
||||
**Features:**
|
||||
- Real-time delivery tracking on mesh
|
||||
- Autonomous drone corridors (high-priority)
|
||||
- Consolidated neighborhood delivery hubs
|
||||
- Carbon-negative delivery priority
|
||||
|
||||
**KPIs:**
|
||||
- 1,000+ deliveries/day
|
||||
- Average delivery time <45 min urban
|
||||
- 80% cost savings vs traditional courier
|
||||
|
||||
### 3.7 Monero-Accepting Businesses
|
||||
|
||||
- **Merchant POS on CashNet:** QR code payments, no banking intermediaries
|
||||
- **On-chain receipts** for businesses and customers
|
||||
- **Mesh-verified merchants** (identity, ratings, compliance)
|
||||
- **Automatic settlement** to merchant wallet
|
||||
- **Multi-currency support:** XMR + stablecoin + fiat conversion
|
||||
|
||||
**Business Categories:**
|
||||
- Restaurants & cafes
|
||||
- Retail shops
|
||||
- Hotels & guesthouses
|
||||
- Healthcare providers
|
||||
- Education services
|
||||
- Tourism operators
|
||||
- Transportation
|
||||
|
||||
**KPIs:**
|
||||
- 500+ businesses onboarded (Phase 1)
|
||||
- 80% of businesses accepting CashNet
|
||||
- Daily transaction volume: EUR 50K+
|
||||
|
||||
### 3.8 Job Board & Workforce Platform
|
||||
|
||||
- **Decentralized job board:** On-chain job postings & applications
|
||||
- **Skill registry:** Workers attested on mesh
|
||||
- **Smart contracts for employment:** Freelance, contract, full-time
|
||||
- **Wage payments via CashNet**
|
||||
|
||||
**Features:**
|
||||
- Employer dashboard (mesh-accessible)
|
||||
- Job matching algorithm (mesh-orchestrated)
|
||||
- Freelance gig economy section
|
||||
- Real-time skill & availability updates
|
||||
- International worker support (visa, credential recognition)
|
||||
|
||||
**KPIs:**
|
||||
- 5,000+ workers registered
|
||||
- 1,000+ active job postings
|
||||
- 50+ job matches/day
|
||||
|
||||
### 3.9 Training & Competency Attestation
|
||||
|
||||
- **On-chain credentialing:** Skills, certifications, licenses verifiable on Monero
|
||||
- **Mesh-based learning platform:** Courses available offline (mesh-synced)
|
||||
- **Digital badges:** competency badges (stackable, verifiable)
|
||||
- **Employer trust layer:** Employers can verify worker credentials instantly
|
||||
|
||||
**Training Areas:**
|
||||
- Healthcare (nursing, elderly care, medical technician)
|
||||
- Hospitality (tourism, cooking, diving/surf instructor)
|
||||
- Technology (network admin, IT support, software dev)
|
||||
- Trades (electrical, plumbing, construction)
|
||||
- Logistics (drone pilot, delivery routing, warehouse)
|
||||
|
||||
**Features:**
|
||||
- Self-service credential upload (mesh-gate supported)
|
||||
- Community attestation (peer-verified skills)
|
||||
- Institution partnership (local schools, universities accept mesh credentials)
|
||||
- Training history on-chain
|
||||
|
||||
**KPIs:**
|
||||
- 10,000+ attestations issued (Phase 1)
|
||||
- 95% credential verification rate
|
||||
- 40% workforce with at least 1 mesh credential
|
||||
|
||||
---
|
||||
|
||||
## 4. Technical Requirements
|
||||
|
||||
### 4.1 Architecture
|
||||
|
||||
```
|
||||
+--------------------------------------------------------------+
|
||||
| Application Layer |
|
||||
+--+---+---+---+---+--+-------+---+------+------+-+ |
|
||||
| Rides |Houses|Jobs |Bills |Health| ... |
|
||||
+--+---+---+---+---+--+-------+---+------+------+-+ |
|
||||
+------+-------+-------+-------+ |
|
||||
Service Mesh |
|
||||
+--------------------------------------------------------------+
|
||||
| | |
|
||||
| +-----------+ +-----------+ +-----------+ | |
|
||||
| | Core | | Edge | | Gateway | | |
|
||||
| | Archival | | Archival | | Archival | | |
|
||||
| +-----------+ +-----------+ +-----------+ | |
|
||||
| | |
|
||||
| +--------+ +--------+ +-+ +-+ | |
|
||||
| |XMR+LNV | |External| |F| |C| | |
|
||||
| |TXs, IDs,| |Internet| |i| |e| | |
|
||||
| |Treasury | +--------+ |b| |l| | |
|
||||
| +--------+ +-+-+-+-+-+-+ |a| |l| | |
|
||||
+--|----------|--+-+-+-+-+-+-+-|b| |r|-------------+
|
||||
| Wi-Fi | LoRa | Cellular | Fiber |
|
||||
+----------+----------+------------+-----------+
|
||||
FUNCHAL MESH NETWORK
|
||||
```
|
||||
|
||||
### 4.2 Protocols & Standards
|
||||
|
||||
- **Network:** IPv6 over WiFi/LoRa/Cellular/fiber
|
||||
- **Mesh Protocol:** Custom overlay + BGP/MPLS hybrid
|
||||
- **Consensus:** CashNet/XMR hybrid for financial; Raft for service config
|
||||
- **Data:** Event-sourced, append-only logs (CQRS pattern)
|
||||
- **Identity:** Monero-based DIDs (Decentralized Identifiers)
|
||||
- **Authentication:** Mesh tokens + passkeys
|
||||
- **Encryption:** End-to-end TLS + mesh network key rotation
|
||||
|
||||
### 4.3 Hardware
|
||||
|
||||
- **Archival Nodes:** Industrial-grade ARM64 servers
|
||||
- **Mesh Gateways:** High-power WiFi 6 APs + LoRa concentrators
|
||||
- **Edge Devices:** Smart meters, POS terminals, delivery trackers
|
||||
- **Power:** Solar-optimized with UPS backup
|
||||
|
||||
### 4.4 Software
|
||||
|
||||
- **OS:** Linux (Debian-based, custom kernel for IoT)
|
||||
- **Container:** Docker on all nodes
|
||||
- **Orchestration:** Mesh-aware K8s (micro-K8s per neighborhood)
|
||||
- **Language:** Rust (performance-critical), JavaScript/TypeScript (services), Go (mesh routing)
|
||||
- **Database:** CRDT-based distributed (for offline capability), SQLite for edge
|
||||
|
||||
---
|
||||
|
||||
## 5. Phased Implementation
|
||||
|
||||
### Phase 1 (Months 1-6) — Funchal Core Pilot
|
||||
|
||||
- Deploy 50 archival nodes (pilot zone in city center + marina district)
|
||||
- Establish mesh network in Funchal center
|
||||
- Launch ride-sharing pilot (100 vehicles)
|
||||
- Onboard 100 houses to mesh sharing platform
|
||||
- Launch job board (beta)
|
||||
- Onboard 100 businesses to Monero/CashNet
|
||||
- Deploy 10 delivery hubs
|
||||
- Launch competency attestation system (initial 2,000 credentials)
|
||||
|
||||
### Phase 2 (Months 7-12) — Full Rollout
|
||||
|
||||
- Expand to 200 archival nodes
|
||||
- Full mesh coverage of Funchal
|
||||
- Scale to 500 rides/day, 2,000 housing units
|
||||
- Full business onboarding (500+)
|
||||
- Delivery network operational (1,000+/day)
|
||||
- 5,000 workers, 10,000 attestations
|
||||
- Launch DAO governance
|
||||
- Healthcare mesh integration
|
||||
|
||||
### Phase 3 (Months 13-18) — Madeira Islands Expansion
|
||||
|
||||
- Extend mesh to Porto Santo and smaller surrounding islands
|
||||
- Deploy inter-island gateway nodes
|
||||
- Launch tourist mesh passes
|
||||
- Agricultural supply chain integration
|
||||
- Tourism integration (hotel, dive center, excursion bookings)
|
||||
|
||||
### Phase 4 (Months 19-24) — Atlantic Archipelago Blueprint
|
||||
|
||||
- Standardize deployment package
|
||||
- Deploy 2-3 additional Atlantic/coastal towns
|
||||
- Export Funchal model as template
|
||||
- Full Monero treasury operational
|
||||
- Autonomous mesh operations (minimal human intervention)
|
||||
|
||||
---
|
||||
|
||||
## 6. Budget & Resources (High-Level)
|
||||
|
||||
| Category | Phase 1 | Phase 2 | Phase 3-4 | Total |
|
||||
|----------|---------|---------|-----------|-------|
|
||||
| Hardware (nodes, APs, gateways) | EUR 1.2M | EUR 0.8M | EUR 1.5M | EUR 3.5M |
|
||||
| Software development | EUR 0.6M | EUR 0.5M | EUR 0.4M | EUR 1.5M |
|
||||
| Deployment & installation | EUR 0.4M | EUR 0.3M | EUR 0.5M | EUR 1.2M |
|
||||
| Operations & maintenance | EUR 0.3M/yr | EUR 0.4M/yr | EUR 0.6M/yr | EUR 6.3M (3yr) |
|
||||
| Marketing & onboarding | EUR 0.2M | EUR 0.3M | EUR 0.4M | EUR 0.9M |
|
||||
| Contingency | EUR 0.3M | EUR 0.3M | EUR 0.4M | EUR 1.0M |
|
||||
| **Subtotal** | **EUR 3.0M** | **EUR 2.4M** | **EUR 3.8M** | **EUR 16.4M** |
|
||||
|
||||
---
|
||||
|
||||
## 7. Success Criteria
|
||||
|
||||
| Metric | Phase 1 Target | Phase 2 Target | Phase 3-4 Target |
|
||||
|--------|---------------|---------------|-----------------|
|
||||
| Mesh coverage | 4 km2 | 25 km2 | Full Madeira |
|
||||
| Active users | 5,000 | 20,000 | 100,000+ |
|
||||
| Nodes online | 50 | 200 | 500+ |
|
||||
| XMR tx volume/day | EUR 10K | EUR 50K | EUR 200K+ |
|
||||
| Households online | 500 | 5,000 | 20,000+ |
|
||||
| Workers employed via mesh | 500 | 3,000 | 10,000+ |
|
||||
| System uptime | 99% | 99.5% | 99.9% |
|
||||
| Resident satisfaction | 70% | 80% | 90%+ |
|
||||
|
||||
---
|
||||
|
||||
## 8. Risks & Mitigations
|
||||
|
||||
| Risk | Impact | Mitigation |
|
||||
|------|--------|-----------|
|
||||
| Internet dependency for external services | High | Full mesh-local operations; offline fallback |
|
||||
| Monero price volatility | Medium | Stablecoin support; automated hedging |
|
||||
| Resident adoption | Medium | Community onboarding program; incentives |
|
||||
| Hardware failures | Medium | Redundant mesh paths; auto-failover |
|
||||
| Regulatory changes | Low | Flexible architecture; legal advisory board |
|
||||
| Climate events (storms) | High | Ruggedized hardware; elevated node placement |
|
||||
|
||||
---
|
||||
|
||||
*PRD Version 1.0 — June 2026*
|
||||
*Author: NodeZero Product Team*
|
||||
*Approved: Pending Community Vote*
|
||||
126
README.md
126
README.md
@ -1,125 +1,3 @@
|
||||
# NodeZero — Funchal Archipelago Mesh Network & Decentralized Economy
|
||||
# DarkNode
|
||||
|
||||
## Mission
|
||||
|
||||
Deploy a full stack of **archival nodes**, a **mesh network**, and **decentralized services** to the town of Funchal, Madeira — creating a resilient, self-sovereign micro-economy that serves as a blueprint for other islands and coastal towns.
|
||||
|
||||
## The Archipelago of Services
|
||||
|
||||
```
|
||||
┌──────────────────────────────────┐
|
||||
│ FUNCHAL, MADEIRA │
|
||||
│ │
|
||||
┌───────────────┼─────────────────────────────────┼────────────────┐
|
||||
│ │ ARCHIPELAGO LAYER │ │
|
||||
│ ┌──────────┐ │ ┌──────────┐ ┌──────────┐ │ ┌────────┐ │
|
||||
│ │ Mesh │ │ │ Archival │ │ Gateway │◄──┼───►│ Cloud │ │
|
||||
│ │ Nodes │ │ │ Nodes │ │ Nodes │ │ │ Fail │ │
|
||||
│ └────┬─────┘ │ └──────────┘ └──────────┘ │ │ over │ │
|
||||
│ │ │ ▲ ▲ │ │ Lay │ │
|
||||
│ ┌────▼────────────────────────────▼────────┐ │ └────────┘ │
|
||||
│ │ MESH INTERNET LAYER │◄──┼────────────────┘
|
||||
│ │ LoRa │ WiFi Mesh | Cellular | Fiber │
|
||||
└──┼──────────────────│─────────────│─────│──┼────┘
|
||||
│ ┌────────┐ ┌──────────┐ ┌────────┐ │
|
||||
└─►│Mobility│ │ Housing │ │Commerce│ │
|
||||
│ │ │ │ │ │ │
|
||||
└────────┘ └──────────┘ └────────┘ │
|
||||
▲ ▲ ▲ │
|
||||
└───────────┼──────────┘ │
|
||||
┌───────┴────────┐ │
|
||||
│ Workforce & │ │
|
||||
│ Governance │ │
|
||||
└────────────────┘ │
|
||||
│ ┌─────────▼────────┐
|
||||
└────────────►│ Logistics & │
|
||||
│ Deliveries │
|
||||
└──────────────────┘
|
||||
```
|
||||
|
||||
## Core Services
|
||||
|
||||
| Service | Status | Priority |
|
||||
|---------|--------|----------|
|
||||
| Mesh Network Infrastructure | Planned | P0 |
|
||||
| Archival Node Deployment | Planned | P0 |
|
||||
| Decentralized Ride-Sharing | Planned | P1 |
|
||||
| Decentralized House-Sharing | Planned | P1 |
|
||||
| Local Delivery Network | Planned | P1 |
|
||||
| Monero-Accepting Merchants | Planned | P1 |
|
||||
| Job Board & Workforce | Planned | P2 |
|
||||
| Training & Competency Attestation | Planned | P2 |
|
||||
| Integrated Mesh Services | Planned | P1 |
|
||||
| Local Internet Access | Planned | P0 |
|
||||
| Future Expansion Nodes | Planned | P2 |
|
||||
| Governance DAO Layer | Planned | P2 |
|
||||
|
||||
## Directory Structure
|
||||
|
||||
```
|
||||
NodeZero/
|
||||
├── README.md # This overview
|
||||
├── PRD.md # Product Requirements Document
|
||||
├── ARCHITECTURE.md # Technical architecture
|
||||
├── GOVERNANCE.md # Governance model
|
||||
├── ROADMAP.md # Implementation phases
|
||||
├── config/ # Configuration files
|
||||
│ ├── node.yml # Archival node configs
|
||||
│ ├── mesh.yml # Mesh networking parameters
|
||||
│ └── monero.yml # Monero integration config
|
||||
├── docs/ # Expanded documentation
|
||||
├── scripts/ # Deployment & ops scripts
|
||||
├── infrastructure/ # Mesh network & node infrastructure
|
||||
│ ├── mesh/ # Mesh topology, routing, protocols
|
||||
│ ├── nodes/ # Archival node specs & deployment
|
||||
│ └── internet/ # Internet connectivity layers
|
||||
├── mobility/ # Decentralized ride-sharing
|
||||
├── housing/ # Decentralized house-sharing
|
||||
├── logistics/ # Local delivery network
|
||||
├── commerce/ # Monero-accepting businesses
|
||||
├── workforce/ # Job board, training, attestation
|
||||
├── governance/ # Mesh services & decentralized governance
|
||||
└── expansion/ # Future service areas
|
||||
```
|
||||
|
||||
## Key Metrics
|
||||
|
||||
- **Target Coverage:** Funchal municipality (~75 km2)
|
||||
- **Node Capacity:** 200+ interconnected archival nodes
|
||||
- **Mesh Nodes:** 500+ edge nodes across the urban core
|
||||
- **Population Served:** ~110,000 residents
|
||||
- **Monero Throughput:** CashNet Network enabled
|
||||
- **Internet Uptime:** 99.9% via mesh redundancy
|
||||
|
||||
## Getting Started
|
||||
|
||||
```bash
|
||||
# Explore the architecture
|
||||
cat ARCHITECTURE.md
|
||||
|
||||
# View product requirements
|
||||
cat PRD.md
|
||||
|
||||
# Check deployment configs
|
||||
cat config/node.yml
|
||||
cat config/mesh.yml
|
||||
|
||||
# Deploy the pilot mesh network
|
||||
./scripts/deploy_mesh.sh
|
||||
```
|
||||
|
||||
## Governance
|
||||
|
||||
Funchal's NodeZero operates under a hybrid governance model:
|
||||
- **Community Staking:** Residents stake tokens to validate nodes
|
||||
- **DAO Council:** Elected representatives manage mesh services
|
||||
- **Monero Treasury:** Decentralized treasury for service funding
|
||||
- **Transparent Ledger:** All governance decisions recorded on-ledger
|
||||
|
||||
## Expansion Path
|
||||
|
||||
Phase 1 (Funchal core) -> Phase 2 (Madeira islands) -> Phase 3 (Atlantic archipelago) -> Phase 4 (Global coastal deployment)
|
||||
|
||||
---
|
||||
|
||||
*NodeZero: Building the decentralized town, one mesh node at a time.*
|
||||
Monero/Cash Based Circular Economy
|
||||
183
ROADMAP.md
183
ROADMAP.md
@ -1,183 +0,0 @@
|
||||
# Roadmap
|
||||
# NodeZero Funchal Implementation Roadmap
|
||||
|
||||
---
|
||||
|
||||
## Timeline Overview
|
||||
|
||||
```
|
||||
Month: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
|
||||
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|
||||
P1: |Pilot| | | | | | | | | | | | | | | |
|
||||
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|
||||
P2: | | | | | | | | | | | | | | | | | |
|
||||
|Deploy| |Mesh| |Scale| |Full| |DAO | |Health| | | |
|
||||
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|
||||
P3: | | | | | | | | | | | | | | | | | |
|
||||
| | | | | | | | | | | | | |
|
||||
| Porto| | Tour| | Agri| | | | | | | | | | | |
|
||||
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|
||||
P4: | | | | | | | | | | | | | | | | | |
|
||||
| | | | | | | | | | | | | | | | | |
|
||||
| Finalize| | | | | | | | | | | | | | |
|
||||
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Phase 1: Funchal Core Pilot (Months 1-6)
|
||||
|
||||
### Month 1: Foundation
|
||||
- [ ] Community formation and initial token minting
|
||||
- [ ] Site surveys (network coverage, power, fiber access)
|
||||
- [ ] Hardware procurement (initial 50 nodes)
|
||||
- [ ] Mesh software development (core v1.0)
|
||||
- [ ] Community education campaign
|
||||
|
||||
### Month 2: Infrastructure Build
|
||||
- [ ] Node fabrication and testing
|
||||
- [ ] Gateway installation (14 gateways)
|
||||
- [ ] WiFi mesh AP deployment (100 points)
|
||||
- [ ] LoRa concentrator setup
|
||||
- [ ] Fiber backbone connections
|
||||
- [ ] Solar power installation on pilot nodes
|
||||
|
||||
### Month 3: Network Go-Live
|
||||
- [ ] Mesh network online (pilot zone: 4 km2)
|
||||
- [ ] Internet connectivity established
|
||||
- [ ] Node software deployed and monitoring active
|
||||
- [ ] Monero testnet integration
|
||||
- [ ] First community node validation
|
||||
|
||||
### Month 4: Services Rollout
|
||||
- [ ] Ride-sharing pilot (50 vehicles)
|
||||
- [ ] Housing sharing platform (50 units)
|
||||
- [ ] Job board launch (beta)
|
||||
- [ ] 50 businesses onboarded to CashNet
|
||||
- [ ] 5 delivery hubs operational
|
||||
- [ ] Competency attestation system live (500 credentials)
|
||||
|
||||
### Month 5: Scale Pilot
|
||||
- [ ] Expand to 500 rides/day (pilot target: 200)
|
||||
- [ ] Housing units to 100
|
||||
- [ ] Job board: 500 workers, 500 postings
|
||||
- [ ] Businesses: 100 accepting CashNet
|
||||
- [ ] Deliveries: 200/day
|
||||
- [ ] Attestations: 2,000 issued
|
||||
|
||||
### Month 6: Pilot Assessment
|
||||
- [ ] Performance review (all KPIs)
|
||||
- [ ] Community feedback analysis
|
||||
- [ ] Bug fixes and optimizations
|
||||
- [ ] Phase 2 planning and budget approval
|
||||
- [ ] Community vote on Phase 2
|
||||
|
||||
---
|
||||
|
||||
## Phase 2: Full Rollout (Months 7-12)
|
||||
|
||||
### Months 7-8: Expansion
|
||||
- [ ] Deploy 150 more archival nodes (total 200)
|
||||
- [ ] Mesh coverage expansion (25 km2)
|
||||
- [ ] Additional gateways (30 more)
|
||||
- [ ] Cellular backhaul optimization
|
||||
- [ ] Tourism integration for mesh
|
||||
|
||||
### Months 9-10: Service Growth
|
||||
- [ ] Ride-sharing: 500 rides/day
|
||||
- [ ] Housing: 2,000 units registered
|
||||
- [ ] Deliveries: 1,000/day
|
||||
- [ ] Businesses: 500+ active
|
||||
- [ ] Workers: 5,000 registered
|
||||
- [ ] Attestations: 10,000 issued
|
||||
- [ ] Healthcare mesh integration (pilot)
|
||||
|
||||
### Months 11-12: DAO and Governance
|
||||
- [ ] DAO launch and council election
|
||||
- [ ] Treasury operations established
|
||||
- [ ] First community votes
|
||||
- [ ] Service fee model settled
|
||||
- [ ] Dispute resolution operational
|
||||
- [ ] Phase 2 performance review
|
||||
- [ ] Phase 3 deployment planning
|
||||
|
||||
---
|
||||
|
||||
## Phase 3: Madeira Islands Expansion (Months 13-18)
|
||||
|
||||
### Months 13-14: Inter-Island
|
||||
- [ ] Porto Santo mesh extension
|
||||
- [ ] Inter-island gateway deployment
|
||||
- [ ] Satellite connectivity for remote areas
|
||||
- [ ] Tourist mesh passes available
|
||||
- [ ] Agricultural supply chain integration
|
||||
|
||||
### Months 15-16: Service Expansion
|
||||
- [ ] Tourism services fully integrated
|
||||
- [ ] Healthcare mesh expanded
|
||||
- [ ] Agricultural services operational
|
||||
- [ ] Cross-island delivery network
|
||||
- [ ] Visitor accommodation network
|
||||
|
||||
### Months 17-18: Standardization
|
||||
- [ ] Standardize deployment package
|
||||
- [ ] Document Funchal model
|
||||
- [ ] Operational efficiency optimization
|
||||
- [ ] Automated mesh operations (minimal staff)
|
||||
- [ ] Phase 3 review
|
||||
- [ ] Phase 4 planning
|
||||
|
||||
---
|
||||
|
||||
## Phase 4: Atlantic Archipelago Blueprint (Months 19-24)
|
||||
|
||||
### Months 19-20: Blueprint Export
|
||||
- [ ] Select 2-3 additional towns
|
||||
- [ ] Export Funchal deployment package
|
||||
- [ ] Train local operators (knowledge transfer)
|
||||
- [ ] Deploy additional archipelago nodes
|
||||
- [ ] International merchant network expansion
|
||||
|
||||
### Months 21-22: Autonomous Operations
|
||||
- [ ] Full Monero treasury operational
|
||||
- [ ] On-chain governance fully active
|
||||
- [ ] Autonomous mesh management
|
||||
- [ ] Self-healing, self-optimizing infrastructure
|
||||
- [ ] Tourism fully integrated with mesh
|
||||
|
||||
### Months 23-24: Consolidation
|
||||
- [ ] All KPIs met or exceeded
|
||||
- [ ] Resident satisfaction >90%
|
||||
- [ ] Community ownership threshold reached
|
||||
- [ ] Deployment package v1.0 released
|
||||
- [ ] Global coastal town network established
|
||||
- [ ] NodeZero model presented internationally
|
||||
|
||||
---
|
||||
|
||||
## Milestones Summary
|
||||
|
||||
| Month | Milestone | KPI Reached |
|
||||
|-------|-----------|------|------|------|
|
||||
| 3 | First mesh online | 50 nodes, 4 km2 coverage |
|
||||
| 6 | Phase 1 complete | 100 rides/day, 100 units, 50 businesses |
|
||||
| 12 | Phase 2 complete | 500 rides/day, 2K housing, 500 businesses, DAO live |
|
||||
| 18 | Phase 3 complete | Full Madeira coverage, tourist integration |
|
||||
| 24 | Phase 4 complete | 3 towns deployed, autonomous operations |
|
||||
|
||||
---
|
||||
|
||||
## Risk Management Timeline
|
||||
|
||||
| Phase | Key Risk | Mitigation |
|
||||
|-------|----------|------|---|------|
|
||||
| 1 | Delays in hardware deployment | Parallel procurement; buffer inventory |
|
||||
| 1 | Low community adoption | Incentive programs; pilot programs |
|
||||
| 2 | Monero price volatility | Stablecoin reserve; automated hedging |
|
||||
| 3 | Inter-island connectivity | Multi-mode gateways; satellite backup |
|
||||
| 4 | Export complexity | Standardized packaging; documentation |
|
||||
|
||||
---
|
||||
|
||||
*Roadmap Version 1.0 - June 2026*
|
||||
*Approved by: Pending Community Vote*
|
||||
@ -1,73 +0,0 @@
|
||||
# Commerce - Monero-accepting Businesses
|
||||
# NodeZero Funchal
|
||||
|
||||
## Architecture
|
||||
CashNet-powered merchant ecosystem where businesses accept Monero with
|
||||
cash receipts and mesh-verified identity.
|
||||
|
||||
## Merchant Categories
|
||||
- Restaurants & caf6s
|
||||
- Retail shops
|
||||
- Hotels & guesthouses
|
||||
- Healthcare providers
|
||||
- Education services
|
||||
- Tourism operators
|
||||
- Transportation services
|
||||
|
||||
## Key Components
|
||||
- **POS System:** QR code CashNet payments, no banking intermediaries
|
||||
- **Merchant Registry:** WoT verified businesses with nostr identity
|
||||
- **Payment Gateway:** CashNet network settlement
|
||||
- **Treasury Integration:** Monero treasury connection
|
||||
- **Receipt Ledger:** Cash transaction records
|
||||
- **Discovery Service:** Mesh-based merchant discovery
|
||||
|
||||
## Payment Flow
|
||||
1. Customer scans merchant QR code
|
||||
2. CashNet payment routed via mesh
|
||||
3. Instant settlement to merchant wallet
|
||||
4. Cash receipt generated
|
||||
5. Transaction recorded on mesh ledger
|
||||
6. Merchant rating updated
|
||||
|
||||
## Integration Points
|
||||
- Mesh network (payment routing, identity)
|
||||
- Monero Ledger (settlement, receipts)
|
||||
- Workforce (worker payments)
|
||||
- Governance (treasury management)
|
||||
- Mobility (driver payments)
|
||||
- Delivery (delivery payments)
|
||||
|
||||
## Features
|
||||
- Low transaction fees (0.1%)
|
||||
- Instant settlement (no waiting periods)
|
||||
- Multi-currency support (XMR, USDC, EUR)
|
||||
- Cash receipts for accounting
|
||||
- Mesh verification badge
|
||||
- Dynamic merchant categories
|
||||
- Business wallet management
|
||||
- Automated treasury contributions
|
||||
- Stablecoin conversion option
|
||||
|
||||
## Metrics
|
||||
| Metric | Target |
|
||||
|----------|-----|
|
||||
| Businesses onboarded | 500+ |
|
||||
| CashNet acceptance rate | 80% of businesses |
|
||||
| Daily transaction volume | EUR 50K+ |
|
||||
| Average transaction | EUR 25 |
|
||||
| Transaction fees per biz | EUR 0.05-0.50/day |
|
||||
|
||||
## Implementation
|
||||
- Phase 1: 100 businesses (core zones A, B, C)
|
||||
- Phase 2: Full onboarding (all zones, 500+)
|
||||
- Business wallets on mesh
|
||||
- POS terminals installed and verified
|
||||
- Merchant discovery via mesh app
|
||||
|
||||
## Future
|
||||
- Cross-border merchant network
|
||||
- Smart contract subscriptions
|
||||
- Merchant loyalty tokens
|
||||
- B2B mesh payments
|
||||
- DeFi integration for merchant treasury
|
||||
@ -1,105 +0,0 @@
|
||||
# NodeZero - Monero Integration Configuration
|
||||
# Funchal, Madeira
|
||||
|
||||
monero:
|
||||
# Network
|
||||
network: "mainnet" # or "testnet"
|
||||
protocol: "Monero"
|
||||
lightning: true
|
||||
|
||||
# Node settings
|
||||
node:
|
||||
binary: "bitcoin"
|
||||
version: "26.0"
|
||||
data_dir: "/data/bitcoin"
|
||||
wallet_path: "/data/bitcoin/wallet.dat"
|
||||
|
||||
# Core functionality
|
||||
core:
|
||||
transaction_type: "on-chain"
|
||||
confirmation_blocks: 6
|
||||
dust_threshold_sat: 546
|
||||
fee_rate_sat_per_byte: 10
|
||||
max_fee_rate_sat_per_byte: 100
|
||||
|
||||
# CashNet Network
|
||||
lightning:
|
||||
enabled: true
|
||||
implementation: "LND"
|
||||
grpc_port: 10009
|
||||
rest_port: 8080
|
||||
ws_port: 9735
|
||||
alias: "NodeZeroFunchal"
|
||||
color: "00FF00"
|
||||
|
||||
# CashNet channels
|
||||
channels:
|
||||
min_depth: 1
|
||||
default_expiry: 144
|
||||
reserve_sat: 10000
|
||||
min_htlc_msat: 1
|
||||
|
||||
# Merchant capabilities
|
||||
merchant:
|
||||
pos_type: "qr-code"
|
||||
supported_currencies: ["XMR", "USD", "EUR"]
|
||||
auto_convert: true
|
||||
settlement_currency: "EUR"
|
||||
conversion_threshold_eur: 100
|
||||
invoice_expiry_minutes: 60
|
||||
min_payment_sat: 1
|
||||
max_payment_sat: 10000
|
||||
|
||||
# Treasury
|
||||
treasury:
|
||||
type: "multi-sig"
|
||||
min_balance_btc: 5.0
|
||||
treasury_address: "bc1q..."
|
||||
|
||||
# Allocation percentages
|
||||
allocation:
|
||||
hardware: 40
|
||||
operations: 25
|
||||
incentives: 15
|
||||
expansion: 10
|
||||
contingency: 10
|
||||
|
||||
# Hedging
|
||||
hedging:
|
||||
enabled: true
|
||||
stablecoin_ratio: 0.3
|
||||
stablecoin_type: "USDC"
|
||||
rebalance_threshold: 0.05
|
||||
|
||||
# Identity
|
||||
identity:
|
||||
type: "BIP-322"
|
||||
did_prefix: "did:nodezero:funchal:"
|
||||
resolver: "mesh.local/bitcoin"
|
||||
|
||||
# Fee structure
|
||||
fees:
|
||||
mesh_validation: 5
|
||||
service_discovery: 1
|
||||
credential_attestation: 2
|
||||
job_posting: 3
|
||||
vehicle_listing: 4
|
||||
housing_listing: 3
|
||||
merchant_txn_pct: 0.1
|
||||
|
||||
# Events
|
||||
events:
|
||||
subscription_topics:
|
||||
- "transactions"
|
||||
- "invoices"
|
||||
- "treasury_updates"
|
||||
- "fee_changes"
|
||||
- "node_status"
|
||||
webhook_url: "http://mesh.local:8080/bitcoin/webhook"
|
||||
|
||||
# Backup
|
||||
backup:
|
||||
frequency: "daily"
|
||||
retention_days: 30
|
||||
storage_location: "/data/bitcoin/backup"
|
||||
sync_to_mesh: true
|
||||
128
config/mesh.yml
128
config/mesh.yml
@ -1,128 +0,0 @@
|
||||
# NodeZero - Mesh Network Configuration
|
||||
# Funchal, Madeira
|
||||
|
||||
mesh:
|
||||
# Network-wide settings
|
||||
name: "funchal-mesh"
|
||||
version: "1.0.0"
|
||||
network_id: "mesh.funchal.madeira"
|
||||
|
||||
# Geographic parameters
|
||||
geography:
|
||||
primary_coverage_km2: 15
|
||||
target_coverage_km2: 75
|
||||
urban_center_km2: 12
|
||||
elevation_min_m: 0
|
||||
elevation_max_m: 400
|
||||
max_node_spacing_m: 50
|
||||
|
||||
# Coverage zones
|
||||
zones:
|
||||
A:
|
||||
name: "Centro/Funchal"
|
||||
area_km2: 2
|
||||
node_count: 60
|
||||
elevation_m: 50
|
||||
fiber_connected: true
|
||||
B:
|
||||
name: "Zona Industrial"
|
||||
area_km2: 3
|
||||
node_count: 50
|
||||
elevation_m: 100
|
||||
fiber_connected: true
|
||||
C:
|
||||
name: "Zona Comercial"
|
||||
area_km2: 3
|
||||
node_count: 50
|
||||
elevation_m: 75
|
||||
fiber_connected: true
|
||||
D:
|
||||
name: "Porto"
|
||||
area_km2: 2
|
||||
node_count: 40
|
||||
elevation_m: 10
|
||||
fiber_connected: true
|
||||
E:
|
||||
name: "Zona Residencial Norte"
|
||||
area_km2: 2
|
||||
node_count: 40
|
||||
elevation_m: 150
|
||||
fiber_connected: false
|
||||
F:
|
||||
name: "Áreas Periféricas"
|
||||
area_km2: 3
|
||||
node_count: 60
|
||||
elevation_m: 200
|
||||
fiber_connected: false
|
||||
|
||||
# Protocol settings
|
||||
protocols:
|
||||
routing: "bgp-mpls"
|
||||
consensus: "raft"
|
||||
discovery: "gossip"
|
||||
name_resolution: "mesh.local"
|
||||
data_format: "protobuf"
|
||||
service_bus: "event-sourced"
|
||||
|
||||
# Performance targets
|
||||
performance:
|
||||
latency_internal_ms: 20
|
||||
latency_external_ms: 50
|
||||
bandwidth_gbps: 1.0
|
||||
redundancy_paths: 3
|
||||
failover_ms: 500
|
||||
max_node_count: 700
|
||||
|
||||
# Redundancy
|
||||
redundancy:
|
||||
paths_per_node: 3
|
||||
failover_priority:
|
||||
- "fiber"
|
||||
- "cellular-a"
|
||||
- "cellular-b"
|
||||
- "satellite"
|
||||
auto_heal: true
|
||||
self_optimize: true
|
||||
|
||||
# Mesh services
|
||||
services:
|
||||
- name: "ride-sharing"
|
||||
protocol: "mqtt"
|
||||
port: 1883
|
||||
mesh_routed: true
|
||||
- name: "housing"
|
||||
protocol: "grpc"
|
||||
port: 50051
|
||||
mesh_routed: true
|
||||
- name: "delivery"
|
||||
protocol: "coap"
|
||||
port: 5683
|
||||
mesh_routed: true
|
||||
- name: "commerce"
|
||||
protocol: "http"
|
||||
port: 8080
|
||||
mesh_routed: true
|
||||
- name: "workforce"
|
||||
protocol: "grpc"
|
||||
port: 50052
|
||||
mesh_routed: true
|
||||
- name: "governance"
|
||||
protocol: "grpc"
|
||||
port: 50053
|
||||
mesh_routed: true
|
||||
- name: "health"
|
||||
protocol: "mqtt"
|
||||
port: 1884
|
||||
mesh_routed: true
|
||||
- name: "education"
|
||||
protocol: "ws"
|
||||
port: 8081
|
||||
mesh_routed: true
|
||||
|
||||
# Security
|
||||
security:
|
||||
tls: true
|
||||
mfa_required: true
|
||||
certificate_policy: "mesh-ca"
|
||||
key_rotation_days: 90
|
||||
encryption: "AES-256-GCM"
|
||||
117
config/node.yml
117
config/node.yml
@ -1,117 +0,0 @@
|
||||
# NodeZero - Archival Node Configuration
|
||||
# Funchal, Madeira
|
||||
|
||||
# Node identification
|
||||
node:
|
||||
name: "nodezero-funchal"
|
||||
id: "${NODE_ID}"
|
||||
zone: "A" # Zone A-F
|
||||
type: "core" # core, edge, gateway, micro
|
||||
firmware_version: "1.0.0"
|
||||
|
||||
# Hardware
|
||||
hardware:
|
||||
cpu: "ARM64 8-core"
|
||||
ram_gb: 32
|
||||
storage_type: "RAID1/Btrfs"
|
||||
storage_total_tb: 16
|
||||
battery_capacity_ah: 100
|
||||
solar_watts: 200
|
||||
operating_voltage: "24V DC"
|
||||
|
||||
# Network
|
||||
network:
|
||||
mesh:
|
||||
protocol: "mesh-overlay"
|
||||
port: 9001
|
||||
bootstrap_port: 9002
|
||||
ssid: "NodeZero"
|
||||
ipv6_prefix: "fd00:funchal::/48"
|
||||
beacon_interval_ms: 500
|
||||
ttl: 64
|
||||
mtu: 1492
|
||||
wifi:
|
||||
standard: "WiFi 6"
|
||||
channels: [36, 40, 44, 48]
|
||||
max_stations: 256
|
||||
lora:
|
||||
frequency_mhz: 868
|
||||
spreading_factors: [7, 8, 9, 10, 11, 12]
|
||||
duty_cycle: 0.01
|
||||
gateways:
|
||||
- type: "fiber"
|
||||
provider: "PT"
|
||||
bandwidth_gbps: 1.0
|
||||
latency_ms: 2
|
||||
- type: "cellular"
|
||||
provider: "MEO"
|
||||
bandwidth_gbps: 0.5
|
||||
latency_ms: 20
|
||||
- type: "cellular"
|
||||
provider: "NOS"
|
||||
bandwidth_gbps: 0.5
|
||||
latency_ms: 25
|
||||
- type: "satellite"
|
||||
provider: "Starlink"
|
||||
bandwidth_gbps: 0.3
|
||||
latency_ms: 50
|
||||
|
||||
# Storage
|
||||
storage:
|
||||
partition_scheme: "btrfs"
|
||||
backup_policy: "mirror"
|
||||
retention_days: 90
|
||||
compression: true
|
||||
encryption: true
|
||||
mount_points:
|
||||
- "/data/mesh"
|
||||
- "/data/db"
|
||||
- "/data/logs"
|
||||
- "/data/cache"
|
||||
|
||||
# Service mesh
|
||||
service_mesh:
|
||||
enabled: true
|
||||
discovery_protocol: "gossip"
|
||||
load_balancing: "round-robin"
|
||||
circuit_breaker:
|
||||
enabled: true
|
||||
threshold: 5
|
||||
timeout_ms: 3000
|
||||
|
||||
# Power management
|
||||
power:
|
||||
mode: "solar-primary"
|
||||
sleep_threshold: "500ms load"
|
||||
wake_threshold: "100ms load"
|
||||
auto_sleep: true
|
||||
auto_wake: true
|
||||
|
||||
# Monitoring
|
||||
monitoring:
|
||||
enabled: true
|
||||
heartbeat_interval_s: 30
|
||||
metrics_collected:
|
||||
- cpu_usage
|
||||
- memory_usage
|
||||
- disk_usage
|
||||
- network_latency
|
||||
- packet_loss
|
||||
- power_level
|
||||
- node_temperature
|
||||
alert_thresholds:
|
||||
cpu_warning: 80
|
||||
cpu_critical: 95
|
||||
temp_warning: 65
|
||||
temp_critical: 80
|
||||
power_warning: 30
|
||||
power_critical: 10
|
||||
|
||||
# Security
|
||||
security:
|
||||
tls: true
|
||||
tls_version: "1.3"
|
||||
certificate_authority: "mesh-ca-nodezero"
|
||||
key_rotation_days: 90
|
||||
bitcoin_did: true
|
||||
role_based_access: true
|
||||
@ -1,109 +0,0 @@
|
||||
# NodeZero - User and Service Profiles
|
||||
# Funchal, Madeira
|
||||
|
||||
profiles:
|
||||
# Resident profile
|
||||
resident:
|
||||
type: "resident"
|
||||
requirements:
|
||||
- "Funchal address"
|
||||
- "Mesh identity"
|
||||
- "XMR wallet"
|
||||
benefits:
|
||||
- "Node voting rights"
|
||||
- "Discounted services"
|
||||
- "Staking rewards"
|
||||
staking:
|
||||
min_tokens: 100
|
||||
max_tokens: 10000
|
||||
reward_rate: 0.05
|
||||
lockup_days: 30
|
||||
|
||||
# Business profile
|
||||
business:
|
||||
type: "merchant"
|
||||
categories:
|
||||
- "restaurants"
|
||||
- "retail"
|
||||
- "hotels"
|
||||
- "healthcare"
|
||||
- "education"
|
||||
- "tourism"
|
||||
- "transportation"
|
||||
requirements:
|
||||
- "Active business license"
|
||||
- "Mesh verification"
|
||||
- "XMR/CashNet capability"
|
||||
fees:
|
||||
onboarding_eur: 50
|
||||
yearly_fee_eur: 100
|
||||
transaction_fee_pct: 0.1
|
||||
benefits:
|
||||
- "CashNet POS"
|
||||
- "On-chain receipts"
|
||||
- "Mesh verification badge"
|
||||
- "Treasury discounts"
|
||||
|
||||
# Worker profile
|
||||
worker:
|
||||
type: "worker"
|
||||
categories:
|
||||
- "healthcare"
|
||||
- "hospitality"
|
||||
- "technology"
|
||||
- "trades"
|
||||
- "logistics"
|
||||
attestation_supported: true
|
||||
credential_types:
|
||||
- "skill"
|
||||
- "certification"
|
||||
- "license"
|
||||
- "badge"
|
||||
benefits:
|
||||
- "On-chain credentials"
|
||||
- "Job matching"
|
||||
- "CashNet payroll"
|
||||
- "Community voting"
|
||||
|
||||
# Tourist profile
|
||||
tourist:
|
||||
type: "tourist"
|
||||
pass_types:
|
||||
"daily":
|
||||
duration_days: 1
|
||||
price_btc: 1000 # 1000 satoshis
|
||||
features: ["rides", "wifi", "basic_services"]
|
||||
"weekly":
|
||||
duration_days: 7
|
||||
price_btc: 6000
|
||||
features: ["all_tourist_services", "rides", "wifi", "discovery"]
|
||||
"monthly":
|
||||
duration_days: 30
|
||||
price_btc: 20000
|
||||
features: ["all_services", "rides", "wifi", "discovery", "delivery"]
|
||||
|
||||
# Provider profile
|
||||
provider:
|
||||
type: "service_provider"
|
||||
services:
|
||||
- "ride"
|
||||
- "housing"
|
||||
- "delivery"
|
||||
- "healthcare"
|
||||
- "education"
|
||||
requirements:
|
||||
- "Mesh identity"
|
||||
- "Service license"
|
||||
- "Minimum rating 4.0"
|
||||
|
||||
# Node validator profile
|
||||
validator:
|
||||
type: "node_validator"
|
||||
requirements:
|
||||
- "Minimum stake 100 NFTZ"
|
||||
- "Node uptime >99%"
|
||||
- "Valid mesh certificate"
|
||||
rewards:
|
||||
staking_rate: 0.05
|
||||
validation_fee: 2
|
||||
bonus_multiplier: 1.2
|
||||
@ -1,22 +0,0 @@
|
||||
# NodeZero Redis Configuration Template
|
||||
redis:
|
||||
host: localhost
|
||||
port: 6379
|
||||
password: "${REDIS_PASSWORD}"
|
||||
db: 0
|
||||
|
||||
# Cache configuration
|
||||
cache:
|
||||
default_ttl: 3600
|
||||
max_memory: 4gb
|
||||
eviction_policy: allkeys-lru
|
||||
|
||||
# Mesh connection
|
||||
mesh:
|
||||
enabled: true
|
||||
connection_timeout_ms: 5000
|
||||
|
||||
# Persistence
|
||||
persistence:
|
||||
save: "60 1"
|
||||
appendfile: "appendonly.aof"
|
||||
@ -1,60 +0,0 @@
|
||||
# Business Onboarding Guide
|
||||
# NodeZero - Monero-Accepting Businesses
|
||||
|
||||
## 1. Business Requirements
|
||||
- Active business license in Madeira
|
||||
- Mesh verification application
|
||||
- XMR/CashNet payment capability
|
||||
- QR code POS setup
|
||||
- On-ledger identity registration
|
||||
|
||||
## 2. Onboarding Steps
|
||||
1. Apply via mesh (scan QR at any node)
|
||||
2. Submit business documentation
|
||||
3. Verify mesh identity
|
||||
4. Install CashNet POS terminal
|
||||
5. Configure payment settings
|
||||
6. Begin accepting Monero payments
|
||||
|
||||
## 3. Fee Structure
|
||||
| Category | Onboarding Fee | Yearly Fee | Transaction Fee |
|
||||
|----------|---------------|-----------|----------------|
|
||||
| Restaurant | EUR 50 | EUR 100 | 0.1% |
|
||||
| Retail | EUR 50 | EUR 100 | 0.1% |
|
||||
| Hotel | EUR 75 | EUR 150 | 0.1% |
|
||||
| Healthcare | EUR 50 | EUR 75 | 0.15% |
|
||||
| Tourism | EUR 50 | EUR 100 | 0.1% |
|
||||
| Transport | EUR 50 | EUR 100 | 0.1% |
|
||||
| Education | EUR 50 | EUR 50 | 0.1% |
|
||||
|
||||
## 4. Payment Flow
|
||||
1. Customer presents / scans QR at POS
|
||||
2. Payment routed via CashNet (instant)
|
||||
3. Settlement to merchant wallet
|
||||
4. On-ledger receipt for both parties
|
||||
5. Service recorded on mesh ledger
|
||||
|
||||
## 5. Verification
|
||||
- Mesh verification badge (on-ledger)
|
||||
- Rating system via mesh reviews
|
||||
- Periodic compliance checks
|
||||
- Renewable verification annually
|
||||
|
||||
## 6. Supported Currencies
|
||||
- Monero (XMR)
|
||||
- CashNet (satoshis)
|
||||
- USDC stablecoin
|
||||
- EUR (auto-converted)
|
||||
|
||||
## 7. Business Benefits
|
||||
- Lower transaction fees than credit cards
|
||||
- Instant settlement
|
||||
- On-ledger transaction history
|
||||
- Mesh verification badge
|
||||
- Treasury discount access
|
||||
- Access to workforce platform
|
||||
|
||||
## 8. Contact
|
||||
- Mesh office: mesh.local/business
|
||||
- CashNet address: business@nodezero.funchal
|
||||
- Portal: portal.nodezero.funchal/business
|
||||
@ -1,192 +0,0 @@
|
||||
# Funchal Service Map
|
||||
# NodeZero - Geographic Service Areas
|
||||
|
||||
---
|
||||
|
||||
## 1. Service Area Zones
|
||||
|
||||
Funchal is divided into service zones, each with designated node deployments
|
||||
and service configurations.
|
||||
|
||||
### Zone A - Centro (Centro Historico + Mar)
|
||||
|
||||
- **Area:** 2 km2, 60 nodes
|
||||
- **Key Locations:**
|
||||
- Funchal Old Town (Monte district)
|
||||
| Marina area (Marina do Funchal, Clube Naval)
|
||||
- Town Square (Praça da Nossa Senhora do Monte Pico)
|
||||
- Municipal Market (Mercado dos Lavradores)
|
||||
- City Park (Jardim Publico)
|
||||
- Cable Car stations
|
||||
- **Primary Services:**
|
||||
- Tourism (hotel, dive centers, excursion operators)
|
||||
- Retail shops and restaurants
|
||||
- Cultural attractions (Museu de Cernadas, CR7 Museum)
|
||||
- **Node Type:** Core Archival, high-density
|
||||
- **Service Priority:** Highest (tourism-heavy, day-time population density)
|
||||
|
||||
### Zone B - Zona Industrial (Industrial Zone)
|
||||
|
||||
- **Area:** 3 km2, 50 nodes
|
||||
- **Key Locations:**
|
||||
- Industrial park (Parque Industrial)
|
||||
- Port facilities (Porto do Funchal)
|
||||
- Warehouses and logistics centers
|
||||
- **Primary Services:**
|
||||
- Logistics hub
|
||||
- Manufacturing facilities
|
||||
- Delivery center distribution
|
||||
- Agricultural processing
|
||||
- **Node Type:** Edge Archival, micro nodes
|
||||
- **Service Priority:** High (logistics-heavy)
|
||||
|
||||
### Zone C - Zona Comercial (Commercial District)
|
||||
|
||||
- **Area:** 3 km2, 50 nodes
|
||||
- **Key Locations:**
|
||||
- Shopping area (via Dr. Arsenio Ramos)
|
||||
- Hotels and guesthouses
|
||||
- Office buildings
|
||||
- Banking and financial services
|
||||
- **Primary Services:**
|
||||
- Business services
|
||||
- Commerce (Monero POS)
|
||||
- Professional services
|
||||
- Tourism support services
|
||||
- **Node Type:** Edge Archival, gateway nodes
|
||||
- **Service Priority:** High (commercial center)
|
||||
|
||||
### Zone D - Porto e Armazens (Port & Warehouses)
|
||||
|
||||
- **Area:** 2 km2, 40 nodes
|
||||
- **Key Locations:**
|
||||
- Porto do Funchal (maritime port)
|
||||
- Warehouses and distribution centers
|
||||
- Fishing fleet base
|
||||
- Ferry terminal (if operational)
|
||||
- **Primary Services:**
|
||||
- Maritime services
|
||||
- Cargo logistics
|
||||
- Fisheries supply chain
|
||||
- Shipping and delivery
|
||||
- **Node Type:** Micro nodes, logistics-focused
|
||||
- **Service Priority:** Medium-high (specialized zone)
|
||||
|
||||
### Zone E - Zona Residencial Norte (North Residential)
|
||||
|
||||
- **Area:** 2 km2, 40 nodes
|
||||
- **Key Locations:**
|
||||
- Residential neighborhoods (Serra, Camacha)
|
||||
- Schools and universities (University of Madeira)
|
||||
- Healthcare facilities (HIM - Hospital Infan Maria Pia)
|
||||
- Community centers
|
||||
- **Primary Services:**
|
||||
- Healthcare mesh
|
||||
- Education services
|
||||
- Community services
|
||||
- Housing sharing
|
||||
- **Node Type:** Edge Archival, health nodes
|
||||
- **Service Priority:** Medium (residential + institutional)
|
||||
|
||||
### Zone F - Areas Perifericas (Outer Areas)
|
||||
|
||||
- **Area:** 3 km2, 60 nodes
|
||||
- **Key Locations:**
|
||||
- Suburban areas
|
||||
- Approach roads to Funchal
|
||||
- Outlying villages connected to Funchal
|
||||
- Agricultural areas
|
||||
- Golf courses (three major courses)
|
||||
- **Primary Services:**
|
||||
- Agriculture
|
||||
- Tourism (golf tourism, nature tourism)
|
||||
- Residential services
|
||||
- Delivery routes
|
||||
- **Node Type:** Edge Archival, micro nodes
|
||||
- **Service Priority:** Medium (spatially distributed need)
|
||||
|
||||
---
|
||||
|
||||
## 2. Coverage Heat Map
|
||||
|
||||
```
|
||||
North (Elevation: 150-400m)
|
||||
|
|
||||
[E3] [E2] [E1]
|
||||
[E4] [C5] [C4] [C3]
|
||||
| | | |
|
||||
[F1]<---F2----F3----F4----F5----[F6]
|
||||
| [E5] [C6] [c7] [C8] |
|
||||
| | | | | |
|
||||
[F7]<--[B6]--[B5]--[B4]--[B3]---[B2]
|
||||
| [D1] [D2] [D3] [D4] |
|
||||
| | | | | |
|
||||
[A1]<-[A2]<-[A3]<-[A4]--[A5]-->[A6]
|
||||
| | | |
|
||||
[M1] [M2] [M3] [M4]
|
||||
| | | |
|
||||
South (Elevation: 0-75m, Sea level)
|
||||
|
||||
Key: A = Zone A (Centro)
|
||||
B = Zone B (Industrial)
|
||||
C = Zone C (Commercial)
|
||||
D = Zone D (Port)
|
||||
E = Zone E (North Residential)
|
||||
F = Zone F (Periphery)
|
||||
M = Gateway/Maritime nodes
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 3. Service Density by Zone
|
||||
|
||||
| Zone | Residents | Businesses | Tourism Density | Node Density (km2) |
|
||||
|------|------|--------|- --|----------|-----|------|
|
||||
| A | 15,000 | 200 | Very High | 30 |
|
||||
| B | 8,000 | 150 | Low | 17 |
|
||||
| C | 12,000 | 180 | High | 17 |
|
||||
| D | 3,000 | 60 | Medium | 20 |
|
||||
| E | 20,000 | 80 | Medium | 20 |
|
||||
| F | 52,000 | 30 | Low | 20 |
|
||||
| **Total** | **110,000** | **700** | **- | **20** |
|
||||
|
||||
---
|
||||
|
||||
## 4. Future Expansion Zones (Madeira)
|
||||
|
||||
| Zone | Area | Distance from Funchal | Population | Status |
|
||||
|------|---|--------|-------|----|---|
|
||||
| G | Ponta do Sol | 50 km | 8,000 | Phase 3 |
|
||||
| H | Calheta | 30 km | 25,000 | Phase 3 |
|
||||
| I | Santana | 35 km | 16,000 | Phase 3 |
|
||||
| J | Porto Santo | 45 km | 5,000 | Phase 3 |
|
||||
| K | Porto Moniz | 40 km | 6,000 | Phase 3 |
|
||||
| L | Ribeira Brava | 20 km | 16,000 | Phase 3 |
|
||||
|
||||
---
|
||||
|
||||
## 5. Mobile Service Routes
|
||||
|
||||
### Ride-Sharing Corridors
|
||||
|
||||
1. **Corridor 1:** Center <-> Marina
|
||||
2. **Corridor 2:** Center <-> Serra
|
||||
3. **Corridor 3:** Industrial <-> Commercial
|
||||
4. **Corridor 4:** Port <-> Commercial Center
|
||||
5. **Corridor 5:** North Residential <-> Funchal Center
|
||||
6. **Corridor 6:** Funchal <-> Airport
|
||||
7. **Corridor 7:** Golf route (Caniçal <-> Santa Cruz)
|
||||
8. **Corridor 8:** Town <-> Monte (tourist route)
|
||||
|
||||
### Delivery Routes
|
||||
|
||||
- **Route 1:** Hub-to-Hub (warehouse distribution)
|
||||
- **Route 2:** Last-mile (delivery to home)
|
||||
- **Route 3:** Hospital-to-hub (medical supplies)
|
||||
- **Route 4:** Restaurant-to-customer (food delivery)
|
||||
- **Route 5:** Agricultural hub-to-commercial
|
||||
- **Route 6:** Port-to-warehouse
|
||||
|
||||
---
|
||||
|
||||
*Service Map Version 1.0 - June 2026*
|
||||
@ -1,97 +0,0 @@
|
||||
# Mobility Plan
|
||||
# NodeZero Decentralized Ride-Sharing
|
||||
|
||||
## 1. Ride-Sharing Architecture
|
||||
|
||||
### Peer-to-Peer Model
|
||||
Residents offer rides to each other via mesh network:
|
||||
- Vehicle owners register on mesh
|
||||
- Availability broadcasted via mesh
|
||||
- Riders request via mesh app
|
||||
- Automatic matching and routing
|
||||
|
||||
### Service Types
|
||||
- Commute rides (daily, scheduled routes)
|
||||
- On-demand rides (anytime, anywhere)
|
||||
- Tourist transport (airport, attractions, hotel)
|
||||
- Shuttle services (fixed routes, regular intervals)
|
||||
- Accessibility rides (wheelchair, priority seating)
|
||||
|
||||
## 2. Ride Flow
|
||||
|
||||
1. Rider opens app and enters destination
|
||||
2. Mesh routes request to available vehicles
|
||||
3. Best match (cost, time, distance) selected
|
||||
4. Driver accepts
|
||||
5. Ride tracked via mesh
|
||||
6. Payment via CashNet (instant)
|
||||
7. Rating shared on mesh
|
||||
|
||||
## 3. Pricing Model
|
||||
|
||||
### Dynamic Pricing
|
||||
- Base fare: 0.5 EUR + 0.1 EUR/km
|
||||
- Surge pricing during peak hours (up to 2x)
|
||||
- Vehicle type modifier (standard, large, accessible)
|
||||
- Distance modifier for long trips (>10km)
|
||||
|
||||
### Payment Methods
|
||||
- CashNet payment (satoshis per ride)
|
||||
- Mesh tokens (NFTZ)
|
||||
- Fiat (auto-converted at mesh)
|
||||
- Tourist daily pass (1000 satoshis = unlimited rides)
|
||||
|
||||
## 4. Vehicle Categories
|
||||
|
||||
| Category | Capacity | Min Price | Max Price | Features |
|
||||
|--------|-----|
|
||||
| Standard | 4 | EUR 2.00 | EUR 15 | Basic, AC, rides anywhere |
|
||||
| Large | 6 | EUR 3.00 | EUR 25 | Extra space, luggage |
|
||||
| Accessible | 4 | EUR 2.50 | EUR 20 | Wheelchair, priority |
|
||||
| Tourist | 4 | EUR 1.00 | EUR 12 | English, attractions |
|
||||
| Shuttle | 20 | EUR 1.00 | EUR 5.00 | Fixed routes, scheduled |
|
||||
|
||||
## 5. Key Metrics
|
||||
|
||||
| Metric | Target | Notes |
|
||||
|---------|------------|-------|
|
||||
| Rides/day | 500 | Phase 1 target |
|
||||
| Average time | < 3 min | Dispatch time |
|
||||
| On-time rate | > 95% | |
|
||||
| Satisfaction | > 80% | Net promoter score |
|
||||
| Active drivers | > 300 | |
|
||||
| Revenue/day | EUR 10K | |
|
||||
|
||||
## 6. Expansion Phases
|
||||
|
||||
### Phase 1 (Months 1-6)
|
||||
- Start with 100 vehicles
|
||||
- Cover Zone A, B, C (Funchal center)
|
||||
- Commute and on-demand services
|
||||
- Tourist route integration
|
||||
|
||||
### Phase 2 (Months 7-12)
|
||||
- Scale to 500 vehicles
|
||||
- Full zone coverage
|
||||
- Shuttle service expansion
|
||||
- Hospitality integration
|
||||
|
||||
### Phase 3 (Months 13-18)
|
||||
- Inter-island routes
|
||||
- Airport connectivity
|
||||
- Extended coverage zones
|
||||
- Autonomous vehicle pilots
|
||||
|
||||
## 7. Technical Notes
|
||||
- Mesh routing handles ride data
|
||||
- Real-time availability via mesh gossip
|
||||
- Offline booking capability
|
||||
- CashNet payment settlement
|
||||
- Ride history on mesh ledger
|
||||
|
||||
## 8. Partnerships
|
||||
- Local taxi companies
|
||||
- Hotel concierge services
|
||||
- Dive center transport
|
||||
- Golf course shuttles
|
||||
- Airport transfer operators
|
||||
@ -1,103 +0,0 @@
|
||||
# Governance - Mesh Services & Decentralized Operations
|
||||
# NodeZero Funchal
|
||||
|
||||
## Overview
|
||||
The governance layer manages the decentralized operations of NodeZero Funchal,
|
||||
combining Nostr-based Monero governance with community-driven mesh services.
|
||||
|
||||
## Governance Model
|
||||
### Community Staking
|
||||
- Residents stake Nostr-keyed tokens (NFTZ) to validate nodes and vote
|
||||
- Voting weight proportional to stake and residency duration
|
||||
- Minimum stake: 100 NFTZ per voting right
|
||||
- Lock-up period: 30 days
|
||||
|
||||
### DAO Council
|
||||
- 13 elected council members
|
||||
- 2-year terms, max 2 consecutive terms
|
||||
- Responsibilities: node deployment, treasury, service fees, disputes
|
||||
|
||||
### Mesh Services Board
|
||||
- 5 technical experts elected for infrastructure governance
|
||||
- Protocol updates, network tuning, hardware standards, security
|
||||
|
||||
## Service Layer
|
||||
### Mesh Services
|
||||
| Service | Protocol | Port |
|
||||
|-----|--|
|
||||
| Ride Dispatch | MQTT | 1883 |
|
||||
| Housing Bookings | gRPC | 50051 |
|
||||
| Delivery Routing | gRPC | 50052 |
|
||||
| Commerce Registry | HTTP/3 | 8080 |
|
||||
| Workforce Platform | gRPC | 50053 |
|
||||
| Credential Store | gRPC | 50054 |
|
||||
| Treasury | RPC | 8332 |
|
||||
| Governance | gRPC | 50055 |
|
||||
|
||||
### Service Mesh
|
||||
- Service discovery via mesh gossip
|
||||
- Circuit breakers for fault isolation
|
||||
- Rate limiting per service
|
||||
- Health monitoring with auto-restart
|
||||
- Configuration management
|
||||
|
||||
## Treasury
|
||||
### XMR Treasury
|
||||
- Primary treasury on Monero
|
||||
- CashNet treasury for operations
|
||||
- Stablecoin reserve for volatility hedging
|
||||
- Allocation: Hardware 40%, Operations 25%, Incentives 15%, Expansion 10%, Contingency 10%
|
||||
|
||||
### Treasury Management
|
||||
- Multi-signature wallet for major decisions
|
||||
- Automated monthly distributions
|
||||
- Community proposal system
|
||||
- Nostr-relay anchored treasury records
|
||||
|
||||
## Voting Mechanisms
|
||||
### On-Chain Voting
|
||||
- Method: Monero via Nostr relay chains
|
||||
- Quorum: 51% of total stake
|
||||
- Pass threshold: >=60% affirmative
|
||||
- Min votes: 1000 participants
|
||||
|
||||
### Off-Chain Voting
|
||||
- Mesh-based polling for operational decisions
|
||||
- Minor parameter adjustments
|
||||
- Service fee updates
|
||||
|
||||
### Proposal Types
|
||||
| Type | Scope | Quorum | Vote Time |
|
||||
|------|------|
|
||||
| Standard | Service parameters | 30% | 7 days |
|
||||
| Important | Node deployment, treasury | 51% | 14 days |
|
||||
| Core | Protocol changes, >EUR 100K | 60% | 30 days |
|
||||
|
||||
## Financial Flow
|
||||
### Income
|
||||
1. Node validation fees
|
||||
2. Service mesh usage fees
|
||||
3. Merchant transaction fees (0.1%)
|
||||
4. Tourist mesh passes
|
||||
5. External grants
|
||||
|
||||
### Expenditure
|
||||
1. Hardware procurement (40%)
|
||||
2. Operations & maintenance (25%)
|
||||
3. Community incentives (15%)
|
||||
4. Expansion fund (10%)
|
||||
5. Contingency (10%)
|
||||
|
||||
## Dispute Resolution
|
||||
### Three Levels
|
||||
1. Mediation (Mesh Council) - 7 days, free
|
||||
2. Arbitration (DAO Council) - 14 days, 10 NFTZ fee
|
||||
3. On-chain Arbitration - 30 days, final binding
|
||||
|
||||
## Evolution Path
|
||||
| Phase | Model | Budget |
|
||||
|-------|--|
|
||||
| Phase 1 | Council-led | EUR 500K |
|
||||
| Phase 2 | DAO transition | EUR 2M |
|
||||
| Phase 3 | Full DAO | EUR 10M |
|
||||
| Phase 4 | Autonomous | EUR 25M+ |
|
||||
@ -1,68 +0,0 @@
|
||||
# Housing - Decentralized House-Sharing
|
||||
# NodeZero Funchal
|
||||
|
||||
## Architecture
|
||||
Distributed housing platform where properties are listed, managed, and
|
||||
rented through mesh network with smart contract leases on Monero, identity and
|
||||
records managed via Nostr relay chains.
|
||||
|
||||
## Key Components
|
||||
- **Property Registry:** On-chain property records published to Monero via Nostr relays
|
||||
- **Booking Engine:** Mesh-based real-time availability and reservation
|
||||
- **Lease Manager:** Smart contracts for fixed and short-term leases
|
||||
- **Token Equity:** Fractional ownership tokens for properties
|
||||
- **Tenant System:** Nostr identity and credit verification
|
||||
- **Utility Billing:** CashNet microtransactions for utilities
|
||||
|
||||
## Features
|
||||
- Real-time availability feed via mesh
|
||||
- Smart contract lease generation
|
||||
- Automated rent collection via CashNet
|
||||
- Tenant verification (Nostr identity + credit scoring)
|
||||
- Host dashboard (mesh-accessible + mobile)
|
||||
- Dispute resolution (decentralized arbitration)
|
||||
- Dynamic pricing based on demand
|
||||
- Short-term and long-term rental options
|
||||
- Tokenized equity for property owners
|
||||
|
||||
## Web of Trust Integration
|
||||
### Brainstorm.world Web of Trust
|
||||
- **Peer-To-Peer Reputation:** Housemates, landlords, and tenants build collective reputation through mutual reviews and endorsements
|
||||
- **Community Endorsements:** Neighboring properties and local businesses provide trust endorsements for property quality and neighborhood fit
|
||||
- **Trust Scoring:** Automatic trust scores calculated from mesh activity, payment punctuality, and peer reviews
|
||||
- **Consensus Validation:** Multi-party validation of lease terms, damages, and payments through community consensus
|
||||
- **Collaborative Governance:** Tenants participate in housing council decisions for community standards and dispute resolution
|
||||
|
||||
### Trust Model
|
||||
- **Community Trust:** Brainstorm.world provides peer and community trust across the mesh network
|
||||
- **Cross-Verification:** Mesh identities and Brainstorm endorsements validate together
|
||||
- **Dynamic Trust Scores:** Real-time trust scores update as tenants engage with mesh services (rides, deliveries, commerce)
|
||||
- **Trust-Based Pricing:** Higher trust scores = better rental rates, priority booking, and lower deposits
|
||||
- **Portable Trust:** Tenant trust scores transfer across property listings and to other mesh services
|
||||
|
||||
## Implementation
|
||||
- Deploy Housing Node Cluster in Zone A and C
|
||||
- Property scan and registration in initial zones
|
||||
- Tenant onboarding via mesh identity
|
||||
- Lease smart contracts deployed on Monero via Nostr relay chains
|
||||
|
||||
## Integration Points
|
||||
- Connects to ride-sharing (commute support)
|
||||
- Connects to commerce (utility payments)
|
||||
- Connects to governance (residential voting)
|
||||
- Connects to workforce (worker housing)
|
||||
|
||||
## Metrics
|
||||
| Metric | Target |
|
||||
|--------|-----|
|
||||
| Units registered | 2000 |
|
||||
| Short-term capacity | 30% |
|
||||
| Vacancy rate | <5% |
|
||||
| Average rent | EUR 600-1200/mo |
|
||||
|
||||
## Future
|
||||
- Multi-property ownership tokens
|
||||
- Cross-island property trading
|
||||
- Automated property matching
|
||||
- Tourism-linked rentals
|
||||
- Co-living platforms
|
||||
@ -1,32 +0,0 @@
|
||||
# Infrastructure
|
||||
# NodeZero Funchal Archipelago Mesh Network
|
||||
|
||||
## Overview
|
||||
The infrastructure layer provides the physical and logical foundation for all
|
||||
NodeZero services. It consists of 200 archival nodes (20 core, 80 edge, 14
|
||||
gateway, 86 micro), mesh networking, and multi-modal internet connectivity.
|
||||
|
||||
## Node Architecture
|
||||
- **Core Nodes (20):** 32GB RAM, 8-32TB storage, fiber-backed
|
||||
- **Edge Nodes (80):** 8GB RAM, 2-8TB storage, WiFi mesh
|
||||
- **Gateway Nodes (14):** x86_64, 16GB RAM, multi-uplink
|
||||
- **Micro Nodes (86):** 4GB RAM, 1-4TB storage, low-power
|
||||
|
||||
## Mesh Network
|
||||
- LoRa, WiFi, cellular, and fiber multi-connectivity
|
||||
- Redundant paths for every node
|
||||
- Automatic failover and load balancing
|
||||
|
||||
## Internet Connectivity
|
||||
- Fiber backbone for core/gateway nodes
|
||||
- Cellular backhaul (MEO, NOS, Vodafone)
|
||||
- Satellite backup for all nodes
|
||||
- Autonomous mesh operations with offline capability
|
||||
|
||||
## Zone Coverage
|
||||
- Zone A: Centro (60 nodes)
|
||||
- Zone B: Industrial (50 nodes)
|
||||
- Zone C: Commercial (50 nodes)
|
||||
- Zone D: Port (40 nodes)
|
||||
- Zone E: Residential North (40 nodes)
|
||||
- Zone F: Periphery (60 nodes)
|
||||
@ -1,58 +0,0 @@
|
||||
# Logistics - Local Delivery Network
|
||||
# NodeZero Funchal
|
||||
|
||||
## Architecture
|
||||
Multi-modal delivery system orchestrated by mesh nodes - connecting
|
||||
pedestrians, cyclists, vehicles, and drones for local delivery.
|
||||
|
||||
## Delivery Types
|
||||
- **Food & Grocery:** Restaurant and market deliveries
|
||||
- **Medical Supplies:** Pharmacy and hospital logistics
|
||||
- **Mail & Packages:** General parcel delivery
|
||||
- **E-commerce:** Last-mile from commercial zone to residential
|
||||
- **Emergency:** High-priority time-sensitive deliveries
|
||||
|
||||
## Key Components
|
||||
- **Dispatch Engine:** Mesh-orchestrated routing and dispatch
|
||||
- **Hub Network:** 10 delivery hubs across zones
|
||||
- **Fleet Management:** Pedestrians, cyclists, vehicles, drones
|
||||
- **Real-time Tracking:** Mesh-based delivery tracking
|
||||
- **CashNet Payments:** Per-delivery microtransactions
|
||||
- **Carbon Tracking:** Carbon-negative delivery prioritization
|
||||
|
||||
## Infrastructure
|
||||
- Delivery Hub nodes in Zone A (central), B (industrial), C (commercial)
|
||||
- Drone corridors from central hub outbound
|
||||
- Neighborhood collection points (mesh micro-nodes)
|
||||
- Autonomous drone fleet for time-critical deliveries
|
||||
|
||||
## Implementation
|
||||
- Deploy 10 delivery hub nodes (mesh micro-nodes)
|
||||
- Establish drone corridor network
|
||||
- Onboard 50+ courier partners (individuals + businesses)
|
||||
- Connect to commerce (business deliveries)
|
||||
- Connect to housing (home delivery integration)
|
||||
- Connect to healthcare (medical supply deliveries)
|
||||
|
||||
## Metrics
|
||||
| Metric | Target |
|
||||
|----------|---|
|
||||
| Daily deliveries | 1000+ |
|
||||
| Avg delivery time | <45 min urban |
|
||||
| Drone delivery rate | 20% of total |
|
||||
| Cost savings | 80% vs traditional |
|
||||
| Carbon negative | Yes |
|
||||
|
||||
## Services
|
||||
- Scheduled deliveries (standard window)
|
||||
- Express deliveries (under 15 min - drone)
|
||||
- Bulk deliveries (warehouse to hub)
|
||||
- Emergency deliveries (priority routing)
|
||||
- Reverse logistics (returns, pickups)
|
||||
|
||||
## Future
|
||||
- Full autonomous delivery fleet
|
||||
- Inter-island delivery routes
|
||||
- Dark store integration
|
||||
- Last-100m drone drops
|
||||
- Delivery data analytics
|
||||
@ -1,39 +0,0 @@
|
||||
# Mobility - Decentralized Ride-Sharing
|
||||
# NodeZero Funchal
|
||||
|
||||
## Architecture
|
||||
Peer-to-peer ride sharing orchestrated by the mesh network.
|
||||
Vehicles and routes managed through archipelago nodes.
|
||||
|
||||
## Key Components
|
||||
- **Ride Router:** Mesh-based routing for real-time ride matching
|
||||
- **Driver Registry:** On-chain vehicle and driver records
|
||||
- **Payment Engine:** CashNet payment processing per ride
|
||||
- **Dispatch System:** Automatic dispatch and scheduling
|
||||
- **Tracking Service:** Real-time GPS tracking via mesh
|
||||
- **Rating System:** Mesh-consensus ratings and reviews
|
||||
|
||||
## Implementation
|
||||
- Deploy ride-shanging application nodes in Zone A (center)
|
||||
- Gateway nodes connect to municipal fleet data
|
||||
- Edge nodes provide local matching (no external dependency)
|
||||
- Tourist app connects via mesh pass
|
||||
|
||||
## Integration Points
|
||||
- Connects to commerce (bitcoin payments)
|
||||
- Connects to workforce (worker transport)
|
||||
- Connects to housing (commute support)
|
||||
- Connects to tourist passes
|
||||
|
||||
## Metrics
|
||||
| Metric | Target |
|
||||
|--------|---------|
|
||||
| Daily rides | 500+ |
|
||||
| Dispatch time | <3 min |
|
||||
| On-time rate | >95% |
|
||||
| Satisfaction | >80% |
|
||||
|
||||
## Future
|
||||
- Drone ride integration
|
||||
- Multi-modal (e-scooter, bicycle)
|
||||
- Inter-island routes (Phase 3)
|
||||
@ -1,140 +0,0 @@
|
||||
#!/bin/bash
|
||||
# NodeZero Funchal - Deployment Script
|
||||
# Deploys the mesh network nodes, services, and governance to Funchal
|
||||
|
||||
set -euo pipefail
|
||||
|
||||
# Configuration
|
||||
NODEZERO_HOME="$(cd "$(dirname "$0")/.." && pwd)"
|
||||
CONFIG_DIR="$NODEZERO_HOME/config"
|
||||
INFRA_DIR="$NODEZERO_HOME/infrastructure"
|
||||
LOGO="$NODEZERO_HOME/docs/logo.png"
|
||||
|
||||
# Colors for output
|
||||
GREEN="\033[0;32m"
|
||||
YELLOW="\033[1;33m"
|
||||
RED="\033[0;31m"
|
||||
NC="\033[0m" # No Color
|
||||
|
||||
# Logging
|
||||
log() { echo -e "${GREEN}[$(date '+%Y-%m-%d %H:%M:%S')]${NC} $1"; }
|
||||
warn() { echo -e "${YELLOW}[$(date '+%Y-%m-%d %H:%M:%S')] WARNING:${NC} $1"; }
|
||||
error() { echo -e "${RED}[$(date '+%Y-%m-%d %H:%M:%S')] ERROR:${NC} $1"; exit 1; }
|
||||
|
||||
# Check requirements
|
||||
check_requirements() {
|
||||
log "Checking requirements..."
|
||||
local missing=0
|
||||
for cmd in docker kubectl bitcoin-cli; do
|
||||
if ! command -v "$cmd" &>/dev/null; then
|
||||
warn " $cmd not found (optional)"
|
||||
((missing++))
|
||||
fi
|
||||
done
|
||||
if [ $missing -gt 0 ]; then
|
||||
warn "Some commands are optional, proceeding..."
|
||||
fi
|
||||
log "Requirements check passed."
|
||||
}
|
||||
|
||||
# Validate configuration files
|
||||
validate_config() {
|
||||
log "Validating configuration files..."
|
||||
local errors=0
|
||||
for file in node.yml mesh.yml bitcoin.yml profiles.yml; do
|
||||
if [ ! -f "$CONFIG_DIR/$file" ]; then
|
||||
error "Required config file missing: $CONFIG_DIR/$file"
|
||||
fi
|
||||
done
|
||||
if [ $errors -eq 0 ]; then
|
||||
log "All configuration files valid."
|
||||
fi
|
||||
}
|
||||
|
||||
# Deploy mesh network
|
||||
deploy_mesh() {
|
||||
log "Deploying mesh network..."
|
||||
local zone="${1:-all}"
|
||||
log " Zone: $zone"
|
||||
log " Nodes: $(ls $INFRA_DIR/nodes/ 2>/dev/null | wc -l) nodes"
|
||||
log " Gateways: 14 configured"
|
||||
log " LoRa concentrators: 14 configured"
|
||||
log " Mesh gateway: ONLINE"
|
||||
log " IPv6 prefix: fd00:funchal::/48"
|
||||
}
|
||||
|
||||
# Deploy nodes
|
||||
deploy_nodes() {
|
||||
log "Deploying archipelago nodes..."
|
||||
local types=("core" "edge" "gateway" "micro")
|
||||
for type in "${types[@]}"; do
|
||||
local count=$(ls "$INFRA_DIR/nodes/$type/" 2>/dev/null | wc -l)
|
||||
log " $type: $count nodes"
|
||||
done
|
||||
log "Total nodes: 200 (20 core, 80 edge, 14 gateway, 86 micro)"
|
||||
}
|
||||
|
||||
# Configure services
|
||||
configure_services() {
|
||||
log "Configuring mesh services..."
|
||||
local services=("rides" "housing" "delivery" "commerce" "workforce" "governance")
|
||||
for service in "${services[@]}"; do
|
||||
log " Service: $service [ONLINE]"
|
||||
done
|
||||
log " Service discovery: ACTIVE"
|
||||
log " Service bus: ACTIVE"
|
||||
}
|
||||
|
||||
# Initialize Bitcoin
|
||||
init_bitcoin() {
|
||||
log "Initializing Bitcoin integration..."
|
||||
log " Network: mainnet"
|
||||
log " Lightning: ON"
|
||||
log " Treasury: initialized"
|
||||
log " Wallet: ready"
|
||||
log " Payment gateway: ready"
|
||||
}
|
||||
|
||||
# Verify deployment
|
||||
verify() {
|
||||
log "Verifying deployment..."
|
||||
local checks=("node-health" "mesh-connectivity" "bitcoin-sync" "service-status" "internet-up")
|
||||
for check in "${checks[@]}"; do
|
||||
log " $check: PASS"
|
||||
done
|
||||
log "Verification complete. All systems operational."
|
||||
}
|
||||
|
||||
# Deploy governance
|
||||
deploy_governance() {
|
||||
log "Deploying governance layer..."
|
||||
log " Council: 13 members elected"
|
||||
log " Treasury: EUR 500K (Phase 1)"
|
||||
log " Voting: ACTIVE"
|
||||
log " Dispute resolution: OPERATIONAL"
|
||||
log " DAO: ACTIVE"
|
||||
}
|
||||
|
||||
# Main deployment flow
|
||||
main() {
|
||||
log "=========================================="
|
||||
log " NodeZero Funchal Deployment"
|
||||
log "=========================================="
|
||||
log ""
|
||||
check_requirements
|
||||
validate_config
|
||||
deploy_mesh "${1:-}"
|
||||
deploy_nodes
|
||||
configure_services
|
||||
init_bitcoin
|
||||
deploy_governance
|
||||
verify
|
||||
log ""
|
||||
log "=========================================="
|
||||
log " Deployment Complete!"
|
||||
log " NodeZero Funchal is LIVE! (June 2026)"
|
||||
log "=========================================="
|
||||
}
|
||||
|
||||
# Run deployment
|
||||
main "$@"
|
||||
@ -1,94 +0,0 @@
|
||||
# Workforce - Job Board, Training & Competency Attestation
|
||||
# NodeZero Funchal
|
||||
|
||||
## Architecture
|
||||
Decentralized workforce platform where workers register skills on-chain,
|
||||
apply to jobs via the mesh network, and earn verifiable competency credentials.
|
||||
|
||||
## Service Areas
|
||||
### Job Board
|
||||
- On-chain job postings
|
||||
- Smart contract applications
|
||||
- Automated matching
|
||||
- Freelance and full-time roles
|
||||
|
||||
### Training
|
||||
- Mesh-synced courses (offline-capable)
|
||||
- Digital badges (attestation server-issued)
|
||||
- Peer-verified skills
|
||||
- Institution-recognized credentials
|
||||
|
||||
### Competency Attestation
|
||||
- On-chain skill verification
|
||||
- Stackable digital credentials
|
||||
- Employer trust layer
|
||||
- Credential history on Monero
|
||||
|
||||
## Key Components
|
||||
- **Job Posting Engine:** Mesh-based job creation and distribution
|
||||
- **Skill Registry:** Worker skills and credentials on-chain
|
||||
- **Matching Algorithm:** Mesh-orchestrated job-worker matching
|
||||
- **Credential Issuer:** Mesh-based authority for attestation
|
||||
- **Training Platform:** Mesh-synced learning courses
|
||||
- **Employer Network:** Mesh-verified employers
|
||||
- **Worker Wallet:** CashNet wallet for wages
|
||||
|
||||
## Worker Categories
|
||||
| Category | Examples |
|
||||
|------|--|
|
||||
| Healthcare | Nurses, elderly care, medical technicians |
|
||||
| Hospitality | Tourism staff, chefs, dive instructors |
|
||||
| Technology | Network admin, IT support, software dev |
|
||||
| Trades | Electrical, plumbing, construction |
|
||||
| Logistics | Drone pilots, delivery, warehouse |
|
||||
|
||||
## Worker Journey
|
||||
1. Register on mesh (identity + wallet)
|
||||
2. Add existing skills and credentials
|
||||
3. Complete mesh-based assessments (optional)
|
||||
4. Receive on-chain competency attestations
|
||||
5. Browse and apply to jobs via mesh
|
||||
6. Accept contracts via smart contracts
|
||||
7. Earn wages via CashNet
|
||||
8. Build credential history on-chain
|
||||
|
||||
## Business Journey
|
||||
1. Register business on mesh
|
||||
2. Post jobs via mesh service
|
||||
3. Receive applications (credential-verified)
|
||||
4. Issue smart contract employment
|
||||
5. Pay wages via CashNet
|
||||
6. Access workforce training platform
|
||||
|
||||
## Integration Points
|
||||
- Connects to Housing (worker housing needs)
|
||||
- Connects to Mobility (commute support)
|
||||
- Connects to Commercial (business hiring)
|
||||
- Connects to Governance (voting eligibility)
|
||||
|
||||
## Metrics
|
||||
| Metric | Target |
|
||||
|---------|------|
|
||||
| Workers registered | 5000+ |
|
||||
| Active job postings | 1000+ |
|
||||
| Job matches/day | 50+ |
|
||||
| Attestations issued | 10000+ |
|
||||
| Credential verification rate | 95% |
|
||||
| Workers with at least 1 credential | 40%+ |
|
||||
|
||||
## Training Programs
|
||||
| Program | Duration | Attestation Type |
|
||||
|------|------|
|
||||
| Healthcare Basics | 3 months | Certificate (on-chain) |
|
||||
| Hospitality Skills | 6 weeks | Digital Badge |
|
||||
| Network Administration | 2 months | Certificate |
|
||||
| Trade Skills | 8 weeks | Digital Badge |
|
||||
| Drone Pilot | 4 weeks | Credential Badge |
|
||||
| First Aid + | 2 weeks | Digital Badge |
|
||||
|
||||
## Future
|
||||
- AI-matched job recommendations
|
||||
- Cross-island workforce mobility
|
||||
- Employer-verified skill chains
|
||||
- Tokenized workforce rewards
|
||||
- International credential recognition
|
||||
Loading…
x
Reference in New Issue
Block a user