> For the complete documentation index, see [llms.txt](https://gamepad-2.gitbook.io/gamepad-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/6.-economic-model/6.3-division-of-uses-and-collaboration-between-dual-tokens.md).

# 6.3 Division of Uses and Collaboration Between Dual-Tokens

In **GamePad**'s economic system, the two tokens form a clear division of labor and a cooperative relationship:

**GPAD**

* System-oriented
* Solving the problem of "who can use the system and to what extent"
* Responsible for long-term operation of credit, resource pricing and governance coordination

**IPAD**

* For the operational phase
* Solving the problem of "who is continuously contributing value to the system's operation"
* Responsible for incentive distribution and operating revenue settlement

Together, they constitute an economic structure suitable for long-term operation:

* GPAD provides stable anchor points and rule boundaries for the operating system.
* IPAD provides continuous incentives and feedback for operational behavior.
* The system does not rely on exogenous subsidies, but is built upon real operational needs and contributions.

Through this dual-token design, **GamePad** incorporates both long-term operational stability and operational incentive efficiency into a controllable and evolving economic system, providing endogenous support for the large-scale operation of intelligent execution infrastructure.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/6.-economic-model/6.3-division-of-uses-and-collaboration-between-dual-tokens.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.