# Token Allocation

The total supply of PUAD is **1,000,000,000 tokens**, and the allocation reflects a long-term strategy focused on sustainable growth, technical extensibility, and decentralized participation.

| Allocation Item           | Tokens      | Percentage | Purpose                                                                 |
| ------------------------- | ----------- | ---------- | ----------------------------------------------------------------------- |
| Community Incentives      | 350,000,000 | 35%        | Rewards for missions, identity systems, and early behavioral engagement |
| Developer & Plugin Grants | 200,000,000 | 20%        | To incentivize plugin developers, AI tool creators, and SDK integrators |
| Platform Ops & Liquidity  | 150,000,000 | 15%        | Operational costs, tech maintenance, bridge services, and DEX liquidity |
| Strategic Partnerships    | 100,000,000 | 10%        | Partner programs with AI firms, plugins, wallets, and Web3 toolkits     |
| Team & Core Contributors  | 150,000,000 | 15%        | Long-term vesting for team members building the ecosystem               |
| DAO Treasury Reserve      | 50,000,000  | 5%         | To be released via governance for protocol upgrades or ecosystem shifts |

***

**💡 Design Principles:**

* **Community First**: 35% dedicated to active users, not speculation
* **Developer-Led Growth**: 20% fuels plugin economy and AI integrations
* **Governance-Ready**: Reserve controlled by future DAO decisions, not centralized teams


---

# 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://pumpad.gitbook.io/pumpad/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.