> For the complete documentation index, see [llms.txt](https://usdtzed-1.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usdtzed-1.gitbook.io/whitepaper/tokenomics.md).

# Tokenomics

The **USDT.z** token economy is designed to ensure **long-term stability**, **liquidity**, and **ecosystem growth** while maintaining the integrity of its **1:1 USD peg**. The allocation strategy prioritizes adoption, community involvement, and sustainable development.

***

#### **Token Specifications**

| Attribute          | Details                    |
| ------------------ | -------------------------- |
| **Token Name**     | Tether USD Bridged ZED 2.0 |
| **Symbol**         | USDT.z                     |
| **Token Standard** | BEP20                      |
| **Decimals**       | 18                         |
| **Network**        | Binance Smart Chain        |
| **Total Supply**   | 27,500,000,000 USDT.z      |
| **Peg**            | 1 USDT.z = 1 USD           |

***

#### **Token Allocation**

| Allocation Category          | Percentage | Amount (USDT.z) | Purpose                                                         |
| ---------------------------- | ---------- | --------------- | --------------------------------------------------------------- |
| **Public Circulation**       | 60%        | 16,500,000,000  | Liquidity, trading pairs, and ecosystem use                     |
| **Ecosystem Development**    | 15%        | 4,125,000,000   | DeFi partnerships, dApp integration, cross-chain expansion      |
| **Community Incentives**     | 10%        | 2,750,000,000   | Staking rewards, airdrops, liquidity mining                     |
| **Team & Advisors**          | 7%         | 1,925,000,000   | Development team, strategic advisors (vesting schedule applied) |
| **Reserve & Stability Fund** | 8%         | 2,200,000,000   | Market stability, peg maintenance, and emergency liquidity      |

***

#### **Distribution Strategy**

* **Initial Launch:** USDT.z is distributed across multiple platforms, including centralized exchanges (CEXs) and decentralized exchanges (DEXs).
* **Liquidity Provision:** Strategic pairing with major cryptocurrencies (BTC, ETH, BNB) to ensure market depth.
* **Vesting:** Team and advisor tokens are subject to a **24-month vesting schedule** to align with long-term project growth.
* **Reserve Fund Management:** Reserve tokens are held in decentralized, multi-signature wallets for peg stability and emergency liquidity.

***

#### **Supply Management**

* **Minting:** New tokens are only minted to match verified USD-pegged reserves.
* **Burning:** Tokens are burned when taken out of circulation to maintain peg integrity.
* **Transparency:** All supply changes are visible on-chain and trackable through blockchain explorers and public dashboards.

***

**In essence:**\
USDT.z’s tokenomics ensure **stability, growth, and trust**, balancing liquidity needs with community incentives and development funding — all under a transparent, decentralized model.


---

# 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://usdtzed-1.gitbook.io/whitepaper/tokenomics.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.