> For the complete documentation index, see [llms.txt](https://dyorhq.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dyorhq.gitbook.io/docs/wallet-and-account/bridge.md).

# Bridge

DyorHQ's bridge is powered by **Aurora Intents** (NEAR Intents). You send on one chain, Aurora settles across chains, and the funds arrive in your DyorHQ wallet on Monad, or the other way round.

**Where:** Home → **Bridge**.

<figure><img src="https://2315413579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn3ZLa5CyOGEcKzuTuITR%2Fuploads%2Fgit-blob-f5261bcfc97296a86286eac708d4a17bb3db275e%2Fdevice-mockup_1.5x_postspark_2026-09-28_09-37-01.png?alt=media" alt=""><figcaption></figcaption></figure>

## Supported chains

One side is always **Monad**. The other can be: Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche, Gnosis, Scroll or Berachain. The default is **Base → Monad**; a flip button reverses direction.

Tokens come from Aurora's list for each chain, with stablecoins (USDC, USDT0, USDT) first. The **Bridge from** picker lists every asset you hold across the supported chains, largest value first, with balances read from public RPCs.

## How to bridge

1. Pick the source chain and token. Enter an amount (25% / 50% / 75% / **Max**).
2. Read the summary: **You receive**, **Minimum received**, **Total fee** (one dollar figure and percentage covering Aurora's protocol fee, withdrawal fee, spread and any DyorHQ integrator fee), **Slippage** (default 1%, adjustable), **Estimated time**, **Route**.
3. Tap **Bridge to Monad** (or **Bridge to \<Chain>**). There's no separate confirmation sheet: the summary above the button is the review. With Require Face ID on, confirm with Face ID.
4. The app sends exactly the quoted amount to Aurora's deposit address on the source chain, notifies Aurora, and tracks the status for up to about ten minutes.

## Status messages

*Sending on \<Chain>…* → *Notifying the bridge…* → *Confirming your deposit…* → *Waiting for the full deposit…* → *Bridging across chains…* → **Arrived** (or **Refunded** / **Failed**).

When it lands: "Arrived on Monad · Received X", with a **View** link that upgrades from the deposit transaction to the destination transaction. If it's slow you'll see *"Still settling, this can take a minute. Check your balance on \<Chain>; DyorHQ keeps checking while it's open."* and later *"Taking longer than usual. Check your balance on \<Chain>; DyorHQ checks again each time you open it."* The bridge itself completes on its own. DyorHQ tracks its status while the app is open (and again when you reopen it), and it shows in your balance and Activity once it lands. A refund returns funds on the source chain and tells you why.

Completed bridges appear in Portfolio under **Bridge** and post a "Bridge complete" notification.

## Fees

Aurora's quote includes its protocol fee, withdrawal fee and spread, plus DyorHQ's 0.1% integrator fee. Everything is shown in the **Total fee** row before you confirm.


---

# 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://dyorhq.gitbook.io/docs/wallet-and-account/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.
