# Bridge GoodDollars

Currently, there's no UI for bridging. This guide will teach how you can bridge using blockchain explorers and Metamask:

### Bridging Instructions

{% hint style="info" %}
In blocker explorer, make sure you press`connect to web3` button
{% endhint %}

<figure><img src="https://3326799749-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LfsEjhezedCgGFXCkms%2Fuploads%2FMwwGGZieUwDqiHKZzpmn%2Fimage.png?alt=media&#x26;token=0f204d1d-7d7d-4a5c-9e6f-8cc52defb917" alt=""><figcaption><p>Connect to Web3 Button</p></figcaption></figure>

{% hint style="info" %}
The current maximum amount you can bridge is 300M G$s.\
If you plan to bridge amounts in that order, you must first verify that your request is within limits. See the Verifying bridge limits section.
{% endhint %}

1. **Approve the bridge to spend G$ tokens**
   1. Go to the G$ Contract page on the chain you are bridging from
      * Fuse: <https://explorer.fuse.io/address/0x495d133B938596C9984d462F007B676bDc57eCEC/write-contract#address-tabs>
      * Celo: <https://celoscan.io/address/0x62b8b11039fcfe5ab0c56e502b1c372a3d2a9c7a#writeProxyContract>
      * Ethereum: <https://etherscan.io/address/0x67C5870b4A41D4Ebef24d2456547A03F1f3e094B#writeContract>
      * XDC:\
        <https://xdcscan.com/address/0xEC2136843a983885AebF2feB3931F73A8eBEe50c>
   2. Open the `approve` method box and enter in the `spender` box the bridge address `0xa3247276dbcc76dd7705273f766eb3e8a5ecf4a5` (same on all chains) and in the `value/amount` enter the number of G$ units you want to bridge.\
      **Notice: In Fuse/Ethereum the units are in 2 decimals meaning that if you want to bridge 1.15 tokens this is equal to 115 units. On Celo the units are in 18 decimals, so 1.15 is 1150000000000000000 units.**\
      Press the \`write\` button and approve the transaction in your wallet.
2. **Find out the estimated bridge fee by going to** [https://goodserver.gooddollar.org/bridge/estimatefees<br>](https://goodserver.gooddollar.org/bridge/estimatefees)Record the amount for the service and path you are bridging, for example if you are bridging from Ethereum to Celo using Axelar then use the value under `AXL_ETH_TO_CELO` if using LayerZero then use the value under `LZ_ETH_TO_CELO`\
   **At the moment Axelar service is usually cheaper.**\
   **Bridging from/to Fuse and XDC is only supported by LayerZero.**
3. **Issue bridge request**
   1. Go to the Bridge Contract page on the chain you are bridging from
      * Fuse: <https://explorer.fuse.io/address/0xa3247276DbCC76Dd7705273f766eB3E8a5ecF4a5/write-proxy#address-tabs>
      * Celo: <https://celoscan.io/address/0xa3247276dbcc76dd7705273f766eb3e8a5ecf4a5#writeProxyContract>
      * Ethereum: <https://etherscan.io/address/0xa3247276dbcc76dd7705273f766eb3e8a5ecf4a5#writeProxyContract>
      * XDC: <https://xdcscan.com/address/0xa3247276dbcc76dd7705273f766eb3e8a5ecf4a5#writeProxyContract>
   2. Open/Scroll to the bridgeTo method box and enter in `target` the wallet address of the recipient, in `targetChainId` enter the chain id you are bridging to (1-Ethereum 122-Fuse 42220-Celo 50-XDC), in `amount` enter the same value as used in step #1 (the approve step), in `bridge` enter 0 for Axelar and 1 for LayzerZero. Lastly in `value/payableAmount` enter the estimated bridge fee from step #2.\
      **Make sure you have at least that amount of native tokens in your wallet**\
      press the \`write\` button

{% hint style="info" %}
When bridging from Ethereum, it can take 15 minutes for the transfer to be executed.
{% endhint %}

### Verifying bridge limits

The bridge enforces some transfer limits for security. To make sure your request will go smoothly it is recommended to first check on the **target** chain that your request is within limits.

1. Go to the Bridge Contract page on the chain you are **bridging to**
   * Fuse: <https://explorer.fuse.io/address/0xa3247276DbCC76Dd7705273f766eB3E8a5ecF4a5/read-proxy#address-tabs>
   * Celo: <https://celoscan.io/address/0xa3247276dbcc76dd7705273f766eb3e8a5ecf4a5#readProxyContract>
   * Ethereum: <https://etherscan.io/address/0xa3247276dbcc76dd7705273f766eb3e8a5ecf4a5#readProxyContract>
   * XDC <https://xdcscan.com/address/0xa3247276dbcc76dd7705273f766eb3e8a5ecf4a5#readProxyContract>
2. Open/Scroll to the `canBridge` method and enter in `from` the wallet address where you are bridging from and in `amount` enter the amount of **units in 18 decimals** that you want to bridge then press the `Query` button.

### Troubleshooting

* You can see the status of your bridge request by copying the bridge request transaction hash from step #3 and pasting it in Axelar or Layerzero scanners according to the service you used.\
  Axelar Scanner: <https://axelarscan.io/>\
  Layzerzero Scanner: <https://layerzeroscan.com/>
* If the transaction did not reach the final step on Axelar or Layerzero consult with their documentation or support channels.\
  <https://docs.axelar.dev/dev/general-message-passing/recovery>
* In case the transaction has been executed by Axelar or Layzezero but still failed to transfer the G$s then contact us via our support form here:

{% embed url="<https://gooddollar.typeform.com/to/J47K2R26>" %}

### Fuse Bridge

Fuse runs a bridge that enables bridging between Ethereum and Fuse. It has an easy-to-use UI here: <https://app.voltage.finance/#/bridge>


---

# Agent Instructions: 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:

```
GET https://docs.gooddollar.org/user-guides/bridge-gooddollars.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.