> For the complete documentation index, see [llms.txt](https://docs.hemi.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hemi.xyz/how-to-tutorials/using-hemi/pop-mining/setup-part-1/add-themi-to-metamask.md).

# (Testnet) Add tHEMI to MetaMask

{% hint style="info" %}
📜 **TL;DR:**

* **tHEMI** is the governance token for the Hemi Network's testnet phase.
* tHEMI tokens are used for **payouts to PoP miners** as a means of acknowledging their contribution to the network's security and functionality. In the future, these incentives will expand to individuals running Sequencers, Publishers, and Challengers.
* View your tHEMI balance and transactions directly in MetaMask.
* The tHEMI token contract address is `0x4200000000000000000000000000000000000042.`
  {% endhint %}

***

## 🌐Overview

tHEMI is the testnet governance token for the Hemi Network. Initially, tHEMI tokens are used for payouts to PoP miners to acknowledge their contribution to the network's security and functionality.

Looking ahead, **tHEMI will play a broader role in rewarding other network participants**, including Sequencers, Publishers, and Challengers, who contribute to the network's resilience and growth. tHEMI is set to become the preferred gas token on the network, offering fee discounts and enhancing user transaction efficiency.

***

## 📚 Tutorial

## Video

{% embed url="<https://vimeo.com/1030116566?share=copy>" %}

### 1. Open MetaMask

![](https://3063395300-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBrGAUP9hcnvqWQvHZlN0%2Fuploads%2F209RTQMxJiGG1F5CNcNb%2F1.png?alt=media\&token=23686255-3dc2-4b93-8adb-41c04d91f8df)

***

### 2. Access Token Selection

* Navigate to `Tokens`
* `Import Tokens`

<img src="https://3063395300-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBrGAUP9hcnvqWQvHZlN0%2Fuploads%2Fruz1ZATbwDHGGa8hBn8B%2F2.png?alt=media&amp;token=7da147da-6a61-475c-b774-6fd9dad216d3" alt="" width="357">

***

### 3. **Enter the Contract Address**

* Type in the tHEMI token contract address `0x4200000000000000000000000000000000000042` into the `Token Contract Address` field.

<figure><img src="https://3063395300-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBrGAUP9hcnvqWQvHZlN0%2Fuploads%2FQGUsSaehW7ciucIrTyRV%2F3.png?alt=media&amp;token=ef623c2c-aa24-4304-9ab0-ddb4a8d4f1a6" alt="" width="352"><figcaption></figcaption></figure>

* If the address is recognized, MetaMask will automatically populate the `Token Symbol` and `Decimals of Precision` fields.

***

### 4. Import

* Confirm the accuracy of the provided information, click on `Add Custom Token`, and then select `Import Tokens`.

Your tHEMI tokens should now be visible in your MetaMask wallet. You can view your balance and conduct transactions directly within the wallet interface.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hemi.xyz/how-to-tutorials/using-hemi/pop-mining/setup-part-1/add-themi-to-metamask.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
