> For the complete documentation index, see [llms.txt](https://qiedex.qie.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qiedex.qie.digital/how-to-bridge-stablecoins.md).

# How to Bridge Stablecoins

### Overview

This guide walks you through the process of bridging **USDC** and **USDT** stablecoins between the **Ethereum** network and the **QIE Mainnet** using our custom-built cross-chain bridge. Since QIE doesn't natively support stablecoins, we've enabled support through a **wrapped token mechanism**, maintaining a **1:1 peg** between the original and wrapped assets.

#### ✅ Supported Stablecoins

| Ethereum Token | QIE Representation |
| -------------- | ------------------ |
| USDC           | `wUSDC.eth`        |
| USDT           | `wUSDT.eth`        |

***

### 🔁 Bridge Flow Overview

Our bridge operates by **locking** tokens on Ethereum and **minting wrapped equivalents** on QIE. On return, the wrapped tokens are **burned on QIE**, and the originals are **released** back on Ethereum.

***

### 🔹 Bridging from Ethereum → QIE

#### Steps:

1. **Select Networks**
   * **From:** Ethereum
   * **To:** QIE Mainnet
2. **Choose Asset**
   * Select either **USDC** or **USDT** from the asset list.
3. **Initiate Transfer**
   * When the transfer is started:
     * Your **original tokens are locked** on the Ethereum network.
     * Simultaneously, an **equal amount of wrapped tokens** are **minted** on QIE:
       * `wUSDC.eth` for USDC
       * `wUSDT.eth` for USDT
4. **Receive on QIE Mainnet**
   * The wrapped tokens will be available in your wallet on QIE shortly after confirmation.

***

### 🔸 Bridging from QIE → Ethereum

#### Steps:

1. **Select Networks**
   * **From:** QIE Mainnet
   * **To:** Ethereum
2. **Choose Asset**
   * Select either `wUSDC.eth` or `wUSDT.eth` depending on your holdings.
3. **Initiate Transfer**
   * When the transfer is started:
     * The **wrapped tokens are burned** on the QIE network.
     * The **original Ethereum-based tokens are unlocked** and returned to your Ethereum wallet.

***

### 🧾 Token Contract Addresses on QIE

| Token        | Symbol      | QIE Contract Address                         |
| ------------ | ----------- | -------------------------------------------- |
| Wrapped USDC | `wUSDC.eth` | `0x0e93FAcc0a2cfD418403f3AD3EEfB5C8b2dfAec7` |
| Wrapped USDT | `wUSDT.eth` | `0xCB7bBC584475dce754a918ccD92FF6E0211f3CEE` |

***

### 🔒 Security & Peg

* All bridged assets are **pegged 1:1** with their original Ethereum counterparts.
* The bridge ensures:
  * **Locking mechanism on Ethereum**
  * **Minting and burning logic on QIE**
  * **Secure release mechanism back on Ethereum**

***

### ⚠️ Notes

* Only **USDC and USDT** are currently supported.
* Wrapped tokens on QIE are **non-native** and should only be handled via the bridge.
* Ensure that you always use the **official bridge interface -**[**https://bridge.qie.digital/**](https://bridge.qie.digital/stable-bridge) to avoid loss of funds.

***

### ✅ Example Use Case

Imagine you want to use USDC on a dApp that runs on the QIE network. Simply bridge your USDC from Ethereum, and you'll receive `wUSDC.eth` on QIE — usable just like native tokens. When you're done, bridge them back, and your original USDC will be unlocked on Ethereum.


---

# 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://qiedex.qie.digital/how-to-bridge-stablecoins.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.