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

# Rare routes

Some routes exist on-chain but have never been used, or were used so long ago that the data is out of reach. When automatic discovery comes up empty, you can supply the missing piece yourself.

## When it appears

A red **BRIDGE ROUTE NOT FOUND** panel offers two buttons: **ENTER MANUALLY** and **RETRY**.

Try **RETRY** first. Public RPC nodes fail intermittently, and a second attempt often succeeds on its own.

## Entering details by hand

**ENTER MANUALLY** accepts either of two things:

**The OFT contract on the destination network.** With that address the bridge searches from the destination side and reconstructs everything else. Find it on LayerZero Scan: open any message for this token and copy the receiver address.

**A transaction hash of any bridge for this token.** One LayerZero Scan lookup then yields the sender, the source transaction and the destination contract at once.

## When manual entry will not help

If the message says the token uses **LayerZero V1**, or that the contract is a LayerZero application but **not a standard OFT**, no address will help. Those are different protocols and interfaces — see [Supported tokens](/galactic-bridge-docs/supported-tokens.md).

{% hint style="info" %}
A route that had no history still works. Once `peers()` confirms the contracts are paired, the bridge builds the transaction from the standard interface — being first to use a route is not a problem.
{% endhint %}


---

# 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/rare-routes.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.