> 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.1-main-token-gpad.md).

# 6.1 Main Token: GPAD

GPAD is a system-level functional token in the **GamePad** runtime execution infrastructure, and its core role is to provide a stable value anchor for long-term operation.

The design goal of GPAD is not high-frequency excitation, but rather for:

* Pricing and settlement benchmarks for operational resources and execution capabilities
* Used to acquire or unlock specific operating permissions, execution quotas, and long-term operating credits.
* Participate in parameter governance and rule coordination that are directly related to system stability
* As a value coordinating unit among agreement parties, operating nodes, and ecosystem participants.

In the **GamePad** system, GPAD is primarily responsible for ensuring the long-term, controllable operation of the system. Its value is intrinsically linked to the scale of system operation, execution requirements, and governance effectiveness.

**Total: 1,000,000,000 GPAD**

|           **Allocation Category**           | **Percentage** |    **Quantity**   |                                                                            **Design Description**                                                                           |
| :-----------------------------------------: | :------------: | :---------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
|     Operation and Ecological Incentives     |       35%      |    350,000,000    | Used for long-term operational contribution settlement, system-level incentives, and support for key operational roles, with release pace tied to actual operational scale. |
|  Ecological Development and Project Support |       20%      |    200,000,000    |      Supports integration with intelligent games, agent systems, and ecosystem protocols, with a focus on long-term cooperation and building fundamental capabilities.      |
|          Team and core contributors         |       20%      |    200,000,000    |         Incentivizes the core team's investment in system architecture, operational stability, and long-term engineering evolution (with long-term linear release).         |
| Early supporters and strategic partnerships |       10%      |    100,000,000    |                                   Early collaboration for key resource providers such as computing power, AI, engines, and infrastructure.                                  |
|       Reserves and governance buffers       |       15%      |    150,000,000    |                             Used for system governance, parameter tuning, and buffering against extreme operating pressure and long-term risks.                             |
|                  **Total**                  |    **100%**    | **1,000,000,000** |                                                                **Fixed total amount, no additional issuance**                                                               |


---

# 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:

```
GET https://gamepad-2.gitbook.io/gamepad-docs/gamepads-white-paper/6.-economic-model/6.1-main-token-gpad.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.