# How It Works EPIZO has three layers. Each one can be understood independently. Together they form a complete system. ### Layer 1 — The node (software) EPIZO node is a single application installed on any standard computer. It runs a management interface — called the Command Center — that orchestrates a set of specialized tools running alongside it.
ToolWhat it doesWorks offline?
OllamaRuns AI language models locally — no API, no cloud, no OpenAIYes — fully
QdrantVector database for AI knowledge search (RAG)Yes — fully
KiwixServes offline Wikipedia, medical refs, survival guides (.ZIM format)Yes — fully
KolibriKhan Academy education platform — full courses, multi-userYes — fully
ProtoMapsOffline regional maps — search, navigation, tile renderingYes — fully
CyberChefEncryption, hashing, encoding, data analysisYes — fully
FlatNotesLocal markdown note-taking and documentationYes — fully
The Command Center manages installation, updates, configuration, and real-time status for all tools. It is accessible through any browser on the local network at . Everything runs inside Docker containers — isolated, reproducible, and easy to update. The node operator does not need to know what Docker is. They just run the installer. ### Layer 2 — The mesh (connectivity) When internet connectivity is lost, EPIZO nodes in the same area do not go dark. They form a mesh — communicating with each other over local wireless networks. #### How the mesh works 1\. Each node continuously broadcasts its presence to the local network 2\. Nearby nodes discover each other automatically — no configuration required 3\. Content syncs between nodes over Wi-Fi, Bluetooth, or radio links 4\. Users connect to any node in range — their device gets full access to all services 5\. The mesh self-heals — if one node goes down, traffic routes through others The result: an offline node is not a single point of failure. A network of ten nodes in a neighborhood is a resilient, self-sustaining local internet — for as long as the hardware has power. ### Layer 3 — The protocol (Ethereum) The protocol layer is what transforms Project Epizo from a standalone offline system into a **global, self-sustaining network of resilient knowledge nodes**. While Epizo can run independently on any device, the Ethereum protocol layer enables coordination, incentives, transparency, and long-term sustainability without relying on any single company or centralized server. By launching on **Ethereum**, Epizo gains access to the most battle-tested smart contract ecosystem in the world — secure, decentralized, and trusted by millions. This creates a foundation where the project can grow for decades, not just years.\ **Hardware gives Epizo power. Ethereum gives Epizo permanence.** ### Why Launch on Ethereum Most offline systems eventually fail for one reason: * Funding disappears * Servers shut down * Owners lose interest * Communities fragment * No incentive exists to maintain infrastructure Project Epizo solves this through Ethereum. Ethereum allows Epizo to create an open economic layer where contributors, operators, educators, builders, and communities are rewarded for strengthening the network. Instead of depending on donations or a single founder, Epizo becomes **community-owned infrastructure**. ### What the Protocol Handles #### Staking — Commitment With Real Accountability Node operators stake **$EPIZO** tokens to register and participate in the network. Staking signals serious commitment to reliability, uptime, and quality service. Operators who abandon their nodes or repeatedly fail performance standards may lose part of their stake. This creates trust without needing centralized enforcement. Stake to serve. Earn by staying online. #### Proof of Uptime — Transparent Reliability The protocol continuously verifies whether registered Epizo nodes remain active and reachable. Availability proofs are recorded transparently through Ethereum-compatible systems, ensuring reward distribution is based on real contribution — not false claims. Reliable operators earn more. Neglected nodes earn less. This ensures the network grows through quality, not hype. #### Content Anchoring — Trusted Knowledge Every major Epizo content pack can be cryptographically fingerprinted and anchored on-chain: * Wikipedia snapshots * Medical databases * Educational libraries * Maps * AI models * Emergency response guides Any user or node can verify their local content matches the authentic approved version. This matters especially in times of: * misinformation * censorship * manipulated archives * disaster scenarios * disconnected regions Truth should be verifiable, even offline. #### DAO Governance — Community Controlled $EPIZO holders govern the future of the ecosystem through decentralized voting. The community can decide: * Which content collections receive priority updates * Treasury spending * Hardware grants for schools or remote regions * Node reward parameters * New integrations and AI tooling * Sustainability budgets * Ecosystem partnerships No single founder or company can unilaterally control Epizo. Those who build it should guide it. ### Sustainability Engine for Project Epizo The Ethereum layer is not just for tokens — it is the **long-term sustainability mechanism** of Epizo. Protocol revenues, treasury reserves, staking systems, and community governance can fund: * Continued software development * Security audits * Better AI integrations * Faster deployment tools * Open-source contributors * Global educational expansion * Hardware grants for underserved communities This means Epizo can continue improving even if the original creators step away. ### Why This Matters Offline infrastructure is too important to depend on charity or temporary enthusiasm. Project Epizo uses Ethereum so that: * contributors are rewarded * operators stay accountable * governance stays open * funding remains transparent * the ecosystem survives long-term ### The Vision A world where knowledge, AI, maps, and education remain available everywhere — funded by its own network, governed by its own community, and secured by Ethereum. **Epizo is not just software.**\ **It is sovereign infrastructure.** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.projectepizo.com/how-it-works.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.