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

# Bridge

Move assets across chains — including between EVM and Solana — with the receive address always visible before you approve.

{% hint style="info" %}
Bridging is powered by **Relay**, a third-party cross-chain provider. Novamp shows you exactly where funds will land and the estimated time before you sign. You keep custody throughout.
{% endhint %}

## Overview

Bridge moves value between `🟢 Robinhood Chain (4663)`, `🔵 Base (8453)`, `🟡 BNB Chain (56)`, `⚪ Ethereum (1)`, and `🟪 Solana`. Choose an origin asset and a destination asset on a **different** chain; Relay quotes the route (`/api/relay/*`), and your origin wallet signs the deposit.

Because it can bridge across virtual machines (EVM ↔ Solana), the **destination receive address is always shown and editable** before you approve — so you can see precisely where funds settle.

{% hint style="warning" %}
Relay is an independent third-party provider. Cross-chain transfers carry Relay's fees, routing, and settlement times, all disclosed in the quote.
{% endhint %}

## How it works

```mermaid
flowchart LR
  A[Pick origin asset + chain] --> B[Pick destination asset + chain]
  B --> C[Confirm receive address]
  C --> D[Relay quotes route + time]
  D --> E[Approve on origin if needed]
  E --> F[Sign origin deposit]
  F --> G[Relay bridges]
  G --> H[Funds settle on destination]
```

1. **From** — choose the origin chain + asset and an amount (25% / 50% / 75% / MAX; MAX keeps a native-gas buffer).
2. **To** — choose the destination chain + asset (must differ from the origin).
3. **Receive address** — defaults to your connected destination-family wallet, or paste a custom address. It's validated for the destination VM (0x for EVM, base58 for Solana).
4. **Review** — you receive, receive address, destination, minimum received, bridge fee, price impact, and estimated time.
5. **Execute** — approve the origin token if needed, then sign the origin deposit.

## How to use it

* **Same-chain?** Bridge blocks it — "Pick two different chains." Use [🔄 Swap](/traders/swap.md) for same-chain trades.
* **Solana origin** signs popup-free with your Novamp Solana (Privy) wallet; **EVM origin** signs with your EVM wallet.
* **Always confirm the receive address.** The panel shows a short form of the settlement address and whether it's your connected wallet or a custom one.

## Important details

| Detail          | Behavior                                                          |
| --------------- | ----------------------------------------------------------------- |
| Provider        | Relay (`/api/relay/*`) — third-party                              |
| Direction       | Any chain → any other chain, incl. EVM ↔ Solana                   |
| Receive address | Always visible + editable before approve                          |
| Estimated time  | Shown in the quote (seconds to minutes)                           |
| Settlement      | Funds arrive after the origin tx confirms; can take a few minutes |
| Custody         | Non-custodial on both sides                                       |

## What happens next?

1. Your origin transaction is submitted (Approve → Deposit → Bridging).
2. Relay relays to the destination; the panel shows a **settling** state — you can safely leave the page.
3. On completion you get **Origin tx** and **Destination tx** links, and the destination balance updates once the fill confirms.

{% hint style="warning" %}
Sending to the **wrong address or wrong network can permanently lose funds.** Double-check the receive address — especially when bridging EVM ↔ Solana, where address formats differ. See [⚠️ Trading Risks](/traders/trading-risks.md).
{% endhint %}

## Troubleshooting

| Symptom                     | Likely cause                           | What to do                                                          |
| --------------------------- | -------------------------------------- | ------------------------------------------------------------------- |
| "Pick two different chains" | Origin and destination match           | Change one side, or use [Swap](/traders/swap.md)                    |
| "Add receive address"       | No destination wallet / invalid paste  | Connect the destination wallet or paste a valid address             |
| "Connect Novamp Solana"     | Solana signer not ready                | Connect / wait for the Privy wallet to prepare                      |
| Stuck on "settling"         | Cross-chain settlement in progress     | Wait a few minutes; check the origin tx link                        |
| Funds not arrived           | Wrong receive address / still relaying | Verify the destination tx; contact support if confirmed-but-missing |

## Continue exploring

* [🔄 Swap](/traders/swap.md)
* [🔄 Switch Networks](/getting-started/switch-networks.md)
* [⛓️ Supported Chains](/welcome-to-novamp/supported-chains.md)
* [⚠️ Trading Risks](/traders/trading-risks.md)


---

# 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.novamp.io/traders/bridge.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.
