> For the complete documentation index, see [llms.txt](https://docs.zaros.fi/overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zaros.fi/overview/zrs-token/tokenomics/zrs-supply-and-emissions.md).

# $ZRS Supply & Emissions

<figure><img src="/files/X7uAzHYGkgsYCeIh4tSa" alt=""><figcaption></figcaption></figure>

## Tokenomics Information

**Total Supply:** 1,000,000,000

**Initial Circulating Supply:** 95,929,470

**Wallet for Tokens Locked:**

* **Investors / Advisors / Core Contributors:** 0x7cc7e125d83a581ff438608490cc0f7bdff79127
* **Zaros Foundation (Treasury & Ecosystem & etc.):** 0xF510e630dEc6a37Df71792899418833409A9d098

### Token Distribution Breakdown:

* **Investors:** Allocation for early investors with a 6-month cliff and a 12-month vesting period.
* **Future Core Contributors:** Token allocation for upcoming core team members with cliff and vesting periods TBD.
* **IDO LBP:** Token allocation for the Initial DEX offering, to be launched through Fjord Foundry's [LBP](/overview/zrs-token/tokenomics/lbp-system.md). No cliff, no vesting.
* **Ecosystem Incentives (zPoints):** Includes incentives for initial protocol participation, ongoing incentives for protocol participation for the next 4 years, and airdrops.
* **Treasury:** Reserved tokens for operational needs, opportunistic fundraising, and ongoing expenses. 0,75% at TGE, no cliff, and vesting schedule TBD.
* **Advisory:** Tokens allocated to advisors with a 6-month cliff and an 18-month vesting period.
* **Core Contributors:** Token allocations for the core team members with a 6-month cliff and a 12-month vesting period.
* **Founders:** Token allocations for the founders with a 6-month cliff and a 24-month vesting period.

### Revenue Distribution

The Zaros Revenue Distribution system is responsible for managing the allocation of ETH real yield accrued by the protocol through fees paid by traders using Zaros' trading products.

* **70% to ZLP Vaults:** The majority of accrued ETH is sent to the ZLP Vaults LPs, since they're the ones market making to Zaros and creating its liquidity.
* **15% to veZRS Lockers**: This portion of the revenue generated is allocated to veZRS lockers, incentivizing long-term holding and participation in the ecosystem.
* **10% to the DAO Treasury:** This allocation is reserved for the DAO Treasury. This portion empowers the DAO with funds to support its decision-making processes.
* **5% for Buyback and Burn of ZRS**: The remaining revenue is used to buy back ZRS tokens from the market and subsequently burn them, reducing the overall supply.

It's important to note that these allocations are subject to change through future ZCCPs (Zaros Configuration Change Proposals), allowing for dynamism and adaptability in the revenue distribution strategy.<br>

### $ZRS Emission Schedule

This document provides a detailed breakdown of [$ZRS Emission](https://docs.google.com/spreadsheets/d/1yMTQQI9eEn9-fWusVcpaHGbOn7ISsvhO-6yoOpMzENQ/edit#gid=950169057).


---

# 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://docs.zaros.fi/overview/zrs-token/tokenomics/zrs-supply-and-emissions.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.