Why a Polygon PoS Withdrawal Can Stay Pending

A Polygon PoS withdrawal can stay pending because burning tokens on Polygon is only the first of two steps. The burn removes the bridged tokens from circulation on Polygon; it does not yet release the corresponding tokens held on Ethereum.

The bridge must first establish that the burn happened. Polygon validators group blocks into a checkpoint and submit it to Ethereum. After Ethereum records that checkpoint, a proof can show that the withdrawal transaction belongs to one of the included blocks. For a broader map of bridge designs, the guide to Polygon Bridge explains how this checkpoint route fits among other transfer paths.

What does “pending” mean after a Polygon withdrawal?

It usually means the burn is recorded on Polygon but the checkpoint and Ethereum claim have not both finished. The bridge flow has three moving parts: the Polygon burn transaction, the checkpoint on Ethereum, and the exit transaction that releases the locked tokens. A status label may cover more than one of these stages, so check the transaction details before deciding what is delayed.

Think of the checkpoint as a signed receipt for a set of Polygon blocks. Until that receipt is available on Ethereum, the bridge contract cannot verify the burn there. Once it is, the withdrawal proof connects the burn transaction to the checkpoint, and the Ethereum contract can process the exit.

Why does the checkpoint take time?

Because a Polygon block is not itself proof that Ethereum has accepted the withdrawal. Validators must submit a checkpoint covering the block that contains the burn, and Ethereum must process that submission. If the burn is recent, it may simply be waiting for the relevant block range to be checkpointed.

The checkpoint stage depends on activity across the network, including validator and Ethereum transactions. That is separate from the speed of the Polygon burn itself. A fast confirmation on Polygon does not skip the Ethereum checkpoint step.

What happens after the checkpoint?

After the checkpoint is recorded, the bridge can generate an inclusion proof for the burn. The withdrawal is completed when an exit transaction submits that proof to the Ethereum bridge contract and the contract releases the tokens. That final transaction needs an Ethereum wallet signature and enough ETH to pay its network fee.

So “checkpoint complete” does not always mean “funds received.” It can mean the proof is ready and the exit transaction still needs to be sent, or that the exit has been submitted and is awaiting Ethereum confirmation.

What should you check before acting?

Use the transaction hash to identify the stage, then act on that stage only:

• If the Polygon burn is not confirmed, check its status on Polygon.
• If the burn is confirmed but no checkpoint is recorded, the withdrawal is waiting for the checkpoint.
• If the checkpoint is recorded, look for the proof or exit action in the bridge interface.
• If an Ethereum exit transaction was sent, check that transaction on Ethereum and confirm whether it succeeded.

Do not start another withdrawal just because the first one is waiting. A confirmed burn is already part of the bridge process; repeating it can burn more tokens without speeding up the checkpoint. The practical distinction is simple: a Polygon confirmation proves the burn, while an Ethereum exit completes the withdrawal.