> For the complete documentation index, see [llms.txt](https://whitepaper.virtuals.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.virtuals.io/virtuals-bai-pi-shu/xin-xi-zhong-xin/virtual-dai-bi-ai-dai-li-de-ji-chu-zi-chan/virtual-dai-bi-fen-pei-yu-dai-bi-jing-ji-xue.md).

# $VIRTUAL 代币分配与代币经济学

了解 $VIRTUAL 代币的分配与代币经济学，包括固定 10 亿供应量、公开流通、流动性池分配和生态金库。

### $VIRTUAL 代币经济学与供应分配

<figure><img src="https://4017910838-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Frrll8DWDA3BJwEBqOtxm%2Fuploads%2FlSiM8yBP68RvPuZmHuoo%2Fimage.png?alt=media&amp;token=2774a453-9123-45f5-a9d5-8e926477a12b" alt="$VIRTUAL token distribution and tokenomics allocation"><figcaption><p><strong>$VIRTUAL 代币在公开分发、流动性池和生态金库之间的分配。</strong></p></figcaption></figure>

**所有 $VIRTUAL 代币都已完全解锁并完成归属。**

$VIRTUAL 的总供应量为 1,000,000,000 枚代币。该供应量是铸造的，不会有未来通胀。它分配给 DAO 利益相关方。

### $VIRTUAL 代币分配

* **公开分发 — 60%：** 600,000,000 枚 $VIRTUAL 代币已进入公开流通。
* **流动性池 — 5%：** 50,000,000 枚 $VIRTUAL 代币分配给流动性池。
* **生态金库 — 35%：** 350,000,000 枚 $VIRTUAL 代币用于支持社区激励和 VIRTUAL 协议生态增长。

### 生态金库治理与释放

生态金库位于一个由 DAO 控制的多重签名钱包中。在接下来的三年里，其释放量每年不得超过 10%。部署需要治理批准。


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://whitepaper.virtuals.io/virtuals-bai-pi-shu/xin-xi-zhong-xin/virtual-dai-bi-ai-dai-li-de-ji-chu-zi-chan/virtual-dai-bi-fen-pei-yu-dai-bi-jing-ji-xue.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 `automate deployments from our CI pipeline` 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.