> For the complete documentation index, see [llms.txt](https://mantabridge.gitbook.io/manta-bridge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mantabridge.gitbook.io/manta-bridge-docs/troubleshooting.md). # troubleshooting Use this page to narrow common Manta Bridge issues by symptom, cause, and next action. For live status, verify in [Manta Bridge](https://mantabridge.cc/), your wallet, and the relevant block explorer before retrying. ## Quick checks first Before troubleshooting: 1. Confirm the connected wallet is the same wallet that started the transfer. 2. Confirm the selected direction: Ethereum L1 to Manta Pacific for deposits, or Manta Pacific to Ethereum L1 for withdrawals. 3. Check whether the next required action is on Ethereum or Manta Pacific. 4. Keep enough ETH on the network where you need to submit the next transaction. 5. Review [bridge timing](/manta-bridge-docs/reference/bridge-time.md) before assuming a transfer failed. ## Common symptoms | Symptom | Likely cause | What to do | | ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Transfer looks pending | The source transaction may still be confirming, the bridge message may still be processing, or a withdrawal may be in the rollup exit process. | Check the source transaction hash. For withdrawals, review [bridge timing](/manta-bridge-docs/reference/bridge-time.md). Do not submit duplicates unless the bridge interface or wallet clearly requires a new action. | | Funds are not showing on the destination network | The wallet may be on the wrong network, the token may be hidden, or the bridge message may not be complete. | Switch to the destination network and confirm the same wallet address. Add the token if needed, then check the bridge interface and explorers. | | Wrong network is selected | The wallet is connected to Ethereum when the next step is on Manta Pacific, or the reverse. | Switch networks from the bridge prompt or wallet selector. Deposits start on Ethereum L1; withdrawals start on Manta Pacific and may require a later Ethereum L1 completion step. | | Token approval is needed or stuck | ERC-20 transfers require an approval before the bridge contract can move the token. The approval may be pending, rejected, or too low. | Check the approval transaction first. If it failed or was rejected, approve again from the correct network. If the allowance is too low, update it deliberately. See [token approvals](/manta-bridge-docs/guides/token-approvals.md). | | Not enough ETH for gas on Manta Pacific | ETH is the gas token on Manta Pacific, so Manta Pacific actions require ETH there even when bridging USDC or another ERC-20. | Add enough ETH on Manta Pacific for the required transaction. Verify the live wallet prompt before signing; do not rely on old fee estimates. | | Withdrawal is taking longer than a deposit | Withdrawals follow the rollup exit model, while deposits complete after the L1 transaction and L2 message processing. | Track the withdrawal in the bridge interface. Expect separate phases and possible later action on Ethereum L1. For background, see Ethereum's [optimistic rollups](https://ethereum.org/en/developers/docs/scaling/optimistic-rollups/) and the OP Stack [withdrawal flow](https://docs.optimism.io/op-stack/bridging/withdrawal-flow/). | ## When to avoid retrying Avoid repeated signing when you are unsure whether the first transaction was submitted. A wallet confirmation, pending transaction, or explorer record can mean the action is already in progress. Retry only after checking: * the transaction hash on the source network; * the bridge interface for any required next step; * the selected wallet account and network; * whether the action was an approval or the bridge transfer. ## Security checks If a prompt asks for an unfamiliar token approval, spender, network switch, or transfer amount, stop and verify the route. Bridges involve smart contracts, wallets, and multiple networks, so careful review is part of normal use. For broader safety guidance, read [is Manta Bridge safe?](/manta-bridge-docs/security/is-manta-bridge-safe.md). For short answers to related questions, see the [FAQ](/manta-bridge-docs/faq.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://mantabridge.gitbook.io/manta-bridge-docs/troubleshooting.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.