What a Bridge Withdrawal Claim Does, Step by Step

A bridge withdrawal claim is a transaction on the destination chain that proves a withdrawal began on the source chain and asks the bridge to release the corresponding asset. For a typical token withdrawal from Polygon PoS to Ethereum, the sequence is burn, checkpoint, proof, claim. The first transaction removes the bridged tokens from Polygon; it does not, by itself, put tokens in the user’s Ethereum wallet.

That distinction matters because a bridge connects two separate ledgers. The Polygon Bridge’s movement of tokens between Ethereum and Polygon depends on contracts recording the transfer on both networks. A withdrawal claim is the step that lets Ethereum’s bridge contracts verify the Polygon-side event and release the matching asset.

What happens when a bridge withdrawal starts?

A withdrawal starts when the user submits a transaction on Polygon to burn the bridge’s mapped version of a token. The wallet pays the Polygon network fee, usually in POL. The burn transaction records which token and amount left circulation, along with the destination address used for the return.

The original asset is held by bridge contracts on Ethereum during this process. Burning its Polygon representation is the bridge’s way of preventing the same value from remaining spendable on both networks. It is similar to handing in a claim ticket before collecting an item: the ticket is retired so it cannot be used twice.

At this point, the withdrawal is initiated but not finished. The burn has to become part of a Polygon block, and that block has to be covered by a checkpoint recorded on Ethereum. Until then, Ethereum’s contracts have no confirmed record they can use to validate the withdrawal.

What does the checkpoint prove?

A checkpoint commits to a range of Polygon blocks by recording a cryptographic root on Ethereum. Polygon validators submit these checkpoints, and the root acts like a compact contents page: it lets a contract check whether a particular transaction belongs to the covered blocks without storing every transaction on Ethereum.

Once the burn’s block is included, a proof can be assembled from the withdrawal transaction and the checkpoint data. The proof shows that the burn event is part of the committed Polygon history. The bridge’s Ethereum contracts check that proof and confirm the withdrawal has not already been claimed.

The checkpoint and the claim do different jobs. A checkpoint makes the burn verifiable from Ethereum; it does not automatically send the released asset to the user. The claim transaction submits the proof to the destination-chain contract and requests the release.

How do you complete and check a claim?

After the checkpoint covers the burn, the bridge interface can prepare the withdrawal proof and offer a claim action. The user switches to Ethereum and signs a separate transaction. The Ethereum wallet needs ETH to pay that network’s fee. If the proof is valid and unused, the bridge contract releases the corresponding asset to the specified address.

• Keep the burn transaction hash; it identifies the Polygon-side withdrawal.
• Check the transaction’s status in the bridge interface and wait until the burn is checkpointed.
• Confirm the destination network, token, amount and recipient before signing the Ethereum claim.
• Check the claim transaction on Ethereum to confirm the asset arrived.

If the claim is not yet available, the usual missing step is checkpoint inclusion, so submitting another burn can create a separate withdrawal rather than advance the first one. Use the transaction hash to follow the existing transfer, and make sure the claim page and wallet show the intended networks before signing.

The key change is that the Polygon representation has been burned and, after a valid claim, the matching asset is released on Ethereum. What to watch next is the status of the burn’s checkpoint and then the Ethereum claim transaction: both steps must complete for the withdrawal to reach its destination.