Why Manta Bridge Deposits Do Not Appear on Manta Pacific
An Ethereum deposit can be final before it appears on Manta Pacific: the bridge must credit the destination chain after the source transaction. The user should first verify the wallet, network, asset, and bridge-history status instead of sending the transfer again.
Why is manta bridge not showing a completed deposit?
A completed Ethereum transaction only proves that the source-chain transaction was accepted; it does not prove that the destination-side credit has already been observed in the right wallet view. The usual cause is a wallet still set to Ethereum Mainnet, an incomplete bridge record, or a transfer made through a different route than expected.
What is the transfer actually doing?
A blockchain bridge, a system that moves assets or messages between otherwise separate blockchain networks, has a source-side action and a destination-side result. Those are related transactions, not one shared balance update.
The official manta bridge interface currently shows Ethereum Mainnet as the source and Manta Pacific Mainnet as the destination for ETH deposits. It also exposes Deposit, Withdraw, and History views. That distinction matters: a deposit is not a swap, and a withdrawal is not evidence that an earlier deposit arrived.
Manta Pacific should be treated as its own network in the wallet. A layer 2, a separate Ethereum-scaling network that extends Ethereum, has a separate balance and transaction history even when the same wallet address controls funds on both networks.
Which check finds the problem fastest?
| What is visible | What it usually means | What to check next |
|---|---|---|
| The Ethereum transaction is pending | The deposit has not finished on the source chain. | Wait for confirmation; do not start a second deposit. |
| The Ethereum transaction succeeded, but bridge History has no record | The wallet may be connected to a different account, or the transaction may not have used the intended bridge route. | Reconnect the sending address and inspect the transaction details. |
| History shows the deposit, but the wallet balance is unchanged | The wallet is likely displaying Ethereum Mainnet or the wrong Manta Pacific account. | Switch to Manta Pacific Mainnet and confirm the full address. |
| The balance appears on Manta Pacific, but an app cannot use it | The app may require a different asset, token interface, or a small amount of native ETH for gas. | Check the app’s supported asset and its network selector. |
Why checking the address alone is not enough
An EVM wallet often uses the same hexadecimal address on Ethereum and Manta Pacific. That makes an address match reassuring but incomplete. The relevant question is whether the wallet is connected to the correct chain and whether the bridge record belongs to that same account.
Wallet extensions can silently show another imported account, a hardware-wallet account, or a recently selected address. Before diagnosing a missing deposit, the user should compare the sender shown in the Ethereum transaction with the connected address shown in the bridge. They must match character for character.
What should be checked before trying again?
- Open the Ethereum transaction and confirm that its status is successful, not pending or reverted.
- Reconnect the exact sending wallet to the bridge and inspect its History entry rather than relying on the browser’s previous session.
- Switch the wallet to Manta Pacific Mainnet, then refresh the balance and the destination-side activity.
- Confirm that ETH was deposited, not an unsupported token or a transfer sent to a look-alike contract or third-party route.
When is it time to stop troubleshooting locally?
Escalation is appropriate when the Ethereum transaction is successful, the connected sending address is correct, Manta Pacific Mainnet is selected, and the bridge History entry still does not resolve. The useful support package is the Ethereum transaction hash, the sending address, the selected source and destination networks, the asset, and a screenshot of the History status. A seed phrase, private key, or wallet-recovery request is never part of bridge support.
The important restraint is simple: a second deposit does not repair an unlocated first one. It creates a second transaction to reconcile. The bridge record and the selected Manta Pacific network should be resolved before any further transfer is submitted.