# Roadmap

EPIZO. Protocol develops in four phases. The software foundation already exists and is production-ready. The protocol layer builds on top.

> **From working software → decentralized offline infrastructure**
>
> The core system already exists.\
> The protocol layer is what scales it globally.

### 🧭 Phases Overview

Phase 0 → Foundation ✅\
Phase 1 → Protocol Launch ⚡\
Phase 2 → DAO Activation 🏛️\
Phase 3 → Full Offline Autonomy 🌐\
Phase 4 → Ubiquity (Run Anywhere) 📱\ <br>

## 🧱 Phase 0 — Foundation

**Status:** Q2–Q4 2025 ✅ Complete (Now in Beta)

> The infrastructure already works. This is not theoretical.

#### 🔧 Core Stack

* Open-source (Apache 2.0) by Crosstalk Solutions
* Command Center (AdonisJS + React + Docker orchestration)
* Fully integrated services:
  * Ollama (AI inference)
  * Qdrant (RAG / vector DB)
  * Kiwix (offline Wikipedia)
  * Kolibri (education)
  * ProtoMaps (maps)

#### ⚙️ System Capabilities

* BullMQ job system (downloads, embeddings, model pulls)
* Content collections (ZIM + maps + versioned manifests)
* One-command install (Debian/Ubuntu)

***

## ⚡ Phase 1 — Protocol Mainnet Launch & Operator Beta

**Timeline:** Q1–Q2 2026

> Turning software into a **coordinated network**

#### ⛓️ Protocol Layer

* Smart contracts (staking, rewards, DAO) → Ethereum testnet
* Content hash anchoring (verifiable datasets)
* $EPIZO Token Generation Event (TGE)

#### 🧑‍💻 Operator Experience

* Node dashboard:
  * uptime tracking
  * staking status
  * reward preview

#### 🌍 Ecosystem

* Discord launch (Operators / Builders / Stakers)
* Security audit (third-party)
* First DAO proposal → **hardware grants (conflict zones)**

#### 🔗 Networking

* Mesh networking (PoC)
* Local Wi-Fi node sync testing

***

## 🏛️ Phase 2 — DAO Activation

**Timeline:** Q3 2026

> Governance + real incentives go live

#### 💰 Token Utility Live

* Staking portal → earn real $EPIZO
* First on-chain governance vote

#### 🌐 Network Expansion

* 1,000 staked nodes target
* 30+ countries coverage

#### 🤝 Real-World Adoption

* NGO & institutional partnerships
* Hardware grant program opens

#### 📦 Ecosystem Features

* Content marketplace (region/language/use-case bundles)
* Mobile companion app (iOS + Android)

#### 🌍 Field Testing

* Mesh mode tested in real crisis deployments

***

## 🌐 Phase 3 — Full Local Operation (Protocol Optional)

**Timeline:** Q4 2027

> The system survives **without the protocol**

#### 🔌 Offline Independence

* Node runs fully standalone
* No internet ever required

#### 🔄 Offline Staking

* Rewards continue offline
* Sync happens later (batch submission)

#### 📡 Advanced Mesh

* Peer-to-peer content sync
* No internet required

#### 📈 Network Scale

* 5,000+ nodes
* 50+ countries

#### 🏛️ Governance Evolution

* First DAO council
* Representation from conflict regions

#### 💰 Economic Shift

* Treasury becomes self-sustaining
* Real revenue > token emissions

***

## 📱 Phase 4 — Any Device, Anywhere

**Timeline:** Q3 2026+

> EPIZO becomes **ubiquitous infrastructure**

#### 📲 Platform Expansion

* Native Android node (phone = server)
* Full ARM support (low-cost hardware globally)
* EPIZO Lite (<1GB RAM devices)

#### 🌐 Accessibility

* Browser-based node access
* No install required

#### 🔄 New Capabilities

* Node-to-node content trading
* Local storage economy

#### 📊 Network Goals

* 10,000+ nodes
* Global resilience coverage

#### 🏛️ DAO v2

* Quadratic voting
* Community council system

#### 🚀 Infrastructure Evolution

* Decentralized content CDN
* Nodes earn by serving other nodes

***

## 📊 Current Status Snapshot

| Capability                             | Status               | Target Phase |
| -------------------------------------- | -------------------- | ------------ |
| Core offline node software             | ✅ Live (Open Source) | Complete     |
| AI assistant (Ollama + RAG)            | ✅ Live               | Complete     |
| Offline knowledge (Wikipedia, medical) | ✅ Live               | Complete     |
| Offline education (Kolibri)            | ✅ Live               | Complete     |
| Offline maps (ProtoMaps)               | ✅ Live               | Complete     |
| Docker orchestration                   | ✅ Live               | Complete     |
| Smart contracts                        | 🚧 In development    | Phase 1      |
| DAO governance                         | 🚧 Preparing mainnet | Phase 1–2    |
| Staking & rewards                      | 🧪 In design         | Phase 2      |
| Mesh networking                        | 🧪 Proof of concept  | Phase 2–3    |
| Offline staking                        | 📌 Planned           | Phase 3      |
| Android / ARM node                     | 📌 Planned           | Phase 4      |

***

## 🧠 Final Perspective

> **Most projects start with a token and promise software later.**\
> **EPIZO starts with working infrastructure — and adds coordination on top.**

***

### 🧩 One-line Summary

**Phase 0:** Build it\
**Phase 1:** Tokenize it\
**Phase 2:** Govern it\
**Phase 3:** Decouple it\
**Phase 4:** Scale it globally


---

# 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/roadmap.md?ask=<question>
```

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.