# Tokenomics

### The tokenomics of **POI$ON** can be broken down as follows

* **Ticker: POI$ON**
* **Contract address:** See the [Contract List](/smart-contracts/contract-list.md)
* **Chain:** Arbitrum, BSC, and others
* **Total Supply: 10,610,000** **POI$ON**
* **Initial Supply**: 2,250,000
* There will be 3 **POI$ON** minted per Ethereum Block for the first 1 month and 1 **POI$ON** tokens minted per block afterwards for 4 years. Minting will be split between 3 chains Ethereum, Bsc, Arbitrum.

### Uniswap Liquidity

* **Ticker: POI$ON**
* **Contract address:** 0xa74eceae9c7670b019e0890881598b4c398d1c01
* **Chain:** Arbitrum
* **Supply:** 750,000
* **Listing Price:** $0.04

## **POI$ON Token Supply** <a href="#mirror-token-supply" id="mirror-token-supply"></a>

There will be a total of **10,660,000** **POI$ON** to be brewed over 4 years. After that MasterCastle will stop minting new **POI$ON** and only store them for distribution.

### Cumulative Distribution Schedule (in millions) <a href="#cumulative-distribution-schedule-in-millions" id="cumulative-distribution-schedule-in-millions"></a>

| ​                                | LGE      | Y1       | Y2       | Y3       | Y4        |
| -------------------------------- | -------- | -------- | -------- | -------- | --------- |
| Private Sale                     | 0.5      | 0        | 0        | 0        | 0         |
| Public Sale (ILO)                | 1        | 0        | 0        | 0        | 0         |
| Uniswap Liquidity                | 0.75     | 0        | 0        | 0        | 0         |
| pToken and **POI$ON** LP staking | **0**    | 3.01     | 2.6      | 1.9      | 0.9       |
| **Token supply**                 | **2.25** | **5.26** | **7.86** | **8.76** | **10.66** |
| Annual inflation (%)             | -        | 42%      | 27.08%   | 21.29%   | 17.77%    |

Total of 2.25**M** tokens will be available at Liquidity Generation Event. The distribution of these tokens will be made as below. For more info on these token sales, please see the [public and private sale](/appendix/public-and-private-sale-info.md) info.

* **Strategic sale**: 23% (0.5M) tokens will be allocated for Private Sale. Because of the initial investment these tokens are the same as public price for strategic investors who will help with the initial growth of the project. Funds transferred to the developer fund will be used for development of the system, advertising and marketing, airdrops, sponsoring new information websites for the ecosystem.&#x20;
* **Public Sale**: 44% (1M) tokens will be allocated for public sale. All funds going to Uniswap Liquidity.
* **Uniswap Liquidity**: 33.5% (0.75M) At the end of Public Sale will be used for Liquidity Generation on Uniswap.

Total supply of **POI$ON** tokens will increase for 4 years due to inflation, until the total token supply becomes **10.66M**. The distribution structure at the end of year 4 will look like the below:

* **Strategic Sale**: 4% (0.5M) tokens will be allocated for Private Sale. Because of the initial investment these tokens are the same as public price for strategic investors who will help with the initial growth of the project. Funds transferred to the developer fund will be used for development of the system, advertising and marketing, airdrops, sponsoring new information websites for the ecosystem.
* **Public Sale**: 8% (1M) tokens will be allocated for public sale. All funds going to Uniswap Liquidity.
* **Uniswap Liquidity**: 6% (0.75) tokens will be allocated for public sale. All funds going to Uniswap liquidity.
* **Potion and POI$ON LP Staking:** 82% (10.36M) minted over 4 years. Distributed **ONLY** as an award to support conduct that secures the ecosystem.


---

# Agent Instructions: 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.poison.finance/protocol/tokenomics.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.