> For the complete documentation index, see [llms.txt](https://docs.shadeprotocol.io/shade-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shadeprotocol.io/shade-protocol/advanced-topics-apps/bridge.md).

# Bridge

Shade Bridge

**The** [**Shade Bridge**](https://app.shadeprotocol.io/bridge) **is an interface that allows you to seamlessly bridge assets between different blockchains using the power of IBC.**

The following are a list of key features of the Shade Bridge:

* Generalized IBC token transfers (Osmo —> ATOM etc.)
* Transfer assets into Shade DeFi ecosystem
* Convert your public IBC assets into privacy-preserving equivalents
* Bridge private tokens like SHD & SILK to the broader Cosmos

In order to use the [**Shade Bridge**](https://app.shadeprotocol.io/bridge) you will need the following:

* Keplr installed
* Tokens for gas / transfer
* \~1-2 minutes

{% embed url="<https://www.youtube.com/watch?v=X6suAVGDXfY>" %}

{% embed url="<https://www.youtube.com/watch?t=&v=Rc5kp-9_xqg>" %}

{% embed url="<https://shadeprotocol.io/shade-guide/how-to-bridge-to-secret-network>" %}

The list of supported chains on the Shade Bridge is always growing as more IBC channels & relayers are setup in the Cosmos Ecosystem.&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.shadeprotocol.io/shade-protocol/advanced-topics-apps/bridge.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.