> 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/introduction.md).

# Introduction

A universal cross-chain bridge interface for **LayerZero V2 OFT** tokens.

Move any OFT token between EVM networks — including tokens that no bridge interface has ever listed.

{% hint style="info" %}
Live at [galacticbridge.app](https://galacticbridge.app) · Source code on [GitHub](https://github.com/mckellen-eth/galactic-bridge)
{% endhint %}

## The problem it solves

Most bridge interfaces only support tokens their team has added by hand. When a project never gets listed, moving its token between networks becomes manual work: find the OFT contract on a block explorer, decode somebody else's bridge transaction, and assemble the call yourself. Slow, error-prone, and easy to get wrong when a window is closing.

Galactic Bridge does that work for you. Paste a token contract address and it finds the contract, resolves the route, calculates the fee and hands your wallet a ready transaction.

## What makes it different

**It asks contracts, not history.** Most tools can only reproduce routes that somebody has already used. Galactic Bridge queries the contract directly for the networks it is connected to, so a route works even if nobody has ever bridged it before.

**It builds the transaction.** It reuses the call format from a real direct transaction where one exists — many OFTs use custom function selectors, so a learned format is safer than a guess — and assembles it from the LayerZero V2 standard where none does. This matters more than it sounds: popular tokens are usually bridged through routers and aggregators, so past transactions hold the router's call data, not the token's. The fee always comes from a live quote.

**It finds bridge adapters.** Many tokens are not OFTs themselves — they are moved by a separate adapter contract. Galactic Bridge locates that adapter automatically by cross-referencing token transfers with LayerZero events on-chain.

**It explains what it cannot do.** A route that will not work says why: the token runs on LayerZero V1, or the project switched that direction off, or it is moved by a third-party application rather than its own contract. Silence would leave you guessing.

**It is non-custodial.** No account, no registration, no personal data. Your keys and funds never leave your wallet, and every transaction is signed by you.

## Supported networks

Ethereum · BNB Chain · Base · Arbitrum · Optimism · Polygon · Avalanche · Mantle · HyperEVM · Ink · X Layer · Plasma · Robinhood · Arc


---

# 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/introduction.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.