> For the complete documentation index, see [llms.txt](https://navofamily.gitbook.io/navo-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navofamily.gitbook.io/navo-docs/help/testnet-usdc.md).

# Get testnet USDC

Get testnet USDC to trade USDC-paired launches on Elysium Testnet.

Some Navo launches use **USDC** as the pair token instead of HYPE. You pay and receive USDC when you trade them. On Elysium Testnet this is testnet USDC. Testnet USDC has no monetary value.

Circle does not issue USDC directly on Elysium Testnet. You get USDC on HyperEVM Testnet first, then bridge it to Elysium Testnet. The bridge locks your USDC on HyperEVM Testnet and gives you the same amount on Elysium Testnet.

{% hint style="info" %}
You also need testnet HYPE for gas on both networks: on HyperEVM Testnet to bridge, and on Elysium Testnet to trade. See [Get testnet HYPE](/navo-docs/help/testnet-hype.md).
{% endhint %}

## Step 1: get USDC on HyperEVM Testnet

1. Open Circle's official faucet: [faucet.circle.com](https://faucet.circle.com).
2. Select **USDC** and the network **HyperEVM Testnet**.
3. Enter the address of the wallet that you use on Navo.
4. Send the request.

The faucet page shows how much it sends and when you can ask again.

## Step 2: bridge USDC to Elysium Testnet

1. Open the official Elysium bridge: [testnet.elysium.kinetiq.xyz/bridge](https://testnet.elysium.kinetiq.xyz/bridge).
2. Click **Connect** and connect the same wallet.
3. Select **USDC** and enter the amount to bridge from HyperEVM Testnet to Elysium Testnet.
4. Approve USDC when your wallet asks, then confirm the bridge transaction.

The USDC arrives in the same wallet on Elysium Testnet after the bridge processes the deposit.

## Add USDC to your wallet

If your wallet does not show your USDC balance, add the token by hand with these values.

| Network          | USDC address                                 | Decimals |
| ---------------- | -------------------------------------------- | -------- |
| HyperEVM Testnet | `0x2B3370eE501B4a559b57D449569354196457D8Ab` | 6        |
| Elysium Testnet  | `0x7D29d8047B905000459c0E80c34a26CeedcB47b2` | 6        |

Navo accepts only the Elysium Testnet address above. A token with the name USDC at a different address is not the bridged USDC.

Sources: [USDC contract addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses) in the Circle docs, and [Token bridging on Elysium](https://testnet.elysium.kinetiq.xyz/docs/token-bridging-on-elysium) in the Elysium docs.

{% hint style="warning" %}
A faucet never needs your seed phrase or private key, and it never asks you to send funds first. Use only the links on this page, in the Circle docs or in the Elysium docs.
{% endhint %}


---

# 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://navofamily.gitbook.io/navo-docs/help/testnet-usdc.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.