Why Polygon withdrawal claims appear after the burn

A Polygon PoS withdrawal burns the bridged tokens on Polygon before Ethereum can release the originals, so the claim appears only after validators record that burn in a checkpoint and a proof is ready. The burn and the claim are separate steps on separate networks. Seeing the first transaction succeed does not mean the second is ready.

What happens when a Polygon withdrawal starts?

The wallet first sends a withdrawal transaction to a Polygon contract. For a bridged token, that transaction burns the Polygon-side representation. The burn is recorded in a Polygon block, but Ethereum’s contracts cannot act on that block just because it exists: they need evidence that the block and its transaction are part of Polygon’s history.

That evidence arrives through a checkpoint. Polygon validators submit checkpoints to Ethereum, committing to a range of Polygon blocks. A checkpoint is like a dated page in a shared ledger: it lets the Ethereum bridge check whether a particular burn was included. For more on the token flow and the roles of the contracts, see this fuller explanation of how the Polygon Bridge moves tokens between networks.

Why does the claim button take time to appear?

The claim cannot be prepared until a checkpoint covering the burn block has been accepted on Ethereum. A burn near the start of a checkpoint’s block range may become provable sooner than one just after the previous range closed. Validator processing, Ethereum transaction confirmation, and the service that builds the withdrawal proof also add steps. The bridge interface may show the claim only after it has detected the checkpoint and obtained the proof.

These are distinct stages, so a delay does not by itself mean the burn failed. The burn transaction confirms on Polygon; later, the checkpoint anchors its block on Ethereum; then a proof ties the burn to that checkpoint. Only with that proof can the Ethereum bridge verify the withdrawal and make the claim available. There is no single timer that starts at the burn and guarantees when the button will appear.

What does the claim do?

Once the proof is ready, the wallet submits a second transaction on Ethereum. The bridge contract checks the proof, verifies that the withdrawal has not already been claimed, and releases the corresponding asset. That transaction needs an Ethereum network fee. Until it confirms, the withdrawal is not complete, even if the interface already says “claim” or “action required.”

The sequence is easiest to track as three separate records:

• Burn: the Polygon transaction destroys the bridged token.
• Checkpoint and proof: validators commit the relevant block to Ethereum, and proof data shows the burn’s inclusion.
• Claim: a user transaction asks the Ethereum contract to release the asset.

What should you check if a claim is delayed?

Start with the Polygon transaction status. If the burn did not confirm, there is no completed withdrawal to claim. If it did, check whether the checkpoint covering its block has arrived and whether the bridge’s transaction page now offers the Ethereum claim. Keep the burn transaction hash; it identifies the withdrawal if the interface needs to refresh or locate it again.

Before initiating a withdrawal, account for the two fees: one on Polygon to burn the token and another on Ethereum to claim it. Once the burn is confirmed, the Polygon-side tokens cannot simply be returned by cancelling the transaction. The useful distinction is between burned, provable, and claimed: each is a different state, and only the last means the asset has reached Ethereum.