> For the complete documentation index, see [llms.txt](https://zeebu.gitbook.io/zbu-protocol-1.0/hvKFvzLoONc5kSQNlboc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zeebu.gitbook.io/zbu-protocol-1.0/hvKFvzLoONc5kSQNlboc/zbu-protocol/protocol-simplified.md).

# Protocol Simplified

## ZBU Protocol Overview

ZBU Protocol emerges as a groundbreaking *<mark style="color:orange;">**decentralized liquidity engine**</mark>* specifically engineered for the dynamic DeFi landscape. It integrates a sophisticated ecosystem involving multiple participant roles and innovative mechanisms to ensure efficient, secure, and decentralized settlements.

### <mark style="color:blue;">Ecosystem Participants</mark>

{% tabs %}
{% tab title="Delegators" %}

<table data-view="cards" data-full-width="true"><thead><tr><th align="center"></th><th align="center"></th><th align="center"></th><th></th><th data-hidden data-type="files"></th></tr></thead><tbody><tr><td align="center"><img src="/files/F9ykdjti8bvgJVNsVmTL" alt="" data-size="original"></td><td align="center"><strong>Contribution</strong></td><td align="center"><mark style="color:orange;">1 to 100,000 ZBU</mark></td><td></td><td></td></tr><tr><td align="center"><img src="/files/HTb7Wzv0viZXVCJ32CDs" alt=""></td><td align="center"><strong>Seats</strong></td><td align="center"><mark style="color:orange;">Unlimited</mark></td><td></td><td></td></tr><tr><td align="center"><img src="/files/2UCiWrjyRSfGnbeCUFz2" alt=""></td><td align="center"><strong>Verification</strong></td><td align="center"><mark style="color:orange;">None</mark></td><td></td><td></td></tr></tbody></table>
{% endtab %}

{% tab title="Deployers" %}

<table data-view="cards" data-full-width="true"><thead><tr><th></th><th align="center"></th><th align="center"></th><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><img src="/files/F9ykdjti8bvgJVNsVmTL" alt=""></td><td align="center"><strong>Min. Contribution</strong></td><td align="center"><mark style="color:orange;">$1,000,000 ~ ZBU</mark></td><td></td><td></td></tr><tr><td><img src="/files/HTb7Wzv0viZXVCJ32CDs" alt=""></td><td align="center"><strong>Seats</strong></td><td align="center"><mark style="color:orange;">300</mark></td><td></td><td></td></tr><tr><td><img src="/files/2UCiWrjyRSfGnbeCUFz2" alt=""></td><td align="center"><strong>Verification</strong></td><td align="center"><mark style="color:orange;">KYC/KYB</mark></td><td></td><td></td></tr><tr><td><img src="/files/OphYemTcZpYtiOhA3ZSJ" alt=""></td><td align="center"><strong>Reward</strong></td><td align="center"><mark style="color:orange;">0.60%</mark></td><td></td><td></td></tr></tbody></table>
{% endtab %}

{% tab title="OLPs" %}

<table data-view="cards" data-full-width="true"><thead><tr><th></th><th align="center"></th><th align="center"></th><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><img src="/files/F9ykdjti8bvgJVNsVmTL" alt=""></td><td align="center"><strong>Min.</strong> <strong>Contribution</strong></td><td align="center"><mark style="color:orange;">$1,000,000 ~ ZBU</mark><br><mark style="color:orange;">$3,000,000 ~ USDT</mark></td><td></td><td></td></tr><tr><td><img src="/files/HTb7Wzv0viZXVCJ32CDs" alt=""></td><td align="center"><strong>Seats</strong></td><td align="center"><mark style="color:orange;">Unlimited</mark></td><td></td><td></td></tr><tr><td><img src="/files/2UCiWrjyRSfGnbeCUFz2" alt=""></td><td align="center"><strong>Verification</strong></td><td align="center"><mark style="color:orange;">KYC/KYB</mark></td><td></td><td></td></tr><tr><td><img src="/files/OphYemTcZpYtiOhA3ZSJ" alt=""></td><td align="center"><strong>Rewards</strong></td><td align="center"><mark style="color:orange;">0.40%</mark></td><td></td><td></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

### <mark style="color:blue;">**Role of each ecosystem participants in the ZBU Protocol:**</mark>

{% tabs %}
{% tab title="Delegators" %}

* **Role**: Delegators are standard users who stake their ZBU tokens within the platform.
* **Process**: Upon staking ZBU, Delegators receive VeZBU tokens, which empower them with voting rights and influence within the ecosystem.
* **Rewards**: They earn daily rewards based on the amount of VeZBU staked and the activities performed by the Deployers they support.
  {% endtab %}

{% tab title="Deployers" %}

* **Role**: Deployers act as infrastructure providers critical to the platform’s functionality.
* **Eligibility**: To become a Deployer, participants must stake a significant amount of ZBU tokens.
* **Function**: They use their staked VeZBU to deploy settlement smart contracts. These contracts manage the settlement processes, leveraging the staked VeZBU to allow for the settlement of invoices up to the value of the VeZBU held.
* **Rewards**: Deployers earn a 0.60% fee on each transaction they facilitate, incentivizing them to maintain and expand their operations.
  {% endtab %}

{% tab title="On-Demand Liquidity Providers (OLPs)" %}

* **Role**: OLPs are liquidity providers who ensure that assets within the platform are sufficiently liquid.
* **Function**: They contribute to the liquidity pools, maintaining a specified ratio (typically 20-80 \[ZBU-USDC]) to balance the pool. This ratio ensures that there is enough liquidity available for the settlement cycles they support.
* **Rewards**: OLPs earn a 0.40% reward on each settlement cycle that utilizes their provided liquidity, encouraging them to commit more resources to the platform.
  {% endtab %}

{% tab title="Merchants" %}
**Role**

Merchants utilize the Zeebu PSP platform for Invoice settlements.&#x20;

**Responsibilities**

* Primarily, it includes telecom carriers using #ZBU for invoice settlements with their counter party.
  {% endtab %}
  {% endtabs %}

### <mark style="color:blue;">**Core Component of ZBU Protocol:**</mark>

{% tabs %}
{% tab title="Vault" %}

<figure><img src="/files/ufFmyvj4i4hX5iFVoHET" alt="" width="128"><figcaption></figcaption></figure>

* **Functionality**: The Vault is a staking mechanism where users can lock their ZBU tokens for a period ranging from 0 to 720 days.
* **Token Issuance**: Based on the amount and duration of the stake, participants receive VeZBU tokens. The longer the lock-in period, the higher the number of VeZBU tokens issued, enhancing the staker's influence and reward potential within the platform.
* **Usage**: VeZBU tokens are essential for participating in settlement cycles and earning rewards, serving as a key tool for governance and transaction validation.
  {% endtab %}

{% tab title="Liqudity Pool" %}

<figure><img src="/files/KLSxUNXVsvJ5t2yPpxov" alt="" width="128"><figcaption></figcaption></figure>

* **Structure**: The primary liquidity pool pairs ZBU with USDT, maintaining a 20-80 (ZBU-USDC) ratio to optimize liquidity availability versus demand.
* **Participation**: Liquidity providers contribute ZBU and USDT to the pool and receive LP tokens in return.
* **Incentives**: These LP tokens can be locked for periods of 6, 12, or 24 months, during which holders earn rewards based on the liquidity utilized in settlement cycles. This locking mechanism stabilizes the pool and ensures ongoing liquidity support.
  {% endtab %}
  {% endtabs %}

***


---

# 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, and the optional `goal` query parameter:

```
GET https://zeebu.gitbook.io/zbu-protocol-1.0/hvKFvzLoONc5kSQNlboc/zbu-protocol/protocol-simplified.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.