Recover a Manta Bridge Session After Disconnect

To recover a Manta bridge session after a disconnect, reconnect the same wallet account, check the bridge history and transaction status, then continue only with a step that has not already completed. The wallet connection lets the page read your address and request signatures; it does not hold the transfer itself. Once a transaction is signed and sent, its progress is recorded on the chain even if the browser closes.

A deposit can involve two wallet actions: an ERC-20 approval, if needed, and the deposit transaction. Approval lets the bridge contract use the token, but it does not move the token across the bridge. The deposit is a separate transaction. A withdrawal also has separate stages, so a disconnected page may leave you needing to return later and sign a follow-up transaction. For a fuller explanation of the route and its steps, see manta bridge.

What should I check after reconnecting?

Reconnect the wallet you used to start the transfer, then check the selected account and the source and destination networks. If you switched accounts or networks, the page may show a blank balance or history even though the original transaction still exists. The bridge interface has a History view; use it to locate the transfer and see which stage it reports.

If you have a transaction hash, look it up on the explorer for the chain where you submitted it. A hash for an Ethereum deposit belongs on an Ethereum explorer; one for a Manta Pacific transaction belongs on the Manta Pacific explorer. Check whether the transaction is pending, confirmed, or failed. A confirmed deposit may still need time for the destination balance to update, while a failed transaction did not complete that on-chain step.

How do I know whether to submit again?

Do not repeat a transaction just because the page lost its connection or stopped showing progress. First match the wallet address, asset, amount and direction against the history entry and transaction details. The wallet prompt is the point where a requested action becomes a signed transaction; before that, closing the page usually leaves no transaction to recover. After signing, use the hash and history to determine what happened.

• If the wallet never showed a signature request, reconnect and start the intended step again.
• If an approval succeeded but the deposit did not, submit the deposit as a separate action.
• If the deposit transaction is pending, wait for its status to resolve before trying again.
• If it failed, check the error and available gas before making a fresh attempt.

Keep the transaction hash somewhere you can retrieve it. It is a durable reference to the on-chain action; a spinner or disconnected browser tab is only a view of that action. This is like losing the tracking page for a parcel: reconnecting restores the view, but the parcel’s movement has its own record.

What if the transfer is only partly complete?

Follow the status shown for that specific transfer. A bridge can require later processing after the first transaction, and a withdrawal may need another wallet signature at a later stage. Reconnect with the same account, open the existing history entry, and take only the next action the bridge requests. Keep enough ETH on the relevant network to pay for a required transaction.

Before signing, confirm the app address, wallet account, network, asset and transaction details. Never enter a seed phrase into a bridge page or send it to someone offering recovery help. In most cases, recovery means restoring the wallet connection and identifying the last completed transaction—not restarting the transfer.