# Token Use Cases — $EPIZO

## EPIZO Protocol — Token Use Cases & Tokenomics

***

### 🪙 Token Use Cases — $EPIZO

$EPIZO is **not a speculation vehicle**.\
It functions as the **coordination and incentive layer** of the protocol.

***

### ✅ What $EPIZO is Used For

#### **1. Staking — Activate a Node**

Operators must stake $EPIZO to register a node.\
This stake acts as a **commitment bond**.

* Minimum stake → accessible globally (including Global South)
* Higher stake → higher reward tiers
* Slashing → applies if node goes offline without warning

**Why this matters**\
Staking enforces accountability. Running a node is permissionless — maintaining it is not.

***

#### **2. Earning — Running Nodes**

Operators earn $EPIZO for verifiable contributions:

| Metric                | Description                                      |
| --------------------- | ------------------------------------------------ |
| **Uptime**            | Node is online and responsive (on-chain sampled) |
| **Content Freshness** | Matches latest verified content hash             |
| **Community Service** | Optional signed attestations of real-world usage |

**Why this matters**\
Rewards are based on **real participation**, not passive holding.

***

#### **3. Governance — DAO Voting**

All $EPIZO holders can participate in governance.

* Token-weighted voting
* Delegation supported
* Active operators gain governance multipliers over time

**DAO Decisions Include:**

* Content curation standards
* Hardware grant approvals
* Emission rate adjustments
* Protocol parameters (staking, slashing, rewards)
* Treasury allocation

***

#### **4. Institutional Access Fees**

Organizations (NGOs, governments, enterprises) pay $EPIZO for:

* Certified content collections
* SLA-backed deployments

> Individual/community usage remains **free**

**Impact:**\
Creates **non-inflationary treasury revenue**

***

#### **5. Grant Repayment Cycle**

Operators receiving hardware grants:

* Repay a portion via earned rewards
* Feed funds back into treasury

**Result:**\
A **self-replenishing funding loop** without constant token issuance

***

### ❌ What $EPIZO is NOT Used For

* Not a **yield farming token** (no passive LP rewards)
* Not a **governance-only token** (must be used to matter)
* Not a **payment token for users** (node access is free)
* Not a **wrapped asset** (native, purpose-built)

***

### 🔄 Token Flow Summary

| Actor             | Token Action      | Direction              | Purpose                              |
| ----------------- | ----------------- | ---------------------- | ------------------------------------ |
| Node Operator     | Stake $EPIZO      | Operator → Protocol    | Activate node, ensure accountability |
| Node Operator     | Earn $EPIZO       | Protocol → Operator    | Reward uptime, freshness, service    |
| Token Holder      | Vote              | Holder → DAO           | Governance participation             |
| NGO / Institution | Pay Fees          | Institution → Treasury | Access certified content             |
| DAO               | Distribute Grants | Treasury → Operator    | Fund node deployment                 |
| Grant Recipient   | Repay             | Operator → Treasury    | Sustain grant cycle                  |

***

## 📊 Tokenomics

***

### **Token Details**

| Property   | Value    |
| ---------- | -------- |
| Token Name | EPIZO    |
| Ticker     | $EPIZO   |
| Network    | Ethereum |
| Standard   | ERC-20   |

***

### **Supply Overview**

| Metric              | Value           |
| ------------------- | --------------- |
| Total Supply        | 10,000,000      |
| Initial Circulating | \~9,000,000     |
| Launch Type         | Fair Launch     |
| Inflation Model     | Declining Curve |

***

### 📦 Allocation Breakdown

| Allocation                | Amount         | % of Supply | Vesting                       |
| ------------------------- | -------------- | ----------- | ----------------------------- |
| Node Operator Rewards     | 500,000        | 5%          | 10 years, halving curve       |
| DAO Treasury              | 200,000        | 2%          | Controlled by DAO             |
| Core Team & Contributors  | 100,000        | 1%          | 4-year vest, 1-year cliff     |
| Ecosystem & Grants        | 100,000        | 1%          | DAO-approved quarterly unlock |
| Early Backers & Investors | 100,000        | 1%          | 3-year vest, 6-month cliff    |
| Public Launch & Liquidity | 9,000,000      | 90%         | Unlocked at TGE               |
| **TOTAL**                 | **10,000,000** | **100%**    |                               |

***

### 💰 Revenue Model — Reducing Inflation Dependency

EPIZO generates **real economic revenue**, not just token emissions:

* **Institutional licensing fees**\
  Paid in $EPIZO for certified content bundles
* **Enterprise node certification**\
  SLA-backed deployments with on-chain attestations
* **Grant repayment cycle**\
  Recycled funding from operator earnings

**Outcome:**

* Reduced reliance on inflation
* Sustainable treasury growth
* Real-world economic backing

***

### 🛡️ Anti-Inflation Design

* No pre-mine with immediate liquidity
* Staking required to earn rewards
* Slashing penalties for unreliable nodes
* Governance multipliers favor active contributors
* DAO-controlled emission adjustments

***

### 🏛️ DAO Treasury Usage

The treasury is fully governed by $EPIZO holders.

#### Intended Uses:

* Hardware grants (conflict zones, underserved regions)
* Developer bounties (protocol improvements, tooling)
* Security audits & smart contract reviews
* Ecosystem partnerships (NGOs, universities, healthcare)
* Operational reserves for long-term sustainability

***

### 🧠 Summary

$EPIZO is designed as:

> **A utility + coordination + incentive token — not a speculative asset**

It aligns:

* Infrastructure operators
* Governance participants
* Real-world institutions

Into a **self-sustaining decentralized ecosystem**


---

# 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/token-use-cases-usdepizo.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.