Four Checks Before a Polygon PoS Withdrawal

A Polygon PoS withdrawal takes two transactions: one burns the token on Polygon, and a later claim releases the corresponding asset on Ethereum. Between them, validators must include the burn in a checkpoint submitted to Ethereum. Before you start, check the route, token, amount and wallet you will use to claim.

What happens during a Polygon PoS withdrawal?

The first transaction calls the bridge on Polygon and burns the bridged token there. The burn creates an event that records the withdrawal. A validator checkpoint then commits Polygon transaction data to Ethereum. After that checkpoint is available, the bridge can verify evidence of the burn and release the corresponding token on Ethereum.

That middle step is why the withdrawal is not an instant transfer. Think of the checkpoint as a receipt that Ethereum can verify: the claim needs proof that the burn happened on Polygon. The Polygon Bridge’s lock, mint and claim steps explain the wider bridge flow; here, the key detail is that withdrawal burns on Polygon before the Ethereum claim.

The two transactions also happen on different networks. The burn uses Polygon’s transaction fee. The claim uses Ethereum’s, so the wallet needs the relevant gas token on each network at the time it signs.

Which route and token should you check?

Confirm that the interface says Polygon PoS as the source and Ethereum as the destination. Polygon has more than one bridge route, and steps for one route may not apply to another. A similar-looking token name is not enough to identify the asset: check the token and route shown in the withdrawal details.

This matters because bridged assets represent tokens held or accounted for through a particular bridge. Withdrawing through the matching PoS route lets the bridge process its own burn record and release the corresponding asset on Ethereum. If the route or token shown is unexpected, stop and resolve that mismatch before signing.

What should you verify before signing the burn?

Read the transaction preview and check the amount, token, source network and fee. Make sure the connected wallet is the one holding the Polygon asset. A wallet prompt can look familiar while still asking you to act on the wrong network or approve a different transaction.

Then check where the claim will go and which wallet can complete it. Confirm the Ethereum account shown in the bridge flow, and make sure you can access it after the Polygon transaction. The claim is a separate Ethereum transaction, so plan for its fee as well as the initial Polygon fee.

• Verify the source and destination networks.
• Match the token to the intended bridge route.
• Check the amount and fee in the wallet preview.
• Confirm access to the Ethereum wallet and funds for the later claim.

What happens after the Polygon transaction?

Save the Polygon burn transaction hash. The bridge uses it to track the withdrawal and determine when the burn is covered by a checkpoint. Once the checkpoint is available, return to the bridge flow, connect the Ethereum wallet and submit the claim. The claim is what releases the asset on Ethereum; the burn alone does not complete the withdrawal.

There can be a wait between those steps while the checkpoint is submitted and recognized. Keep the transaction record and check the bridge’s status before retrying or starting another withdrawal. If the claim is ready, verify its Ethereum transaction details before signing.

The practical rule is simple: treat the burn and claim as two planned actions. Check the route, token, amount and wallet before the burn, then keep the transaction hash and Ethereum gas ready for the claim.