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

# AKIVERSE Reward (AKIR) Token

AKIVERSE Reward (AKIR) is an ERC-20 standard utility token that serves as the basis for AKIVERSE's various transactions. AKIRs can be obtained in exchange for Teras, the in-world currency.

![](/files/un7qWVVO15hIvnci8j1L)

|       **Token Name**       |                                     AKIVERSE Reward                                     |
| :------------------------: | :-------------------------------------------------------------------------------------: |
|         **Symbol**         |                                           AKIR                                          |
|     **Token Standard**     |                                          ERC-20                                         |
|      **Total Supply**      |                                            ∞                                            |
| **Initial Issue Quantity** |                                        20,000,000                                       |
|        **Contract**        | [PolygonScan](https://polygonscan.com/token/0xf7130028f0766a6fa21d25c2f249da08f51b8ffb) |

AKIRs are available as a commission for Arcade Machine Crafts and Extracts, and Game Players can earn AKIRs for playing the game and also for providing liquidity by farming AKIRs. AKIRs can be earned by Game Players for playing games and also for providing liquidity by farming AKIRs.

AKIR used for Crafting will be Burned.

AKIR will be allocated as follows

<table data-header-hidden><thead><tr><th width="271.3333333333333" align="center"></th><th align="center"></th><th align="center"></th></tr></thead><tbody><tr><td align="center"><strong>Allocation of Initial Issue</strong></td><td align="center">Qty</td><td align="center">%</td></tr><tr><td align="center"><strong>AKV Staking to earn AKIR</strong></td><td align="center">6,000,000</td><td align="center">30.0%</td></tr><tr><td align="center"><strong>Farming</strong></td><td align="center">8,000,000</td><td align="center">40.0%</td></tr><tr><td align="center"><strong>Marketing</strong></td><td align="center">6,000,000</td><td align="center">30.0%</td></tr><tr><td align="center"><strong>Total</strong></td><td align="center">20,000,000</td><td align="center">-</td></tr></tbody></table>

![](/files/wyJx7NwYAzcLwj8h9l9D)

As mentioned above, AKIR is the foundation for AKIVERSE's various transactions, so we are closely simulating its granting rules, logic settings, and adjustments, and will optimize it as appropriate, keeping a close eye on the balance between supply and demand.


---

# 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.akiverse.io/tokenomics/akiverse-reward-akir-token.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.
