As checked on 10 August 2026, manta bridge presents an Ethereum Mainnet-to-Manta Pacific Mainnet route for ETH. It answers a practical question that matters after a transaction appears successful: a completed deposit only becomes useful when the wallet is viewing Manta Pacific and has enough ETH there to pay for the next action. This holds when the sender used the displayed Ethereum-to-Manta Pacific route and the asset is supported by that interface.
Why does manta bridge show a completed deposit but no usable balance?
A completed deposit can look missing when the wallet is still on Ethereum, Manta Pacific has not been added or selected, the token is not displayed in the wallet, or the received balance contains no ETH for gas.
Separate a completed bridge from a usable wallet state
The bridge transaction and the wallet display are different checks. First, confirm that the Ethereum transaction is confirmed. Then switch the wallet to Manta Pacific Mainnet and inspect the balance there. A bridge is the standard way to move assets from Ethereum to a layer 2, while the wallet must still be pointed at that destination network to show and use them. Ethereum’s own guide describes the same sequence: choose the L2, connect on Ethereum Mainnet, review the amount and fees, then add the destination network if needed.
A rollup is a layer 2 that batches transactions and sends results back to Ethereum; it is a separate execution environment, not another tab inside Ethereum Mainnet. That distinction explains the most common “my funds vanished” report: the funds are on the destination chain while the wallet remains on the source chain.
Check the asset before trying to swap it
ETH is the immediate priority after arrival because it pays gas on an Ethereum-compatible network. A token balance without usable gas can leave a user unable to approve a trade, swap, or send the token onward. Keep enough ETH for the destination-chain transaction before treating the deposit as ready for DeFi.
If the transferred asset is an ERC-20—a token using Ethereum’s standard interface for balances, transfers, approvals, and allowances—the wallet may need its correct destination-chain token contract added before the balance is visible. Do not add a contract address copied from a search result or social post. Confirm it through the project or application that issued the asset.
Read a pending withdrawal as a process, not a failure
A return trip to Ethereum is fundamentally different from a deposit. In a standard L1-to-L2 bridge design, assets are locked on L1 and equivalent assets become usable on L2; on the way back, the L2 representation is burned before the L1 asset is released. The Ethereum standard-bridge walkthrough lays out that lock-and-mint, then burn-and-release model.
That is why “withdrawal initiated” is not the same as “ETH is back on Ethereum.” The user must wait for every required stage shown by the route, rather than send a second withdrawal because the first one has not finalized.
“A withdrawal can be proven more than once … and re-proving resets the proof timer.” — Optimism Documentation
That warning matters because proof and finalization are separate operations in OP Stack-style withdrawal flows. The documented withdrawal flow identifies initiation on L2, proving on L1, and finalization on L1 after the relevant challenge period. A pending state can therefore be normal; a duplicate action can make the situation harder to follow.
Choose the route that matches the next move
The right route depends less on the word “bridge” than on where the assets are now, where they must end up, and whether speed or a direct Ethereum-to-Manta Pacific path matters.
| Option | Best when | What to check first | Trade-off |
|---|---|---|---|
| Manta Pacific bridge interface | The assets start on Ethereum Mainnet and the destination is Manta Pacific | Network, asset, ETH gas, destination wallet | A withdrawal back to Ethereum may require staged processing |
| Third-party liquidity bridge | The assets begin on another network or speed is the main constraint | Route provider, destination asset, fee, liquidity, contract | Uses a separate provider and its own route assumptions |
| Exchange withdrawal | The exchange explicitly supports withdrawal to Manta Pacific | Exact network selection and deposit compatibility | The exchange controls availability and withdrawal rules |
The first option fits someone moving ETH from Ethereum into Manta Pacific for onchain use. A third-party route fits someone already elsewhere who accepts a separate provider’s terms. An exchange withdrawal fits only when the exchange explicitly names Manta Pacific; selecting Ethereum instead can send funds to the wrong network for the intended destination.
Stop before signing when any one detail changes
- Confirm the source is Ethereum Mainnet and the destination is Manta Pacific Mainnet.
- Confirm the receiving address is the intended wallet address.
- Confirm the asset and amount shown in the wallet prompt, including any approval.
- Keep ETH for fees on the source chain and, after arrival, on Manta Pacific.
- Use the bridge history and transaction explorer before submitting a repeat transaction.
Resolve the two states before moving funds again
If the deposit is confirmed but invisible, change to Manta Pacific, add the correct token only after verifying its contract, and check whether ETH is available for gas. If the withdrawal is pending, identify its stage—initiated, provable, proven, or finalizable—before doing anything else. Those checks distinguish a display problem from a bridge-process problem.
FAQ
Does a completed deposit mean the token is ready to use?
Only if the wallet is on Manta Pacific, displays the correct asset, and has enough ETH for gas.
Why is the token visible but a swap will not submit?
The wallet may have no ETH on Manta Pacific to pay the transaction fee.
Should a pending withdrawal be sent again?
No. Check its bridge-history stage first; a withdrawal can require proving and finalization before it reaches Ethereum.
Can the same wallet address be used on both networks?
Usually an EVM wallet uses the same address format across networks, but the wallet must be switched to the correct network to view and use that network’s balances.