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

# what is manta bridge

Manta Bridge is the bridge interface for moving supported assets, such as ETH and USDC, to and from Manta Pacific. It helps users move value between Ethereum L1 and Manta Pacific while preserving the chain-specific rules for deposits, withdrawals, gas, and token approvals.

## Overview

Manta Pacific is a modular Ethereum L2 that uses OP Stack execution and Celestia for data availability. Manta Bridge connects users to the contracts and transaction flow needed to bring assets onto Manta Pacific, use them in L2 applications, and withdraw them back when needed.

Use [Manta Bridge](https://mantabridge.cc/) to review the current supported networks, assets, fees, and transaction status before submitting a transfer.

## What Problem Does It Solve?

Assets do not automatically exist on every chain. If you hold ETH or an ERC-20 token on Ethereum L1, that balance is separate from the corresponding balance available on Manta Pacific.

Manta Bridge provides the path between those environments:

| Direction  | Meaning                                               | Typical Use                                                     |
| ---------- | ----------------------------------------------------- | --------------------------------------------------------------- |
| Deposit    | Move assets from Ethereum L1 to Manta Pacific L2      | Fund a wallet for apps, swaps, or transactions on Manta Pacific |
| Withdrawal | Move assets from Manta Pacific L2 back to Ethereum L1 | Return assets to Ethereum or another L1-based workflow          |

ETH is also the gas token on Manta Pacific, so users need ETH on the destination network to pay for transactions after bridging.

## Deposits at a High Level

A deposit moves assets from L1 to L2.

1. Connect a wallet to the bridge.
2. Choose the source network, destination network, asset, and amount.
3. For ERC-20 tokens, approve the bridge contract if approval is required.
4. Submit the deposit transaction from the source chain.
5. Wait for the bridge interface to show the asset as available on Manta Pacific.

Deposits require source-chain gas, and ERC-20 deposits may require a separate approval transaction before the bridge transaction. For background on token approvals, see ethereum.org's guide to [ERC-20 tokens](https://ethereum.org/developers/docs/standards/tokens/erc-20/).

## Withdrawals at a High Level

A withdrawal moves assets from Manta Pacific back to Ethereum L1. Because Manta Pacific follows a rollup-style exit model, withdrawals are not the same as ordinary same-chain transfers. The transaction must follow the bridge and rollup process before funds are available on the destination chain.

At a high level:

1. Start the withdrawal from Manta Pacific.
2. Pay the required L2 gas.
3. Follow the bridge status until the withdrawal is ready for the next step.
4. Complete any required claim or finalization action on the destination chain.

Always verify the live status, expected steps, and current network costs in the bridge interface before withdrawing. For more context on rollup mechanics, see ethereum.org's overview of [optimistic rollups](https://ethereum.org/developers/docs/scaling/optimistic-rollups/).

## How Manta Bridge Fits with Manta Pacific

Manta Bridge is the asset movement layer for users who want to enter or exit Manta Pacific. Manta Pacific itself is the L2 execution environment where users transact after assets arrive.

To understand the network first, read [What Is Manta Pacific?](file:///2078213/getting-started/what-is-manta-pacific.md). For a step-by-step explanation of the bridge flow, approvals, and transaction lifecycle, continue to [How It Works](file:///2078213/getting-started/how-it-works.md).

For background on Manta Pacific's modular data availability design, see Celestia's documentation on [data availability](https://docs.celestia.org/learn/celestia-101/data-availability/).


---

# 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:

```
GET https://mantabridge.gitbook.io/manta-bridge-docs/what-is-manta-bridge.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.