# 3. Tokenomics

#### 3.1 Token Overview

* Name: AIFin Token (AITO)
* Total Supply:1,100,000,000,000
* Chain: BSC
* Utilities: Governance, staking rewards, transaction fees, ecosystem access.

#### 3.2 Allocation

| Category               | Share | Description                                                                  |
| ---------------------- | ----- | ---------------------------------------------------------------------------- |
| Team & Foundation      | 5%    | Dev & Ops support. 6-month lock, 4-year linear vesting.                      |
| Community Incentives   | 65%   | Yield farming, governance rewards, node staking. Dynamic distribution.       |
| Ecosystem Fund         | 10%   | Dev tools & partnerships. 6-month lock, 1-year linear vesting.               |
| Private & Public Sales | 5%    | Early backers. 6-month lock, 3-year linear vesting.                          |
| Reserve Pool           | 5%    | Market volatility & expansion. DAO-controlled. 6-month lock, 3-year release. |
| Liquidity Provision    | 3%    | CEX/DEX liquidity. 20% TGE, 12-month linear release.                         |
| Marketing & Ops        | 7%    | Ongoing market & operational support. 6-month lock, 3-year release.          |

#### 3.3 Deflationary Mechanisms

* Buyback & Burn: 30% of fees used to burn AITO, reducing supply.
* Governance Deposit: Failed proposals burn their AITO collateral.
* Cross-chain Collateral: Locked AITO in bridging operations gradually released.


---

# 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://aifin-1.gitbook.io/aifin/3.-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.
