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

# Bridge

Use [Bridge to Onyx](https://app.onyx.org/bridge) to move **XCN**, **ETH**, and **USDC** between Ethereum Mainnet and Onyx Mainnet.

The bridge supports both directions. Fees, minimums, and processing times differ by direction. Always confirm current values in the app before you submit a transfer.

## Supported assets

| Asset    | Ethereum    | Onyx                           |
| -------- | ----------- | ------------------------------ |
| **XCN**  | ERC-20 XCN  | Native XCN (gas and transfers) |
| **ETH**  | Native ETH  | Bridged ETH (18 decimals)      |
| **USDC** | ERC-20 USDC | Bridged USDC (6 decimals)      |

All three assets can move in both directions when the bridge is operational. If an asset is unavailable in the app, treat it as unsupported regardless of what appears elsewhere in the ecosystem.

## Fees

Bridge fees are application-level charges and are separate from Onyx network gas. They can include a percentage charge, a per-asset minimum fee, or both. Directional fees and minimum transfer amounts can change.

Use the [Onyx Bridge](https://app.onyx.org/bridge) for the exact amount you will receive. Integrations must fetch the current limits and a live fee quote immediately before confirmation; documentation examples are not a source of truth for mutable bridge values.

See [Network Fees](/developer-guide/network-fees.md) for transactions submitted on Onyx. Transactions submitted on Ethereum incur Ethereum network gas separately.

## Processing times and delays

Bridge transfers are not instant. Each transfer moves through several phases:

1. **Source confirmation** — your transaction is confirmed on the sending chain.
2. **Security hold** (Onyx → Ethereum only) — withdrawals wait approximately **1 hour** before the relayer submits the Ethereum leg.
3. **Relay** — the bridge operator processes the transfer.
4. **Destination submission** — the receiving-chain transaction is broadcast.
5. **Completion** — funds arrive at your destination address.

Total time depends on network congestion, relayer load, and the direction you are bridging. Track progress in the Bridge app. A successful source transaction does not mean the destination leg has finished.

When bridge health is degraded, the app may enter maintenance mode and pause new transfers. Existing transfers can still be tracked — do not resubmit the same transfer.

For bridge APIs, smart-account requirements, and integration details, see [Bridge Integration](/developer-guide/bridge.md). External integrators use **`https://bridgeapi.onyx.org/api/v1`**.


---

# 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.onyx.org/onyx-defi/onyx-app/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.