> 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/manta-pacific-vs-arbitrum.md). # manta pacific vs arbitrum Manta Pacific and Arbitrum are both Ethereum L2 ecosystems, but they make different design choices around execution, data availability, and withdrawal flow. This page compares those choices at a bridger level, without assuming fixed fees, speeds, or market conditions. ## Quick Comparison | Area | Manta Pacific | Arbitrum | | ------------------ | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | | Execution design | EVM-compatible L2 using OP Stack-style execution. | EVM-compatible L2 built on Arbitrum Nitro. | | Data availability | Modular design that uses Celestia for data availability. | Posts rollup data to Ethereum, using the mechanisms supported by Arbitrum Nitro. | | Gas token | ETH is used for gas on Manta Pacific. | ETH is used for gas on Arbitrum One. | | Bridging direction | Deposits move assets from Ethereum L1 to Manta Pacific; withdrawals return assets from Manta Pacific to L1. | Deposits move assets from Ethereum L1 to Arbitrum; withdrawals return assets through Arbitrum's rollup bridge flow. | | ERC-20 handling | ERC-20 deposits require an approval before the bridge can transfer the token. | ERC-20 deposits generally require approval before the bridge or gateway can transfer the token. | ## Design Difference ### Manta Pacific: modular DA Manta Pacific separates execution from data availability. In this model, the L2 executes transactions while Celestia provides the data availability layer used by the rollup design. Celestia describes data availability as the ability for network participants to verify that block data has been published and can be retrieved when needed in its [data availability documentation](https://docs.celestia.org/learn/celestia-101/data-availability/). For a bridger, the practical takeaway is simple: Manta Pacific is still an Ethereum L2 experience for deposits, withdrawals, wallets, and ERC-20 approvals, but its underlying cost and publication model is modular. Read the overview of [what Manta Pacific is](file:///2078213/getting-started/what-is-manta-pacific.md) for the network-level context. ### Arbitrum: Nitro rollup architecture Arbitrum uses the Nitro stack, with transaction ordering, batching, execution, validation, and bridging handled by Arbitrum-specific components. Arbitrum's docs describe Nitro as routing transactions through a sequencer, executing them with an EVM-compatible state transition function, and supporting parent-to-child and child-to-parent bridge messaging in the [Inside Arbitrum Nitro](https://docs.arbitrum.io/how-arbitrum-works/inside-arbitrum-nitro) overview. For a bridger, the important distinction is not that one system is "better" in all cases. It is that the bridge mechanics, withdrawal path, fee calculation, and confirmation assumptions are chain-specific. ## What This Means When Bridging ### Deposits Deposits are usually the simpler direction on both networks. You start on Ethereum L1, approve the token if it is an ERC-20, then submit the bridge transaction. The destination L2 balance becomes available after the bridge and network have processed the deposit. Do not assume the same total cost across Manta Pacific and Arbitrum. A deposit can include wallet gas, approval gas, bridge contract interaction, and L2-related costs. Check the live bridge interface before confirming. ### Withdrawals Withdrawals follow each rollup's exit model. That means the L2-to-L1 path is not just a normal token transfer; it depends on cross-chain messages and the validation/finality process of the source L2. The OP Stack documentation explains the OP Stack protocol model in its [protocol overview](https://docs.optimism.io/op-stack/protocol/overview), while Arbitrum documents its own child-to-parent messaging and withdrawal flow in the Nitro docs. Plan withdrawals with more care than deposits. Confirm the current withdrawal steps, expected completion flow, and any required claim or finalization action in the official bridge UI before sending funds. ## Which One Should You Use? Use Manta Pacific when you want to bridge into the Manta Pacific ecosystem, use applications deployed there, or hold assets on that network. Use Arbitrum when your target application, liquidity, or wallet workflow is on Arbitrum. The bridge choice should follow the destination chain you actually need. If you are comparing bridge UX across networks, see [Manta Bridge vs other L2 bridges](file:///2078213/compare/vs-other-l2-bridges.md). {% hint style="warning" %} Always verify the selected network, token contract, wallet address, approval request, and live fees before confirming a bridge transaction. {% endhint %} --- # 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/manta-pacific-vs-arbitrum.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.