The clean answer is also the easy one to misuse: Manta Pacific gas is paid in ETH.
That does not mean every cost around Manta Bridge is one simple ETH fee. A bridge transaction can touch Ethereum L1, an ERC-20 approval, a bridge contract, Manta Pacific execution, and later a rollup withdrawal path. The gas token is ETH on Manta Pacific, but the total user cost depends on where the transaction is happening and what the transaction is asking the chain to do.
This memo keeps the scope narrow: how gas works when you move assets such as ETH or USDC to and from Manta Pacific, why Manta Pacific's OP Stack plus Celestia design can support lower-cost activity by mechanism, and what to verify before trusting a wallet quote. No live fee numbers. No made-up averages. Those belong in the interface at the moment you sign.
Manta Pacific is a modular Ethereum Layer 2: OP Stack execution, Celestia data availability, and ETH-native gas on the L2. In practical terms, the user pays ETH for transactions on Manta Pacific in the same broad sense that Ethereum users pay gas for computation, but an L2 fee has additional accounting around data publication or data availability.
Ethereum's own technical overview of gas is the right baseline: gas measures computational effort, and transaction fees depend on gas used and the price per gas unit. On an L2, the execution environment may feel familiar to an EVM wallet, but the full fee picture is not a copy of Ethereum mainnet.
That distinction is where most user confusion starts. Manta Bridge is not charging "gas" as a single platform toll; it is helping a user move assets across systems that each have their own fee surface.
The table below is intentionally illustrative. It is a reading guide for transaction prompts, not a schedule of actual fees.
| Layer of the action | Gas token or cost unit | What is being paid for | When it matters | What can change before signing |
|---|---|---|---|---|
| Ethereum L1 deposit transaction | ETH on Ethereum | The source-chain transaction that starts a bridge deposit | Bridging from Ethereum into Manta Pacific | L1 congestion, transaction complexity, wallet gas settings |
| ERC-20 approval | ETH on the source chain | Permission for a contract to move a token such as USDC | Before some token deposits, if allowance is insufficient | Token, spender address, allowance amount, prior approvals |
| Bridge contract interaction | Usually source-chain gas for deposits | The contract call that encodes the asset, amount, destination, and recipient | During deposit or routing | Asset support, route, contract path, current gas estimate |
| Manta Pacific execution | ETH on Manta Pacific | Transfers, swaps, claims, app interactions, and other L2 execution | After assets arrive on Manta Pacific | L2 fee parameters, transaction complexity, ETH balance |
| Data availability component | Embedded in L2 fee design | The cost of making transaction data available to the relevant network participants | For L2 transactions, depending on chain configuration | Data size, DA layer conditions, rollup fee configuration |
| Withdrawal path | ETH on the relevant chain at each step | Exit initiation, proof/finality, and claim/finalization actions as applicable | Leaving Manta Pacific for Ethereum or another route | Rollup model, bridge route, required steps, current network state |
The useful habit is to ask which row you are looking at. An approval is not a deposit. A deposit is not an L2 swap. A withdrawal is not just a deposit in reverse.
For the user, ETH as the gas token means a simple rule: keep enough ETH on Manta Pacific to do the next transaction after your assets arrive. If you bridge only USDC and have no ETH on Manta Pacific, you may be able to see the balance but still be unable to move it without gas.
This is not special pleading for one bridge; it is how account-based chains feel when the asset you hold is not the asset needed for fees. Ethereum's ERC-20 token standard explainer is useful context here because ERC-20 transfers and approvals are contract interactions, not native ETH transfers. They can require approval logic, allowance checks, and a gas-paying account.
Manta Bridge should therefore be read as two related workflows. First, move the asset. Second, preserve enough ETH on the destination network to use it. The second step is boring until it is the only thing blocking you.
For user-level terminology, the gas fees explainer is useful because it keeps ETH-as-gas separate from bridge routing, approvals, and withdrawal planning. Those categories blur together quickly when a wallet reduces the whole process to a few confirmation screens.
Low-cost L2 activity is not magic. It comes from moving execution off Ethereum mainnet while preserving a path back to Ethereum security assumptions and making transaction data available in a cheaper, scalable way.
Celestia matters because data availability is one of the major cost and design constraints for rollups. Celestia's own data availability documentation frames the core question as whether block data has been published so network participants can download and verify it. That is the DA part of "modular": execution and data availability are not forced into one monolithic layer.
For Manta Pacific, the mechanism is the point. OP Stack handles the EVM-style execution layer; Celestia supplies modular data availability; ETH remains the gas token users need on the L2. This combination can make transactions cheaper than doing comparable activity directly on Ethereum mainnet, but it does not entitle anyone to quote a universal discount or future fee.