> For the complete documentation index, see [llms.txt](https://whitepaper.venus.vip/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.venus.vip/vus-token-mechanism.md).

# VUS Token Mechanism

**VUS Distribution and Functionality**

In order to promote the construction of the Venus DAO ecosystem, Venus Foundation has issued the token VUS in the form of DAO governance. VUS serves as a medium of exchange for Venus DAO, providing users with various ecological rights and interests of Venus DAO, while VUS is widely used in ecological trading, circulation, and confirmation of rights.

**Governance Token**

VUS is the governance token of Venus DAO. Holders of VUS participate in the voting governance of Venus DAO, decide the future development of the organization and share the future value.

**Platform Token**

VUS is the Venus DAO eco-application platform Token, holding VUS can offset the commission and participate in the platform revenue sharing.

**Circulating Token**

In all Venus ecosystems, VUS acts as a circulation TOKEN, a valuation TOKEN, and performs all exchange functions.

## **VUS Issuance and Distribution**

Token Name: Venus Abbreviation: VUS

Issue number: 4100000000 pieces

<figure><img src="/files/7DjrR50ZBtuHuuNuwakG" alt=""><figcaption></figcaption></figure>


---

# 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, and the optional `goal` query parameter:

```
GET https://whitepaper.venus.vip/vus-token-mechanism.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.