# 6.2 Token Allocation

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

### Community & Ecosystem (77%) <a href="#e853" id="e853"></a>

77% of $DUCK tokens are dedicated to the community and ecosystem development, divided into several key areas:

* **Airdrop (50%)**: 50% of $DUCK tokens are allocated to the community through airdrop campaigns, ensuring widespread distribution and adoption. The airdrop targets key user groups, including DuckChain Miniapp users, on-chain event participants, and AI DAO Genesis Members, rewarding active engagement and loyalty across the DuckChain ecosystem.
* **Liquidity (4%)**: 4% of tokens are reserved for liquidity provisioning, ensuring smooth operations within the DuckChain DeFi ecosystem and facilitating seamless transactions.
* **Marketing (3%)**: 3% of tokens are reserved for marketing initiatives to drive awareness, user engagement, and promote DuckChain’s expansion.
* **Ecosystem Growth (20%)**: 20% of tokens are allocated to support the development of the DuckChain ecosystem, including grants, dApp development, and partnerships to foster growth and sustainability.

### Investor (10%) <a href="#id-095d" id="id-095d"></a>

10% of $DUCK tokens are reserved for investors who have supported DuckChain, contributing to its initial growth and infrastructure.

### Team (10%) <a href="#b7b2" id="b7b2"></a>

10% of $DUCK tokens are allocated to the DuckChain team, ensuring the motivation and long-term commitment of the project’s core contributors.

### Advisor (3%) <a href="#id-265c" id="id-265c"></a>

3% of $DUCK tokens are set aside for advisors, offering them a stake in the project for their strategic guidance and support.


---

# 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://diary.duckchain.io/6.-usdduck-governance-and-ecosystem-token/6.2-token-allocation.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.