> For the complete documentation index, see [llms.txt](https://galactic-bridge.gitbook.io/galactic-bridge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://galactic-bridge.gitbook.io/galactic-bridge-docs/supported-tokens.md).

# Supported tokens

LayerZero Scan lists **every** application built on LayerZero, and most of them are not token transfers at all. Knowing the difference saves a lot of guessing.

## What works

| Type                           | Supported | Notes                                                                                  |
| ------------------------------ | --------- | -------------------------------------------------------------------------------------- |
| LayerZero V2 OFT               | ✅         | The standard this bridge is built for.                                                 |
| V2 OFT bridged through routers | ✅         | The call is built from the standard interface instead of copied.                       |
| V2 OFT with a separate adapter | ✅         | The adapter is found automatically, provided the network's RPC serves historical logs. |

## What does not

| Type                                  | Why                                                                                                                                                                                                        |
| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **LayerZero V1**                      | A different protocol: another endpoint contract, another function, another set of network IDs. The bridge detects these and says so explicitly.                                                            |
| **Custom V2 applications**            | Contracts that send LayerZero messages but are not OFTs. They have peers configured, yet no `token()` and no `quoteSend()` — each one has its own bespoke interface that cannot be reproduced generically. |
| **Tokens moved by a third-party app** | Some launchpads bridge every token they issue through one shared contract with its own interface, so the token has no OFT of its own. The bridge names the application responsible.                        |
| **Stargate pools**                    | Stablecoins such as USDC move through Stargate's own pool architecture rather than the OFT standard. Use Stargate's interface for those.                                                                   |

## Check any token in five seconds

Before troubleshooting, confirm the token is an OFT at all:

```
https://scan.layerzero-api.com/v1/messages/oapp/<EID>/<TOKEN_ADDRESS>?limit=1
```

A list of messages means **yes, it is an OFT**. A response of `{"code":4040}` means the address is not a LayerZero application on that chain — it either needs an adapter, or it is not an OFT.

### Network IDs (EID)

| Network   | EID   | Network   | EID   |
| --------- | ----- | --------- | ----- |
| Ethereum  | 30101 | Base      | 30184 |
| BNB Chain | 30102 | X Layer   | 30274 |
| Avalanche | 30106 | Ink       | 30339 |
| Polygon   | 30109 | HyperEVM  | 30367 |
| Arbitrum  | 30110 | Plasma    | 30383 |
| Optimism  | 30111 | Robinhood | 30416 |
| Mantle    | 30181 | Arc       | 30417 |

{% hint style="info" %}
Use the EID of the chain the address belongs to. The same token can be a plain OFT on one network and use an adapter on another.
{% endhint %}

## A note on Arc

Arc is Circle's Layer 1, where gas is paid in USDC. Bridging **to** Arc works normally — the fee is paid on the source network. Bridging **from** Arc needs USDC for gas, which on mainnet is currently distributed through Circle directly rather than bought on an exchange.


---

# 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://galactic-bridge.gitbook.io/galactic-bridge-docs/supported-tokens.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.