Three Checks for a Polygon PoS Withdrawal That Is Waiting

A Polygon PoS withdrawal to Ethereum can wait at three distinct stages: the Polygon burn, the validator checkpoint, or the Ethereum exit transaction. Find the burn transaction hash first, then check whether its block has been checkpointed and whether an exit has been submitted on Ethereum. Each stage has a different cause and next action.

Which Polygon withdrawal route did you use?

Check the source and destination networks, asset, and route shown for the pending transfer. Polygon PoS withdrawals use a burn on Polygon followed by a proof-based exit on Ethereum, while other routes can use different contracts and timing rules. The breakdown of Polygon Bridge withdrawal routes explains why a transfer estimate only makes sense once you know which path the interface selected.

Confirm that the source transaction succeeded on Polygon PoS. A wallet prompt that was rejected, a transaction that reverted, or a transaction that remains unconfirmed has not completed the burn stage. In that case, there is no valid burn for a later exit to prove. Use the transaction hash from the wallet or bridge history to check the result on a Polygon block explorer; do not rely only on a “pending” label in the bridge interface.

Also verify the asset and recipient shown in the bridge record. A withdrawal releases the corresponding asset on Ethereum according to the bridge’s mapping and the destination address recorded for that transfer. A token with a similar ticker is not necessarily the same asset, and a successful burn does not mean the funds have arrived on Ethereum yet.

Has the Polygon burn been checkpointed?

The PoS exit cannot be completed until a Polygon validator checkpoint covers the block containing the burn. The burn destroys the Polygon representation of the asset. Validators later submit a checkpoint to Ethereum, committing to Polygon block data; the bridge uses that checkpoint and transaction-inclusion proof to verify the burn.

Check the burn’s block and its checkpoint status. If the burn is confirmed but the block has not been checkpointed, the transfer is waiting on the bridge’s proof prerequisite. Reopening the portal or reconnecting the wallet cannot create that checkpoint. Wait for the checkpoint, then check the same transfer again. Checkpoint timing can vary, so an estimate is not a guarantee that the next interface refresh will show the proof as ready.

When the checkpoint is available, the next step is a separate Ethereum transaction. The bridge constructs an exit payload containing proof that the burn was included in the checkpointed Polygon block. For ERC-20 assets on the PoS route, the exit calls exit() on Ethereum’s RootChainManager. That contract verifies the proof and releases the mapped asset from the bridge. The portal may prepare this call for the wallet, but it still needs to be submitted and confirmed on Ethereum.

Is the Ethereum exit still waiting on your wallet?

After the checkpoint, look for an action-required or exit step in the bridge history. If the portal offers a confirm or exit action, review the transaction details and submit it from the wallet that controls the transfer. The exit uses Ethereum gas, so the wallet needs enough ETH there. A checkpointed burn alone does not broadcast this second transaction or pay its gas fee.

If you already submitted the exit, inspect its Ethereum transaction hash. A pending transaction can be delayed by low gas pricing or Ethereum congestion; a dropped or replaced transaction may leave the bridge interface showing an incomplete withdrawal. Check the wallet’s transaction queue and nonce history. If the transaction failed or was dropped, use the portal’s retry or exit flow for that existing withdrawal. Do not initiate another burn to fix a missing Ethereum exit.

A bridge page can also lag behind the chain. If the source burn and Ethereum exit are confirmed on their respective explorers but the portal still shows “pending,” the discrepancy may be in the interface or its transaction indexer. Compare the on-chain records before treating a stale status label as a failed transfer. If there is no confirmed exit transaction, the bridge may still need the wallet action even when its display suggests that the transfer is nearly complete.

• No successful Polygon burn: resolve the source transaction before expecting an exit.
• Burn confirmed, block not checkpointed: wait for the validator checkpoint.
• Checkpoint available, no Ethereum exit: submit the exit transaction and provide Ethereum gas.
• Exit submitted but unresolved: inspect its Ethereum status and the wallet’s queued transactions.

Once the burn is initiated, Polygon Support says it cannot be cancelled or reverted; the pending withdrawal can be completed later. The practical rule is to act on the stage that is actually missing: verify the burn, wait for its checkpoint, or complete the Ethereum exit.