Skip to content
Crypto Record

Crypto news across every chain

2026-10-03 03:52 UTCe2c001

Why a Polygon PoS Withdrawal Waits for a Checkpoint

A Polygon PoS withdrawal waits for a validator checkpoint, then an Ethereum claim; estimate the delay by tracking both stages and keeping gas ready.

Crypto Record Editorial2 min read

Why a Polygon PoS Withdrawal Waits for a Checkpoint

A Polygon PoS withdrawal to Ethereum has two stages: the burn on Polygon must be checkpointed on Ethereum, then you must submit a claim there. The first wait is mostly about when your burn enters a checkpoint; the second depends on Ethereum confirmation and when you send the claim. That distinction gives you a practical way to estimate the wait.

What happens during a Polygon PoS withdrawal?

First, the bridge burns the token on Polygon. Validators then submit a checkpoint to Ethereum, committing to a range of Polygon blocks. Once that checkpoint includes the block containing your burn, the bridge can produce a proof that your transaction happened on Polygon. You submit that proof in a separate Ethereum transaction, which releases the corresponding asset.

The checkpoint is like a dated page in a ledger: your burn must appear on a page Ethereum has received before the bridge can verify it. For a fuller walkthrough of the Polygon Bridge transfer steps, see the linked guide. The key detail for estimating time is that the burn confirmation starts the process; it does not mean the asset has arrived on Ethereum.

How can you estimate the withdrawal wait?

Start the clock when the burn transaction is confirmed on Polygon. Then check whether the bridge marks the withdrawal as checkpointed or ready to claim. Checkpoints are submitted periodically, often described as roughly half-hourly, but that is a cadence, not a promise that your transfer will finish within half an hour. Your burn may just miss a checkpoint, and delays in submitting or processing checkpoints can extend the wait.

After the checkpoint arrives, include time for the proof to become available and for your Ethereum claim transaction to be confirmed. For planning, allow roughly one to three hours in ordinary conditions, with room for longer waits if checkpoint processing or either network is congested. Treat that as a working range, not a service guarantee. A busy Ethereum block or a claim sent with a low fee can add time after the checkpoint has already landed.

What should you check while you wait?

Use the burn transaction hash to follow progress. Check the Polygon transaction first; then look for the checkpoint and claim stage in the bridge interface or transaction history. These stages help distinguish a transfer that is still waiting for a checkpoint from one that is ready for your Ethereum transaction.

  • Burn not confirmed: The withdrawal has not entered the checkpoint wait yet.
  • Burn confirmed, no checkpoint: The bridge is waiting for a checkpoint that includes the burn’s block.
  • Checkpoint received, claim pending: The next step is the Ethereum claim; confirmation depends on Ethereum and the fee you submit.
  • Claim confirmed: Check the receiving wallet on Ethereum for the released asset.

Before initiating a withdrawal, keep POL available for the Polygon transaction and ETH for the Ethereum claim. The second fee is easy to overlook because it comes after the waiting period. If your status has not changed for much longer than the usual planning range, check the transaction hash and bridge status before trying another withdrawal. In short, estimate the wait by tracking checkpoint arrival separately from the final claim; the checkpoint controls most of the uncertainty, while the claim is a transaction you still need to complete.