> For the complete documentation index, see [llms.txt](https://docs.ethgas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ethgas.com/foundation/gwei-bridge-instructions.md).
# $GWEI Bridge Instructions
{% hint style="info" %}
These instructions cover manual (contract-level) token bridging via Wormhole. While this provides zero bridge fee, full control, and transparency, it requires multiple steps and careful input handling.
Most users may prefer UI-based bridge providers such as [https://portalbridge.com](https://portalbridge.com/), inputting the $GWEI contract address directly, automating this process, and offering a simpler, safer experience, but charging a fee for their service.
{% endhint %}
### $GWEI Token Addresses
* Ethereum Mainnet: [`0x2798b1cC5A993085E8A9D46e80499F1B63f42204`](https://etherscan.io/address/0x2798b1cC5A993085E8A9D46e80499F1B63f42204)
* BSC: [`0x30117E4bC17d7B044194b76A38365C53b72F7D49`](https://bscscan.com/address/0x30117E4bC17d7B044194b76A38365C53b72F7D49)
### $GWEI Bridge Instructions
Bridging from BSC -> Ethereum
1. On BSC chain, approve GWEI token for wormhole tokebridge: [`0xb6f6d86a8f9879a9c87f643768d9efc38c1da6e7`](https://bscscan.com/address/0xb6f6d86a8f9879a9c87f643768d9efc38c1da6e7)
2. Call wormhole tokebridge [`0xb6f6d86a8f9879a9c87f643768d9efc38c1da6e7`](https://bscscan.com/address/0xb6f6d86a8f9879a9c87f643768d9efc38c1da6e7) `transferTokens()` according to[ https://wormhole.com/docs/products/token-transfers/wrapped-token-transfers/guides/wtt-contracts/#transfer-tokens](https://wormhole.com/docs/products/token-transfers/wrapped-token-transfers/guides/wtt-contracts/#transfer-tokens)
1. token is the GWEI address [`0x30117E4bC17d7B044194b76A38365C53b72F7D49`](https://bscscan.com/address/0x30117E4bC17d7B044194b76A38365C53b72F7D49)
2. recipientChain ID for ETH is 2 according to[ https://wormhole.com/docs/products/reference/chain-ids](https://wormhole.com/docs/products/reference/chain-ids/)
3. recipient must be in bytes32 format, for example if your address is `0xf1357d45671CB16dE055752809C8d2e3aB4AfE2e` then you should input `0x000000000000000000000000f1357d45671cb16de055752809c8d2e3ab4afe2e`
4. arbiterFee can be set to `0`
5. nonce can start with `0`
6. Example tx:
3. Search your tx hash on[ https://wormholescan.io](https://wormholescan.io/) and wait for around 1-2 min
4. On the Ethereum chain, call wormhole tokenbridge [`0x3ee18b2214aff97000d974cf647e7c347e8fa585`](https://etherscan.io/address/0x3ee18b2214aff97000d974cf647e7c347e8fa585) `completeTransfer` with input data from the below:
1. Get the VAA bytes from[ https://wormhole.com/docs/products/token-transfers/wrapped-token-transfers/guides/fetch-signed-vaa](https://wormhole.com/docs/products/token-transfers/wrapped-token-transfers/guides/fetch-signed-vaa/), remember to put 0x before the hex data
1. Or, open the terminal and run `echo "" | base64 --decode | xxd -p -c 9999` where `""` refers to the vaa data found in the advanced tab of the wormhole explorer page
2. Example tx:
Bridging from Ethereum -> BSC
1. On the Ethereum chain, approve GWEI token for wormhole tokebridge [`0x3ee18b2214aff97000d974cf647e7c347e8fa585`](https://etherscan.io/address/0x3ee18b2214aff97000d974cf647e7c347e8fa585)
2. Call wormhole tokebridge [`0x3ee18b2214aff97000d974cf647e7c347e8fa585`](https://etherscan.io/address/0x3ee18b2214aff97000d974cf647e7c347e8fa585) `transferTokens()` according to[ https://wormhole.com/docs/products/token-transfers/wrapped-token-transfers/guides/wtt-contracts/#transfer-tokens](https://wormhole.com/docs/products/token-transfers/wrapped-token-transfers/guides/wtt-contracts/#transfer-tokens)
1. token is the GWEI address [`0x2798b1cC5A993085E8A9D46e80499F1B63f42204`](https://etherscan.io/address/0x2798b1cC5A993085E8A9D46e80499F1B63f42204)
2. recipientChain ID for BSC is `4` according to[ https://wormhole.com/docs/products/reference/chain-ids/](https://wormhole.com/docs/products/reference/chain-ids/)
3. recipient must be in bytes32 format, for example if your address is `0xf1357d45671CB16dE055752809C8d2e3aB4AfE2e` then you should input `0x000000000000000000000000f1357d45671cb16de055752809c8d2e3ab4afe2e`
4. arbiterFee can be set to `0`
5. nonce can start with `0`
6. Example tx:
3. Search your tx hash on[ https://wormholescan.io](https://wormholescan.io/) and wait for around 18-20 min
4. On BSC chain, call wormhole tokenbridge [`0xb6f6d86a8f9879a9c87f643768d9efc38c1da6e7`](https://bscscan.com/address/0xb6f6d86a8f9879a9c87f643768d9efc38c1da6e7) `completeTransfer` with input data from the below
1. Get the VAA bytes from[ https://wormhole.com/docs/products/token-transfers/wrapped-token-transfers/guides/fetch-signed-vaa](https://wormhole.com/docs/products/token-transfers/wrapped-token-transfers/guides/fetch-signed-vaa/), remember to put 0x before the hex data
1. Or, open the terminal and run `echo "" | base64 --decode | xxd -p -c 9999` where `""` refers to the vaa data found in the advanced tab of the wormhole explorer page
2. Example tx:
---
# 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.ethgas.com/foundation/gwei-bridge-instructions.md?ask=&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.