Mesh
The preceding part specified the cryptographic protocols that protect every message and key exchange in Zentalk -- from elliptic curve key agreement through the Signal Protocol's Double Ratchet to hybrid post-quantum constructions. Those protocols assume a network infrastructure capable of delivering encrypted payloads between endpoints without centralized intermediaries. This part describes that infrastructure.
Identity
The Identity Problem
Nodes
This chapter defines the concept of a node from first principles, surveys the role-differentiation strategies adopted by major distributed systems, and explains why Zentalk consolidates all infrastructure functions into a single unified Full Node type.
Zentamesh
This chapter provides the definitive architectural description of Zentamesh, the peer-to-peer overlay network that forms the infrastructure backbone of Zentalk. It establishes what Zentamesh is and what it is not, articulates the design rationale for a mesh architecture over the available alternatives, describes the conceptual operation of the system from data ingestion through delivery and expiration, differentiates Zentamesh from superficially similar decentralized networks, and analyzes the steady-state storage property that prevents unbounded resource growth.
Storage
The mesh storage layer provides fault-tolerant, encrypted data persistence across the Zentalk network. This chapter describes the complete architecture: from client-side encryption through Reed-Solomon erasure coding, Kademlia DHT-based distribution, capacity management, and automatic self-healing.
Routing
The relay routing network provides real-time message delivery between Zentalk users. This chapter describes the routing architecture: direct delivery for online users, durable offline queuing, multi-hop relay routing for metadata privacy, geographic optimization, and federation between relay servers.
Zentanode
The preceding chapters describe a network of software-based validator nodes connected to the public internet, relaying encrypted messages through a distributed hash table. That architecture assumes internet availability. This chapter addresses what happens when that assumption fails — and why a separate, hardware-based communication layer is not merely a feature enhancement but a structural necessity for any system that claims to provide private, censorship-resistant communication.
Offline Mesh
Offline Communication