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

# $GEM Token

$GEM is the native token powering every product in the GemHunt ecosystem.

Built using the [**OpenZeppelin**](https://www.openzeppelin.com/) standard, it incorporates modern ERC-20 extensions for efficiency, security, and advanced DeFi compatibility.

### Token Information

**Name** - GemHunt

**Symbol** - GEM

**Total Supply** - 1,000,000,000 (1 Billion)

**Decimals** - 18

**Smartcontract Address -** [0xA8e91D8f5b686a1B5EaA457D2603812Cfdfc56bC](https://bscscan.com/token/0xA8e91D8f5b686a1B5EaA457D2603812Cfdfc56bC)

<figure><img src="/files/aytYI9tSLOlP8IyxRf6m" alt="" width="188"><figcaption><p><a href="https://skynet.certik.com/tools/token-scan/bsc/0xA8e91D8f5b686a1B5EaA457D2603812Cfdfc56b">CertiK Skynet Link</a></p></figcaption></figure>

### Token Allocation

Most projects secretly keep large team allocations. $GEM avoids this entirely  supply is owned by the community from day one.

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

| Allocation          | Percent                    | Description                                               |
| ------------------- | -------------------------- | --------------------------------------------------------- |
| **Presale**         | **80% - 800,000,000 $GEM** | Distributed to the community through the on-chain presale |
| **Liquidity**       | **20% - 200,000,000 $GEM** | Permanently added to ensure trading stability             |
| **Team Allocation** | **0%**                     | No reserved tokens for founders, team, or advisors        |


---

# 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://gemhunt.gitbook.io/doc/whitepaper/usdgem-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.