> For the complete documentation index, see [llms.txt](https://docs.wemix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wemix.com/en/tutorial/erc-20-token/check-erc-20-token.md).

# Check ERC-20 Token

You can add and verify the custom token in MetaMask for ERC-20 tokens distributed using Remix.

ERC-20 contracts must be deployed in advance. Please refer to [Write ERC-20 Contract ](/en/tutorial/erc-20-token/write-erc-20-contract.md)for ERC-20 Contract deployment.&#x20;

We will proceed with the process of checking the ERC-20 token in the order below\..

* Step 1 :  Access MetaMask
* Step 2 : Check Token Contract Address
* Step 3 : Add Custom Token
* Step 4 : Confirm Custom Token

{% hint style="info" %}
All examples are based on WEMIX3.0 Testnet.
{% endhint %}

## Step 1 : Access MetaMask

You must run the MetaMask Extensions that are installed. If you do not have MetaMask Extensions installed, you must go to the [Chrome Web Store](https://chrome.google.com/webstore/category/extensions) to download and run MetaMask.

<figure><img src="/files/NMhU2tXE7SSbrut696Ns" alt=""><figcaption><p>Install MetaMask Extension</p></figcaption></figure>

Once MetaMask is running, you can now change the network from Ethereum to WEMIX3.0 Testnet as shown in the picture below.

<figure><img src="/files/D26F5hpNzm72HRqxU5Pv" alt=""><figcaption><p>Connect WEMIX_Testnet</p></figcaption></figure>

## Step 2 : Check Token Contract Address

A token contract address is required to add as a Custom Token. \
The ERC-20 Contract Address deployed through Remix can be found in [Testnet Explorer](https://explorer.test.wemix.com/).

After accessing [Testnet Explorer](https://explorer.test.wemix.com/), you can check tokens by selecting 'Token > Tokens List'.

<figure><img src="/files/sugSJ0lBoPRKOUrjbeRL" alt=""><figcaption><p>Token > Token List</p></figcaption></figure>

Find the name of the token entered when creating the ERC-20 contract, check the Contract Address, and copy it.

## Step 3 : Add Custom Token

Return to the MetaMask and select 'Import tokens' and enter 'Token contract address'. \
When entering 'Token contract address', Token symbol and Token decision are automatically entered.

<figure><img src="/files/wmrbJIm0lvOH7TSGpRet" alt=""><figcaption><p>After selecting 'Import tokens', Enter Token Contract Address and Add</p></figcaption></figure>

If you select 'Add custom token' in the picture above, a screen will be displayed to confirm whether you want to add the token finally. Select 'Import tokens' to complete token registration.

## Step 4 : Confirm Custom Token

Once the token registration is complete, you can check the ERC-20 Token deployed at the bottom of TWEMIX as shown below.&#x20;

Below is an additional example of Token with Token Name 'WT Token'.

<figure><img src="/files/8ynHpNrO4jwikTTmeXgZ" alt=""><figcaption><p>Confirm Custom Token</p></figcaption></figure>


---

# 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.wemix.com/en/tutorial/erc-20-token/check-erc-20-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.
