Why a Polygon withdrawal waits for a checkpoint
A Polygon PoS withdrawal waits for validators to record its burn block on Ethereum; once that checkpoint lands, you still need to complete the exit.
By The Token Trail Desk3 min read

A Polygon PoS withdrawal waits for a checkpoint because Ethereum needs proof that the withdrawal’s burn happened on Polygon. The checkpoint records a batch of Polygon blocks on Ethereum. Until the block containing your burn is included, the bridge cannot prepare the proof needed to release your tokens.
What does a checkpoint do?
A checkpoint is a record of Polygon blocks that validators submit to Ethereum. It lets the Ethereum bridge verify that a withdrawal really happened on Polygon, rather than relying on the bridge website’s status alone. A burn removes the bridged tokens from circulation on Polygon so the original tokens can be unlocked on Ethereum.
This extra step is part of the security trade-off in the Polygon PoS bridge: withdrawing to Ethereum takes longer because Ethereum must verify Polygon’s record. The guide to choosing a route after a stalled Polygon Bridge transfer covers the wider route choice. Here, the key detail is that a confirmed burn and a completed withdrawal are separate steps.
How long should I wait for the checkpoint?
There is no exact countdown. Validators submit checkpoints periodically, and timing can vary. The checkpoint has to cover the specific Polygon block that contains your burn; a newer checkpoint that covers earlier blocks will not be enough. A delay of several minutes or longer can happen, but a long wait by itself does not show that the tokens are lost.
Check the burn transaction on a Polygon block explorer. If it is confirmed, note its block number and compare the bridge status with the checkpoint status. If the bridge still says it is waiting, the required block may not yet be covered, or the site may not have refreshed. Avoid starting a second withdrawal while the first burn is confirmed.
What happens after the checkpoint?
Once a checkpoint covers the burn block, the bridge can create a cryptographic inclusion proof—a compact way to show the burn is part of the recorded blocks. You then submit the exit on Ethereum. In many cases, the wallet must confirm that transaction, and it needs enough ETH on Ethereum to pay the network fee.
So “checkpointed” does not always mean “paid out.” It means the proof can now be made and the Ethereum exit can proceed. Check whether the bridge shows an action to continue or claim. If it does, confirm the destination address and the network before signing.
What should I check if it is still waiting?
Start with the on-chain transaction, then check whether the bridge has caught up with it. These checks help separate a pending checkpoint from a failed withdrawal:
- Confirm the burn transaction succeeded on Polygon and record its block number.
- Check that the bridge is set to the Polygon PoS withdrawal route and the intended Ethereum destination.
- Wait for a checkpoint that covers the burn block, then refresh the bridge and look for the exit step.
- After the checkpoint, make sure your wallet can pay Ethereum’s transaction fee before submitting the exit.
If the burn failed, the withdrawal did not enter the checkpoint stage. If it succeeded but is not yet checkpointed, wait and recheck the same transaction. If the block is checkpointed but the bridge offers no way to continue, use the bridge’s official support channel and share the transaction hash, never your recovery phrase.