> 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/faq.md). # FAQ ## Does it cost anything to use? The interface is free. You pay the LayerZero messaging fee and network gas, both shown before you sign. Nothing is added on top. ## Does connecting my wallet require a signature? No. Connecting shares your address only. The signatures you make are the bridge transaction itself, and — for some tokens — an approval before it. ## Why does the wallet ask me to sign twice? Because that token is a plain ERC-20 moved by a separate adapter contract. The first transaction approves the adapter to move your tokens; the second is the bridge itself. Tokens that are OFT contracts themselves need only one transaction. You can tell them apart in **02 — BRIDGE DETAILS**: if the OFT contract address differs from the token address, expect two transactions. See [Quick start](/galactic-bridge-docs/quick-start.md). ## Why does it say a direction is disabled? Because the token's own contract has no `peer` configured for that network. Directions are set per contract, and projects switch them off — often after a single test transaction, or when migrating to new contracts. LayerZero Scan may still show an old delivered message for that route, but the contract would reject a new one today. The bridge asks the contract directly rather than trusting history, so you find out before signing instead of losing gas on a rejected transaction. Nothing on your side can change this; only the token's team can re-enable the direction. ## Why does one token work and another does not? Because LayerZero hosts many kinds of application, and only some are OFT tokens. See [Supported tokens](/galactic-bridge-docs/supported-tokens.md) — the five-second check there answers it for any address. ## Is a route safe if nobody has used it before? The route is confirmed by the contracts themselves through `peers()`, which is how LayerZero decides whether to deliver a message. An unused route is not an unverified one. That said, start with a small amount when you are first through a route — sensible practice regardless. ## Why did the search take longer this time? When a token is not an OFT itself, the bridge scans blockchain logs to locate its adapter. That is heavier than a simple lookup. The result is then cached, so searching the same token again returns almost instantly. ## Are my saved tokens sent anywhere? No. They are stored in your browser's local storage. Clearing browser data removes them, and they do not follow you to another device. ## Can I use it on mobile? Yes. The interface adapts to small screens, and WalletConnect lets you connect a mobile wallet by scanning a QR code. ## Can I run it myself? Yes — it is open source and runs locally. See [Run it yourself](/galactic-bridge-docs/run-it-yourself.md). ## What happens if a transfer fails? LayerZero messages that are paid for are delivered; failures are almost always a fee that was too low or a destination contract issue. The **LZScan** link in TX STATUS shows the message state on LayerZero's own explorer, which is the authoritative source. ## How do I report a bug or suggest something? Through the **Feedback** section in the site footer, or by opening an issue on [GitHub](https://github.com/mckellen-eth/galactic-bridge/issues). --- # 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/faq.md?ask=&goal= ``` `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.