Skip to main content
Hashbeam

Crypto protocols, markets and policy

db53d6

Why a Bridged Token May Not Pay Manta Pacific Gas

A bridged token does not automatically pay Manta Pacific fees: destination transactions need ETH, and each transaction carries execution gas plus an L1 data fee.

The Hashbeam Desk··5 min read

Why a Bridged Token May Not Pay Manta Pacific Gas

A bridge transfer can deliver a token to Manta Pacific without giving the receiving wallet the ETH it needs to spend that token. The bridge moves or credits the selected asset; a later swap, contract call or token transfer is a separate transaction on the destination chain. That transaction needs destination gas, paid from the wallet’s ETH balance, and Manta Pacific also charges an L1 data fee.

This distinction matters when the asset arriving is a stablecoin or MANTA. The balance can be visible and spendable in principle while the account still cannot submit the transaction that would spend it. For the route itself—what changes as funds move across chains—see this explanation of what changes in a Manta Bridge transfer. Gas is a separate question: it depends on the destination network and the transaction you submit after arrival.

Why can’t the bridged token pay destination gas?

Manta Pacific charges transaction fees in ETH, so a token balance alone does not fund an ordinary transaction from the wallet. In an EVM transaction, the sender authorizes an operation and the network charges for the computation and data it processes. The token being transferred is an input to that operation; it does not become the fee currency just because it has arrived on the same chain.

For example, a wallet can receive USDC on Manta Pacific and still lack the ETH needed to send that USDC to another address. Sending the stablecoin is an EVM transaction initiated by the wallet. The network deducts its fee in ETH from that wallet, separately from the USDC amount. The same applies when the wallet calls a decentralized exchange to swap the USDC: the swap contract may accept USDC as a trade asset, but the call itself still needs ETH for fees.

MANTA is also not a substitute for ETH as Manta Pacific’s default gas currency. Manta Network documentation lists MANTA as an ERC-20 token on Pacific and describes MANTA as a transaction-fee token on Manta Atlantic. Those roles should not be conflated. Unless a particular app provides a fee-paying mechanism such as a paymaster, the normal Manta Pacific wallet transaction requires ETH.

What does a Manta Pacific transaction fee include?

A Manta Pacific transaction fee has an execution-gas component and an L1 data fee. Execution gas accounts for the work performed by the EVM: a simple token transfer generally uses less computation than a contract interaction with multiple storage changes. The L1 data fee accounts for the transaction data that the rollup needs to publish to its data-availability layer.

Manta Pacific’s technical documentation describes this distinction from Ethereum: Pacific transactions require an L1 data fee in addition to standard execution gas, and fee computation parameters differ. That means an Ethereum fee estimate cannot simply be reused as a Pacific estimate. The wallet or application should estimate the fee using Pacific’s network data when you prepare the destination transaction.

Both components can vary with the operation and network conditions. A transaction that reverts may still consume execution gas because the network processed it, and the data fee can still apply because transaction data was submitted. The exact amount is therefore not a fixed charge per token or per bridge arrival. It is tied to the transaction sent on Pacific.

How should you prepare to use funds after bridging?

Before bridging, decide what action you plan to take after the funds arrive and make sure the destination wallet has ETH for that action. A bridge quote for the incoming asset does not, by itself, guarantee that you can make a second transaction. If you bridge only USDC to a wallet with no ETH, the USDC may arrive correctly while remaining unusable for an ordinary outbound transfer until you obtain gas.

  • Check that the receiving wallet address is the one you control on Manta Pacific.
  • Check which asset the bridge will credit and whether that asset is the one your next application accepts.
  • Keep or acquire ETH on Manta Pacific to pay for the next wallet transaction.
  • Use the wallet’s Pacific fee estimate for the specific transfer or contract call before signing.

The practical choice for most users is to plan the bridge amount and destination gas together: arrange for a small ETH balance on Pacific if the bridged asset is not ETH, or ensure enough ETH remains after the transfer if ETH is the asset being bridged. Do not assume that an app’s displayed swap fee includes the network fee; the interface should show whether it sponsors gas or expects the connected wallet to pay it.

If the destination balance appears but a transaction cannot be submitted, first check the wallet’s selected network and ETH balance on Manta Pacific. A token arriving successfully confirms the bridge leg; it does not confirm that the receiving account can pay for a later transaction. Keeping those two operations separate makes the failure easier to diagnose: the bridge credits the asset, while the wallet’s ETH pays for subsequent Pacific execution and data publication.