> 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/guan-yu-virtuals-1/virtual-dai-bi-jing-ji-xue.md).

# $VIRTUAL 代币经济学

$VIRTUAL 代币地址（Base）：0x0b3e328455c4059EEb9e3f84b5543F74E24e7E1b \
\
$VIRTUAL 代币地址（ETH）：0x44ff8620b8cA30902395A7bD3F2407e1A091BF73\
\
$VIRTUAL 代币地址（Solana）：3iQL8BFS2vE7mww4ehAqQHAsbmRNCrPxizWAT2Zfyr9y\
\
$VIRTUAL 代币地址（Robinhood Chain）：0xc6911796042b15d7Fa4F6CDe69e245DdCd3d9c31<br>

## **$VIRTUAL 作为 Agent 代币的基础资产**

<figure><img src="https://4017910838-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Frrll8DWDA3BJwEBqOtxm%2Fuploads%2FvJdLSYipoEREKja1vXO6%2FIMG_3300.png?alt=media&amp;token=3b406e68-a05b-4819-a628-fb1aeab135c6" alt=""><figcaption></figcaption></figure>

* **流动性配对**: 每个单独的 agent 代币都在其各自的流动性池中与 $VIRTUAL 代币配对。创建一个新的 agent 需要一定数量的 $VIRTUAL 代币，这些代币用于建立该 agent 的流动性池。由于这些流动性池的锁定性质，这一过程会对 $VIRTUAL 代币产生通缩压力。
* **路由货币**: 当对 agent 代币有需求时，交易会通过 $VIRTUAL 代币进行路由。用户在购买任何 agent 代币之前，必须先将其 USDC（或其他货币）兑换为 $VIRTUAL。这一机制会在每次购买 agent 代币时持续为 $VIRTUAL 代币创造需求，类似于 ETH 或 SOL 分别在以太坊和 Solana 生态系统中充当基础货币的方式。

## **$VIRTUAL 促进链上 Agent 经济**

* **按推理付款**: 用户按使用次数为 AI agent 推理付费。这些付款通过链上从用户的钱包直接发送到 agent 的钱包，使用 $VIRTUAL 代币完成。


---

# 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/guan-yu-virtuals-1/virtual-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.
