Why Is My Manta Bridge Withdrawal Still Pending?
Three on-chain stages—initiation on Manta Pacific, a proof stage, and final completion on Ethereum—can sit between an exit request and spendable L1 funds. In the manta bridge history, “pending” normally describes an unfinished stage, not a reason to start over. The holder should identify the last confirmed transaction, wait for the next bridge action, and keep ETH available on the network that action names.
Manta bridge: a pending withdrawal has a next state
A bridge is not a token swap. It carries assets or messages between separate blockchain environments, which is why the destination balance can remain unchanged while the source-side transaction is already confirmed. Ethereum’s bridge overview describes bridges as the connection that moves assets and information between chains.
For an L2 exit, the important distinction is between confirmed and finished. A confirmation on Manta Pacific records the withdrawal request. It does not necessarily mean Ethereum has released the corresponding asset. Do not submit a duplicate withdrawal merely because the history entry is still visible.
Chain ID 169 and ETH decide the first check
Manta Network lists Manta Pacific as an L2 rollup with Chain ID 169 and ETH as its currency in its Manta Pacific network configuration. The transaction hash should therefore be checked on the Manta Pacific side first, with the wallet connected to that network.
Gas is the transaction fee paid to execute an on-chain action. ETH is needed for the initial Manta Pacific withdrawal and may also be needed later when the bridge asks for an Ethereum-side action. A wallet with no ETH on the network currently requested by the interface cannot complete that stage.
ERC-20 approval is not the withdrawal
An ERC-20 token follows a standard interface that can let an owner approve a contract to spend a stated amount. For a token withdrawal, the first wallet confirmation may be that approval; the separate bridge transaction is what actually starts the exit.
If only the approval succeeded, return to the bridge and look for the withdrawal transaction that follows it. If the withdrawal transaction itself succeeded, avoid changing allowances or repeating the action until the history identifies a failure or exposes the next required step.
3 history conditions that call for different actions
| Condition | What it means | Useful next action |
|---|---|---|
| The Manta Pacific transaction reverted or was never confirmed | The withdrawal did not begin. | Check the wallet’s error, balance, selected asset, and L2 ETH for gas before attempting a new transaction. |
| The L2 transaction is confirmed but history shows no Ethereum action | The exit is waiting to become actionable. | Keep the transaction hash and wait; submitting the same withdrawal again creates a separate request. |
| History offers a proof, relay, complete, or finalise action | The next stage must execute on Ethereum. | Switch the wallet to Ethereum Mainnet, retain ETH for gas, and sign only that named action. |
Proof maturity, not a spinner, explains the long wait
OP Stack withdrawal specifications describe an L2-to-L1 exit as an L2 initiation followed by an L1 proof and L1 finalization after the required maturity period. The protocol flow makes clear that a withdrawal is finalized by an Ethereum transaction, rather than by the original L2 transaction alone.
That is why a generic time estimate is less useful than the status in bridge history. “Pending” is expected before the next action is available; “ready” means the wallet must return on the named chain. Only a reverted transaction, a missing confirmed hash, or an explicit interface error calls for troubleshooting rather than waiting.