> For the complete documentation index, see [llms.txt](https://docs.tenzorassets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tenzorassets.com/tenzor-tokenomics/usdtnzr/usdtnzr-coin.md).

# $TNZR Coin

### **Overview**

\
TNZR is the backbone of the Tenzor ecosystem—both a utility and governance token rolled into one. It's used for staking, settling fees, driving protocol decisions, and powering user incentives. Distribution has been handled with care to ensure all key players are aligned, from early supporters and institutional partners to the wider community. At its core, TNZR is built to foster decentralization, encourage steady growth, and maintain the long-term health of the network.

<table data-header-hidden data-full-width="false"><thead><tr><th></th><th></th><th></th><th width="335.21435546875"></th></tr></thead><tbody><tr><td><strong>Category</strong></td><td><strong>Allocation</strong></td><td><strong>Amount (TNZR)</strong></td><td><strong>Vesting Schedule</strong></td></tr><tr><td>Ecosystem Incentives</td><td>30%</td><td>150,000,000</td><td>Emitted over 5 years, linear, DAO-governed</td></tr><tr><td>Team &#x26; Core Contributors</td><td>20%</td><td>100,000,000</td><td>1-year cliff, then 3-year linear vesting</td></tr><tr><td>Private Round</td><td>15%</td><td>75,000,000</td><td>20% on TGE, then 1 year linear vesting</td></tr><tr><td>RWA Liquidity Mining</td><td>15%</td><td>75,000,000</td><td>Based on staking participation &#x26; duration</td></tr><tr><td>Treasury &#x26; DAO Reserves</td><td>10%</td><td>50,000,000</td><td>Vested linearly, used via DAO governance</td></tr><tr><td>Partnerships &#x26; Ecosystem</td><td>5%</td><td>25,000,000</td><td>Custom vesting per partnership agreements</td></tr><tr><td>Advisors</td><td>3%</td><td>15,000,000</td><td>12-month cliff, then 24-month vesting</td></tr><tr><td>Public Sale</td><td>2%</td><td>10,000,000</td><td>TGE unlock: 10%,  Monthly Vesting 10%</td></tr></tbody></table>

`0x88a2e6bcc6cdfbbdf78f7357ff4403dcc0f36917`

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

#### The Utility of TNZR

TNZR isn’t just another token. It plays a central role across the Tenzor ecosystem, weaving into everything from staking and governance to bridging and real-world asset integration.

**1. Staking Rewards**

By staking TNZR, users can help secure protocol vaults and, in return, earn yield. Those who lock up RWA tokens can even unlock enhanced rewards—making long-term participation more attractive.

**2. Protocol Fees**

Fees within the Tenzor network—whether for transactions, vault performance, or tokenization—can be paid using TNZR. In many cases, doing so offers a discounted rate, giving token holders an edge.

**3. Governance**

With TNZR in hand, users gain voting power in the Tenzor DAO. This means influence over big-picture decisions: launching new vaults, adjusting reward rates, deciding how treasury funds are used, and refining compliance policies.

**4. Yield Boosting**

Want higher returns? Lock TNZR to amplify your yield multiplier. This system takes inspiration from vote-locking mechanisms seen in other DeFi ecosystems and rewards users who commit.

**5. Cross-Chain Utility**

TNZR isn’t confined to one chain. It’s bridgeable by design and grants access to vaults and incentives across Ethereum, Binance smart-chain and supported Layer 2s.

***

####

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

[`https://bscscan.com/token/0x88a2e6bcc6cdfbbdf78f7357ff4403dcc0f36917`](https://bscscan.com/token/0x88a2e6bcc6cdfbbdf78f7357ff4403dcc0f36917)

#### Emission Schedule: Designed for Longevity

TNZR has a hard cap—500 million tokens. There’s no inflation. Instead, emissions decline over five years, front-loading rewards for early adopters and liquidity providers.

* **Year 1:** 35% allocated to ecosystem incentives and RWA participation
* **Year 2:** 25%
* **Year 3:** 20%
* **Year 4:** 12%
* **Year 5:** 8%

If needed, the DAO can propose tweaks to this schedule based on market dynamics and user growth.

***

#### Governance: A Gradual Decentralization

Initially, governance will be semi-centralized, handled by a multisig wallet controlled by the core team and early advisors. But that won’t last forever. Within 18 months, all decision-making will transition to TNZR stakers and DAO members via on-chain voting.

***

#### Deflation Mechanism: Optional, Strategic

The protocol may periodically burn a portion of TNZR collected from fees—though this depends on DAO approval. If network revenue surpasses certain thresholds, this deflationary tool can help counter dilution and strengthen token value.

***

#### Liquidity: Built for Cross-Chain Access

To ensure smooth access and reduce slippage, liquidity will be distributed across several channels: public sales, protocol-owned liquidity, and incentivized pools on Uniswap,Reya AMM, and partner DEXs. Cross-chain pools will make sure users aren’t boxed into a single network.


---

# 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.tenzorassets.com/tenzor-tokenomics/usdtnzr/usdtnzr-coin.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.
