> For the complete documentation index, see [llms.txt](https://docs.energyweb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.energyweb.org/ewx-ecosystem/bridging-usdewt/bridging-usdewt-using-the-energy-web-x-bridging-web-app.md).

# Bridging $EWT using the Energy Web X Bridging Web App

#### 🎬 Video Walkthrough

**Flow 1: Bridging from EWX to Ethereum**

1. Open the **EWX App** and navigate to the **Bridge** tab.
2. Select **EWX** as the **From** network and **Ethereum (ETH)** as the **To** network.
3. **Connect your EWX wallet** (SubWallet, Nova Wallet, or Polkadot.js).
4. **Enter the amount of $EWT** you wish to bridge.
5. In the **Destination Wallet Address** field, **enter an EVM address on Ethereum Mainnet** — this is where the bridged tokens will be received.
6. **Review and confirm** the transaction details.
7. **Sign the transaction** with your connected wallet.
8. Once executed, **view the bridge status** in the **Transactions** tab.

{% embed url="<https://www.youtube.com/watch?v=nbjAqPYAFik>" %}

***

**Flow 2: Bridging from Ethereum to EWX**

1. Open the **EWX App** and navigate to the **Bridge** tab.
2. Select **Ethereum (ETH)** as the **From** network and **EWX** as the **To** network.
3. **Connect your EVM wallet** (e.g. MetaMask).
4. **Enter the amount of $EWT** you wish to bridge.
5. In the **Destination Wallet Address** field, **enter your Substrate address** on EWX, this is where the bridged tokens will be received.
6. **Review and confirm** the transaction details.
7. **Sign the transaction** with your connected wallet.
8. Once executed, **track the bridge status** in the **Transactions** tab.

{% embed url="<https://www.youtube.com/watch?v=AfTv302VoEk>" %}

***

**Flow 3: Bridging from EWC to EWX**

1. Open the **EWX App** and navigate to the **Bridge** tab.
2. In the dropdown menus, select **EWC** as the **From** network and **EWX** as the **To** network.
3. **Connect your EWC wallet** (for example, MetaMask).
4. **Enter the amount of $EWT** you wish to bridge.
5. In the **Destination Wallet Address** field, **enter your Substrate address** on EWX — this is where the bridged tokens will be received.
6. Click **Bridge EWT** to proceed.
7. **Review the transaction details** carefully, then **confirm** the action.
8. **Sign the transaction** with your connected wallet when prompted.
9. Once submitted, **track the status** of your bridge transfer in the **Transactions** tab.

{% embed url="<https://www.youtube.com/watch?v=dqJJ0Ene3PM>" %}

***


---

# 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.energyweb.org/ewx-ecosystem/bridging-usdewt/bridging-usdewt-using-the-energy-web-x-bridging-web-app.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.