# Ticket NFT

**Ticket NFT** allows the holders(as **Passengers** in AWANA) to win rewards by Proof of Daily Commute, which means converting the value of attention around the daily commuting scenario into their own Attention Asset based on the POW mechanism.

Part of the rewards goes to an reward pool shared by all **Bus NFT** holders to incentive their daily operations.

<figure><img src="/files/uRMSG8h1qdVkUPHfWiPq" alt="" width="375"><figcaption><p>Sample of Ticket NFT </p></figcaption></figure>

## **Ticket Attributes**

* Efficiency: Higher Efficiency value will result in better ART earnings.
* Luck: Higher Luck value will result in better frequency and quality of a Magic Box drop.

## **Ticket Quality**

There are five qualities of ticket NFTs. When a ticket NFT is minted, the value of each attribute will be chosen at random within the min. and max. values according to the quality of the ticket NFT.

\
Users can level up the ticket NFTs by burning ART and get additional points that can be added to different attributes as needed.

<table data-header-hidden><thead><tr><th width="178" align="center"></th><th width="178" align="center"></th><th width="178" align="center"></th><th align="center"></th></tr></thead><tbody><tr><td align="center"><strong>Quality</strong></td><td align="center"><strong>Min.Attribute</strong></td><td align="center"><strong>Max.Attribute</strong></td><td align="center"><strong>Points added for each level up</strong></td></tr><tr><td align="center">N</td><td align="center">1</td><td align="center">8</td><td align="center">4</td></tr><tr><td align="center">R</td><td align="center">8</td><td align="center">16</td><td align="center">6</td></tr><tr><td align="center">SR</td><td align="center">16</td><td align="center">32</td><td align="center">8</td></tr><tr><td align="center">SSR</td><td align="center">32</td><td align="center">60</td><td align="center">10</td></tr><tr><td align="center">UR</td><td align="center">60</td><td align="center">100</td><td align="center">12</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://whitepaper.awana.world/attention-assets/tickets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
