> 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-assets.md).

# supported assets

Manta Bridge supports moving selected assets between Ethereum and Manta Pacific, including native ETH and supported ERC-20 tokens such as stablecoins. The exact asset list can change, so always verify the live options in [Manta Bridge](https://mantabridge.cc/) before starting a transfer.

## Asset Support Model

Assets are supported by route, source chain, destination chain, and token contract. A token being available on one route does not mean it is available on every route or direction.

| Asset type            | Examples                                            | How it usually works                                                                                                                                                       | Verify live                                                                                               |
| --------------------- | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| Native gas asset      | ETH                                                 | ETH is used to pay gas on Ethereum and Manta Pacific. Depositing ETH moves value from L1 to L2 so it can be used for transfers and contract interactions on Manta Pacific. | Check the bridge asset selector, route preview, destination chain, and wallet prompt.                     |
| ERC-20 tokens         | USDC and other supported tokens                     | ERC-20 transfers typically require a token approval before the bridge transaction can move the selected amount.                                                            | Confirm the token symbol, contract details when shown, allowance prompt, amount, and destination network. |
| Route-specific assets | Assets listed only for certain chains or directions | Some assets may be available only from specific source chains, to specific destination chains, or through specific bridge routes.                                          | Review the live supported chain and asset combination before signing.                                     |

For the current network list, see [Supported Chains](file:///2078213/reference/supported-chains.md). To bridge native ETH to Manta Pacific, follow [How to Bridge ETH to Manta Pacific](file:///2078213/guides/bridge-eth-to-manta-pacific.md).

## ETH

ETH is the native gas token for Manta Pacific. You need ETH on Manta Pacific to pay for L2 transactions after a deposit, and you need ETH on Ethereum to pay Ethereum gas when starting an L1 transaction.

When bridging ETH:

1. Select the correct source and destination chains.
2. Choose ETH in the asset selector.
3. Enter the amount to bridge.
4. Review the estimated costs and destination address.
5. Confirm the transaction in your wallet.

Gas is dynamic and depends on network conditions and transaction execution. For background, see Ethereum's [gas documentation](https://ethereum.org/developers/docs/gas/).

## ERC-20 Tokens

ERC-20 assets, such as supported stablecoins, follow a token contract standard rather than using native ETH balance mechanics. Before an ERC-20 can be bridged, your wallet may ask you to approve the bridge contract to spend the selected token amount.

When bridging an ERC-20 token:

1. Check that the token appears for the selected route.
2. Confirm the token symbol and network.
3. Review the approval request, if one is required.
4. Submit the bridge transaction after approval.
5. Keep enough ETH on the source chain to pay gas.

Approvals are separate onchain transactions and may have their own gas cost. For the token standard behind this flow, see Ethereum's [ERC-20 token standard](https://ethereum.org/developers/docs/standards/tokens/erc-20/).

{% hint style="warning" %}
Do not approve a token or sign a bridge transaction based only on a previous transfer, screenshot, or third-party list. Use the live bridge interface and your wallet prompts as the source of truth.
{% endhint %}

## Deposits and Withdrawals

Deposits move assets from Ethereum L1 to Manta Pacific L2. Withdrawals move assets in the opposite direction and follow the rollup exit model, which can involve different steps and timing than deposits.

Manta Pacific uses OP Stack execution with Celestia data availability. For general background on rollup exits and optimistic rollups, see Ethereum's [optimistic rollups overview](https://ethereum.org/developers/docs/scaling/optimistic-rollups/).

## Before You Transfer

Before confirming any bridge action, verify:

* The source chain and destination chain.
* The selected asset and amount.
* The receiving wallet address.
* Any ERC-20 approval request.
* The live route, status, and fees shown in the bridge interface.
* That you have enough ETH for gas on the chain where you are submitting the transaction.

Live asset support, route availability, and costs can change. If an asset is not shown for the route you selected, treat it as unsupported for that route unless the official bridge interface shows otherwise.


---

# 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-assets.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.
