> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/learn/about-bridging/using-stargate.md).

# Using Stargate

Transfer tokens across 80+ chains to and from Chiliz Chain using Stargate's Simple and Advanced modes, powered by the LayerZero OFT standard.

[Stargate](https://stargate.finance/) is an asset bridge built on top of the [LayerZero protocol](https://layerzero.network/), enabling seamless asset transfers between 80+ blockchains, without wrapping tokens, all thanks to the [OFT standard](https://docs.layerzero.network/v2/concepts/applications/oft-standard).

{% hint style="info" %}
Stargate provide [their own tutorial for token transfers](https://docs.stargate.finance/user-docs/transfer).
{% endhint %}

Stargate has two modes, depending on how granular you want to go on some parameters.

## Simple Mode

The Simple Mode is pretty straightforward:

1. Click the "From" field and select one of the tokens found in the wallet that you connected to Stargate.
   * You can also explore the various chains and tokens supported by the bridge, using the search field.
2. Now that it knows the source chain and token, Stargate can suggest target chains and tokens that are compatible.

<figure><img src="https://3400301555-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4L7rBH2rmyoBTn93MSdx%2Fuploads%2Fjd68XIhu5LbCewHptBuC%2Fimage.png?alt=media&amp;token=9320761d-6f80-45d5-97f1-2fa6b184e6be" alt="" width="375"><figcaption></figcaption></figure>

3. Select the target token and chain, then enter how much source token you want to bridge.

<figure><img src="https://3400301555-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4L7rBH2rmyoBTn93MSdx%2Fuploads%2FjWEnuM6SZEPyuDmVJY2Z%2Fimage.png?alt=media&amp;token=6f44f674-ea48-4060-8c04-3e3fe61c4227" alt="" width="375"><figcaption></figcaption></figure>

4. Click "Transfer" to trigger the confirmation dialog from your Web3 wallet.
5. Once confirmed, Stargate takes care of the bridging itself.

## Advanced Mode

While the Advanced Mode presents a wider interface, it is not much more complex than the simple, it simply offers a better overview of what's possible.

<figure><img src="https://3400301555-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4L7rBH2rmyoBTn93MSdx%2Fuploads%2FaucgRdVXWjn7IMecDeFz%2Fimage.png?alt=media&amp;token=79b1ac67-9b4a-43d1-a2c2-5f7486ab3451" alt=""><figcaption></figcaption></figure>

The most notable customizations are:

* "Gas on destination": Use this option if you need native tokens on the destination chain, to facilitate other transactions, such as local swaps.
* "Fee tolerance": You can choose a maximum fee tolerance (in percentage of the transfered tokens). If the amount you're receiving on the target chain is outside of this tolerance, the transaction is reverted.

<figure><img src="https://3400301555-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4L7rBH2rmyoBTn93MSdx%2Fuploads%2F9tNyCJb7CbUDj1KM9nk0%2Fimage.png?alt=media&amp;token=8d4143a1-2c1b-416f-9ff5-e26b751d00d4" alt="" width="375"><figcaption></figcaption></figure>

Otherwise, the way it works remains the same as in the Simple Mode.


---

# 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.chiliz.com/learn/about-bridging/using-stargate.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.
