Network Architecture
Network Architecture
Mesh P2P VPN with distributed routing and verifiable paths.
Network Architecture Overview
Mesh VPN Architecture
Decentralized routing system:
Network Topology
Distributed peer-to-peer mesh
Dynamic routing based on health
Entry Nodes - Your traffic enters the mesh here. Multiple entry points for redundancy, geographically distributed.
Relay Nodes - Intermediate hops in the route. Each knows only previous and next hop. Onion-style routing for privacy.
Exit Nodes - Traffic exits to destination here. Choose exit location. Load-balanced across exit points.
Routing Protocol
Dynamic path selection:
Client requests route from entry to exit region
Routing algorithm selects path based on node health scores, latency metrics, geographic distribution, and load balancing
Establishes encrypted tunnel through selected nodes
Monitors route health continuously
Route Optimization
Multi-path routing for redundancy
Automatic failover to healthy routes
Latency-based path selection
Multi-layer encryption:
Each hop encrypted separately
Node A can't see what Node C knows
End-to-end encryption on top of hop encryption
ChaCha20-Poly1305 for speed
Curve25519 for key exchange
No logs of encryption keys
Health Monitoring
Real-time route health:
Metrics Tracked
Health indicator per hop (green/yellow/red)
Auto Re-routing
If hop degrades, re-route around it
Seamless transition (no connection drop)
User notification of route change
Health improvement triggers route recalculation
Community-run infrastructure:
Stable internet connection
Sufficient bandwidth allocation
Reputation System
Performance-based scoring
Reward multipliers for high-quality nodes
$MACRO earnings based on:
Geographic Distribution
Global coverage:
North America (US, Canada)
Europe (UK, Germany, Netherlands, France)
Asia (Singapore, Japan, Hong Kong)
Others (Australia, South America)
Exit Node Selection
Traffic Analysis Resistance
Prevent correlation attacks:
Timing Obfuscation
Packet size normalization
Flow Correlation Prevention
Different paths for different streams
Optimized for speed:
Overhead: ~15-25ms average added latency
Throughput: 80-95% of direct connection
Better than traditional VPNs (no single chokepoint)
Persistent connections where safe
UDP support for low-latency applications
Failover & Redundancy
Always-on connectivity:
Automatic Failover
If route fails, instant failover to backup
Multiple backup routes pre-computed
No user intervention required
Optional: block all traffic if VPN fails
Decentralized. Verifiable. Fast.
Last updated