> For the complete documentation index, see [llms.txt](https://docs.global-entertainment-token.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.global-entertainment-token.org/ja/6-web3toux/62-noux.md).

# 6.2 三層資産設計のUX的意義

<figure><img src="/files/g00djbarhzewnx31zqlV" alt=""><figcaption></figcaption></figure>

GETは以下の3つの資産を用途に応じて使い分け、ストレスフリーな体験と高機能なエコノミーを両立させています。

<table><thead><tr><th width="136.583984375">レイヤー</th><th width="135.75390625">資産</th><th width="136.1572265625">役割</th><th>UX的意義</th></tr></thead><tbody><tr><td>オンチェーン</td><td>GET</td><td>中核トークン</td><td>Web3ユーザー向けの投資・支援・ステーキング・NFT決済</td></tr><tr><td>オフチェーン</td><td>GET Pay</td><td>決済通貨</td><td>Web2感覚でのQR支払いやチケット・物販決済を実現</td></tr><tr><td>オフチェーン</td><td>GET Miles</td><td>貢献報酬</td><td>行動が数値化され、可視化＆特典に変わる新しい評価軸</td></tr></tbody></table>

この構造により、ユーザーは「参加」「支援」「消費」「貢献」すべての行動が可視化され、報われるUXを享受できます。


---

# 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://docs.global-entertainment-token.org/ja/6-web3toux/62-noux.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.