> For the complete documentation index, see [llms.txt](https://docs.migaloo.zone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.migaloo.zone/learn/tutorials/bridge-assets.md).

# Bridge Assets

{% hint style="danger" %}
When bridging IBC assets must ALWAYS route through their home chain. For example bridging WHALE from Osmosis to Terra would Require first IBCing WHALE to Migaloo first, then IBC to Terra. Bridges such as TFM and IBC FUN *should* automatically route correctly for you, but manual IBC sends using wallets will need routing manually.
{% endhint %}

### Station Wallet:

{% embed url="<https://docs.station.money/using/send>" %}

### LEAP Wallet

{% embed url="<https://leapwallet.notion.site/Make-IBC-transfer-6a4dcb76ad8a4d1baee6a969fbfc64fb>" %}

### Keplr Wallet:

{% embed url="<https://help.keplr.app/articles/ibc-transfers>" %}

### TFM:

{% embed url="<https://docs.tfm.com/quick-start#ibc-transfer>" %}

### IBC FUN

{% embed url="<https://api-docs.skip.money/docs/getting-started>" %}

## IBC Channels

| Network   | Channel   |
| --------- | --------- |
| Terra 2   | 0 <> 86   |
| Juno      | 1 <> 210  |
| Injective | 3 <> 102  |
| Secret    | 4 <> 57   |
| Osmosis   | 5 <> 642  |
| Comdex    | 12 <> 63  |
| Chihuahua | 10 <> 39  |
| Kujira    | 8 <> 58   |
| Carbon    | 14 <> 24  |
| Neutron   | 27 <> 57  |
| Umee      | 22 <> 57  |
| Kava      | 54 <> 126 |
| Axelar    | 53 <> 121 |
| Lunc      | 59 <> 84  |
| Sei       | 57 <> 14  |
| Noble     | 60 <> 14  |

{% hint style="warning" %}
First number is the source and second is destination. Example: Migaloo 0 <-> 86 Terra. On Migaloo, you go from channel 0. Source is always Migaloo first
{% 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://docs.migaloo.zone/learn/tutorials/bridge-assets.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.