> 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/supported-chains.md).

# supported chains

Manta Bridge supports routes that move assets between a source chain and Manta Pacific. Always verify the current chain list in the official bridge interface before sending funds, because available routes can change by asset, direction, maintenance status, and liquidity.

## How to Read the Chain List

The supported chain list answers two separate questions:

1. **Where can the transfer start?** This is the source chain selected in the bridge flow.
2. **Where will the asset arrive?** For Manta Bridge deposits, the destination is Manta Pacific. For withdrawals, the source is Manta Pacific and the destination is the supported return chain.

Do not assume that every asset is available on every supported chain. Chain support and asset support are related but separate. After confirming the chain route, also check the current token list in [Supported Assets](file:///2078213/reference/supported-assets.md).

## Chain Categories

| Chain type                            | Role in the bridge                                                                                       | What to verify                                                                                                                |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Ethereum L1                           | Common source for deposits to Manta Pacific and destination for withdrawals back to L1.                  | Confirm the selected route, wallet network, asset, amount, and Ethereum gas estimate before signing.                          |
| Manta Pacific L2                      | Destination for deposits and source chain for withdrawals. ETH is used for gas on Manta Pacific.         | Confirm your wallet is on Manta Pacific when viewing received balances or starting a withdrawal.                              |
| Other supported EVM chains, if listed | Some bridge interfaces may expose additional EVM-compatible source or destination routes when available. | Treat availability as route-specific. Verify the chain, token contract, bridge path, and wallet prompt in the live interface. |
| Test networks, if listed              | May be available for development or testing flows, depending on the bridge environment.                  | Do not send mainnet assets to a testnet route. Confirm whether the interface is mainnet or testnet before using it.           |

## Deposits and Withdrawals

Deposits move assets from a supported source chain to Manta Pacific. The source-chain transaction pays gas on the source chain, and the received asset appears on Manta Pacific after the bridge message is processed.

Withdrawals move assets from Manta Pacific back to a supported destination chain. Because Manta Pacific follows an optimistic-rollup-style exit model, withdrawals may involve multiple steps and require finalization on the destination side. Ethereum's overview of [optimistic rollups](https://ethereum.org/developers/docs/scaling/optimistic-rollups/) explains the general L2 exit model.

{% hint style="warning" %}
A visible chain in a wallet does not mean that route is supported by the bridge. Use the bridge interface as the source of truth for current source chains, destination chains, and route status.
{% endhint %}

## Manta Pacific as the Destination

Manta Pacific is a modular Ethereum L2 built with OP Stack execution and Celestia data availability. The OP Stack provides the L2 execution framework, while Celestia provides a dedicated layer for data availability. For technical background, see the [OP Stack documentation](https://docs.optimism.io/op-stack/protocol/getting-started) and Celestia's guide to [data availability](https://docs.celestia.org/learn/celestia-101/data-availability/).

When bridging to Manta Pacific:

1. Select a supported source chain.
2. Select Manta Pacific as the destination.
3. Choose an asset supported on that route.
4. Review the route details, fees, and wallet prompts.
5. After completion, switch the wallet to Manta Pacific to view and use the asset.

## Before You Bridge

Confirm these details every time:

| Check                         | Why it matters                                                                                                   |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Source and destination chains | Prevents sending from or to the wrong network.                                                                   |
| Asset availability            | Not every supported chain supports every token.                                                                  |
| Wallet network                | The transaction must be signed on the network where the action starts.                                           |
| Gas token balance             | You need the source chain's gas token to submit the transaction, and ETH on Manta Pacific for later L2 activity. |
| Live route status             | Routes can be paused, changed, or unavailable for a specific asset or direction.                                 |


---

# 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/supported-chains.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.