A manta bridge deposit is not usable until the source-chain transaction has succeeded and the destination-side credit has completed. A wallet can show that tokens left one network while Manta Pacific has not yet reflected them; that is a state to verify, not a reason to submit the transfer again. The transaction hash, selected route, token, and receiving address settle what happened.
A completed wallet prompt does not prove the destination received funds
A completed wallet prompt only proves that the wallet submitted a transaction; the network must still include and execute it. Ethereum transactions are state changes that require validation and a fee, so a pending, reverted, or dropped source transaction cannot create a destination balance. Ethereum’s transaction documentation describes that validation path.
Bridges move assets or messages between networks that otherwise do not communicate natively, and their security and completion time depend on the route’s verification design. Ethereum’s bridge reference notes the trade-off among security, speed, connectivity, and cost. A source confirmation is therefore the first checkpoint, not necessarily the final one.
Check the source transaction before touching the bridge again
The source transaction is the authoritative starting point. Copy its transaction hash—the cryptographic identifier created for a submitted transaction—and inspect it in the explorer for the network from which funds were sent. A transaction hash is generated before broadcast, allowing the exact action to be checked independently of any wallet display.
- Confirm the status is
Success, notPending,Failed,Reverted, orDropped. - Confirm the sender address, destination address, token contract, and amount match the intended transfer.
- Confirm the wallet was connected to the intended source network when the transaction was signed.
- Open the bridge’s history and match the hash, rather than relying on a similarly timed wallet entry.
If the source transaction failed, the token transfer did not complete as intended; repeating the bridge action may be appropriate only after identifying why it failed.
“Success” can still mean the transfer is awaiting the second leg
A successful source transaction can leave the transfer waiting for the bridge’s destination processing, claim action, or available route liquidity. The useful distinction is between an on-chain source success and a completed cross-chain credit. Do not send a second deposit while the first hash is still associated with a pending bridge record: duplicate transfers are a more common operational mistake than a mysteriously vanished balance.
Choose the next action from the status, not the elapsed time
| What is visible | Most likely meaning | Best next action |
|---|---|---|
| Source transaction pending | The network has not finalized the request | Wait or use the wallet’s replacement option if it supports one |
| Source transaction reverted | The contract call failed | Read the explorer error; do not retry blindly |
| Source success, bridge history pending | Destination processing is incomplete | Keep the hash and wait for the route status to change |
| Source success, no bridge record | Wrong site, route, network, or wallet session may have been used | Verify every field before contacting support |
| Bridge record completed, wallet shows no token | The asset may need its token contract added or the wallet network switched | Switch to Manta Pacific and import the verified token contract if needed |
Waiting fits a pending route with a valid hash. Investigation fits a reverted transaction or mismatched record. Support fits a successful source transaction whose bridge record remains unresolved after the interface’s normal processing window; provide the hash, wallet address, source network, destination network, token, and amount, but never a seed phrase or private key.
Gas, token approval, and the two costs that can confuse the result
Gas is the unit measuring computational work, with the fee paid whether an Ethereum transaction succeeds or fails. Ethereum’s gas documentation explains why a failed contract call can still consume a fee. An approval is separate: it authorizes a contract to spend a token, while the later bridge transaction actually moves it.
A bridge can require both an approval and a deposit transaction. Seeing the approval succeed does not mean the deposit was sent. Conversely, seeing a fee deducted does not establish that the right token, route, or recipient was used.
What to preserve if the transfer needs escalation
A manta bridge case is easiest to resolve when it contains the source transaction hash, the wallet address, the exact token and amount, both selected networks, a screenshot of the bridge status, and the approximate submission time. Those details let support distinguish a pending cross-chain credit from a failed contract call, an unsupported asset, or a wallet-display issue without asking for sensitive credentials.