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

# 4.3 WELVトークン設計（Tokenomics）

**基本情報**

| 項目    | 内容                                                                                                                   |
| ----- | -------------------------------------------------------------------------------------------------------------------- |
| トークン名 | <p>WELV（ウェルヴ）</p><div><figure><img src="/files/63loQb8MpAat6JBsdT8a" alt=""><figcaption></figcaption></figure></div> |
| 規格    | （チェーンは後日公開予定）                                                                                                        |
| 総発行量  | 1,000,000,000トークン                                                                                                    |
| 発行主体  | 株式会社ピクセラ（予定）                                                                                                         |

<br>

**アロケーション内訳**

WellthVerse のトークンアロケーションは、エコシステムの長期的・安定的な価値形成を最優先に設計します。\
配分比率は、ユーザーリワード、運営、パートナーシップ、トレジャリー、ガバナンス用 などに あらかじめ定められた割合で割り当てられます。

ただし、市場状況・事業提携・エコシステム成長などの要因により、配分変更が必要となる場合があります。\
その場合は透明性を持って公開し、ユーザー・ホルダーに共有 します。

詳細な割当比率は、後日公開予定です。


---

# 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-ja.wellthverse.com/token/tokenomics.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.
