> 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/5.-token-and-point-design/5.2-role-of-each-asset-and-use-cases.md).

# 5.2 Role of each asset and use cases

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

**\[GET Token] - Core On-chain Asset  -**

* Project support/crowdfunding participation
* Governance voting and proposals
* NFT and RWA payments
* Conversion to GET Pay
* Getting rewarded by staking
* Getting benefits/preferences/exclusive access

**Key Characteristics:**

* Native token on Cardano blockchain
* Market-driven price fluctuations
* Conditional operation with smart contract\ <br>

**【GET Pay】 - Daily settlement currency (off-chain)**

* QR code settlement for live performances, exhibitions and merchandise sales
* Fan club memberships and content tipping
* Partial settlement method for NFT/RWA

**Conversion rules:**

* GET → GET Pay: Convertible at a dynamic rate
* GET Pay → GET: Non-convertible

**Key Characteristics:**

* Instant processing without gas fees
* Smooth, Web2-like payment UX
* GET Miles are automatically awarded based on usage

&#x20;

**【GET Miles】 - Contribution Reward points (off-chain) -**

* Automatically awarded according to actions such as support, participation, voting, and sending out messages
* Royalty function to visualize user “heat level”

&#x20;

Example of awarding (behavior-based scoring)

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Activity</td><td valign="top">Award Miles(Example)</td></tr><tr><td valign="top">Live Show/Event Participation</td><td valign="top">+10 Miles</td></tr><tr><td valign="top">Vote Participation</td><td valign="top">+5 Miles</td></tr><tr><td valign="top">SNS Posting and broadcasting</td><td valign="top">+3~20 Miles</td></tr><tr><td valign="top">Staking Expires</td><td valign="top">+Bonus Miles</td></tr><tr><td valign="top">Long Term Holder</td><td valign="top">Automatic airdrop at regular intervals</td></tr></tbody></table>

&#x20;

**Usage**

* Exchange with limited NFT
* Enter event drawings/awards
* Acquire fan rank/certification badges
* Get proposal rights/preferential access

**Features**

* Not for external transmission or redemption
* Linked to GET Pay usage
* Integration with “level system” and “trust score”


---

# 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/5.-token-and-point-design/5.2-role-of-each-asset-and-use-cases.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.