> 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/compare/vs-other-l2-bridges.md). # vs other l2 bridges Manta Bridge is the native route for moving assets to and from Manta Pacific. This page compares it with third-party L2 bridges across trust assumptions, transfer time, and cost without relying on fixed metrics that can change. ## Native Bridge vs Third-Party Bridges Use [Manta Bridge](https://mantabridge.cc/) when you want the bridge path designed for Manta Pacific deposits and withdrawals. Use third-party bridges only after checking their supported assets, route, contracts, fees, and risk model. | Factor | Native Manta Bridge | Third-party L2 bridges | | ------------ | ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | Primary role | Move assets between Ethereum and Manta Pacific using the native bridge flow. | Route assets through an external bridge, liquidity network, or aggregator. | | Trust model | Depends on Manta Pacific's rollup bridge contracts and the L2's underlying design. | Adds the bridge provider's contracts, liquidity, relayers, routing logic, or validators to the trust surface. | | Deposits | Typically follow the L1 to L2 deposit path. | May use liquidity on the destination chain or an alternate messaging route. | | Withdrawals | Follow the rollup exit model for L2 to L1 withdrawals. | May offer faster exits by using third-party liquidity, but that speed comes from the provider's design rather than changing the rollup's native exit model. | | Cost | Includes network gas and bridge transaction costs shown at execution time. | May include gas, bridge fees, liquidity provider fees, slippage, or route-specific costs. | For broader L2 context, see [Manta Pacific vs Arbitrum](file:///2078213/compare/manta-pacific-vs-arbitrum.md). For timing expectations, see [bridge time](file:///2078213/reference/bridge-time.md). ## Trust Assumptions The native bridge keeps the route focused on Manta Pacific's canonical deposit and withdrawal flow. Manta Pacific uses OP Stack execution and Celestia for data availability, so users should understand both the rollup model and the data availability layer. Ethereum's overview of [optimistic rollups](https://ethereum.org/developers/docs/scaling/optimistic-rollups/) explains the challenge-based model used by optimistic rollups, while Celestia's docs explain [data availability](https://docs.celestia.org/learn/celestia-101/data-availability/). Third-party bridges can be useful, but they introduce additional assumptions. Depending on the provider, users may rely on separate smart contracts, offchain operators, liquidity pools, or bridge-specific security mechanisms. Before using one, review the provider's documentation and contract addresses, then confirm that the route supports Manta Pacific and the exact asset you intend to move. ## Time Deposits from Ethereum to Manta Pacific usually depend on L1 confirmation and L2 processing. Withdrawals from Manta Pacific to Ethereum follow the rollup's exit process, so the native withdrawal path can involve multiple steps and a waiting period. Third-party bridges may provide faster destination-chain liquidity by fronting funds or routing through another system. That can improve user experience, but it does not remove the underlying native exit process; it changes who provides liquidity and which additional system you trust. ## Cost Bridge cost is not a single fixed number. It can change with Ethereum gas, Manta Pacific gas, token approvals, provider fees, liquidity conditions, and route selection. ETH is the gas token on Manta Pacific, so keep enough ETH available for L2 transactions after bridging. For ERC-20 assets such as USDC, the bridge may require a token approval before the transfer. The ERC-20 approval pattern is part of the token standard, and ethereum.org's [ERC-20 reference](https://ethereum.org/developers/docs/standards/tokens/erc-20/) describes the approval and transfer flow. {% hint style="warning" %} Always verify the final route, destination chain, token, approval request, and displayed fees before confirming a bridge transaction. {% endhint %} ## Choosing a Route Choose the native bridge when you want the canonical Manta Pacific bridge path and are comfortable with the rollup deposit or withdrawal flow. Consider a third-party bridge when it supports your asset and destination, you understand the added trust assumptions, and its displayed route, timing, and cost fit your needs. Avoid comparing bridges by stale fee screenshots or old timing claims. Use the live bridge interface and the provider's current documentation for values that can change. --- # 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/compare/vs-other-l2-bridges.md?ask= ``` 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.