Skip to content
Onchain Daily

Protocol-level crypto news, daily

Polygon bridge delays: How each transfer stage works

Why is my Polygon bridge stuck? Most delays are an unconfirmed Ethereum transaction, a pending state sync or checkpoint, or an exit claim still waiting on you.

Onchain Daily Newsroom4 min read

Polygon bridge delays: How each transfer stage works

Find the transaction hash on Etherscan or Polygonscan first, because a Polygon bridge transfer can advance only after its current chain stage completes; most apparent stalls are an unconfirmed Ethereum transaction, a pending state sync or checkpoint, or an exit claim you still need to send.

The Polygon PoS bridge moves supported assets between Ethereum and Polygon. The Polygon bridge is the service used for that route, and each direction completes in stages on the two chains.

Why is my Polygon bridge transfer stuck?

For a deposit, first look for an Ethereum transaction that has not confirmed. The bridge cannot begin the next stage until Ethereum records the deposit transaction. A low transaction fee can leave it pending while the network processes transactions offering higher fees.

Open the transaction hash on Etherscan and check its status. If it is still pending, you can wait or use your wallet’s speed-up option to submit a replacement with a higher fee. That replacement must use the same transaction in your wallet; sending a second deposit can create a separate transfer rather than move the first one along.

Once the Ethereum transaction is confirmed, the deposit may still be waiting for state sync to Polygon PoS. State sync is the relay of the confirmed Ethereum event to Polygon. The destination-side credit depends on that relay completing, so an Ethereum confirmation alone does not mean the tokens are ready on Polygon.

Use the original transaction hash to follow the deposit. If Etherscan shows confirmation but Polygonscan has no corresponding completed Polygon-side activity yet, the transfer is likely between those stages. Give the relay time to complete, then look up the transaction again on Polygonscan. Avoid starting another deposit just because the destination wallet has not updated.

For a withdrawal, the first Polygon-side step is the burn: the tokens are burned on Polygon as the withdrawal begins. The exit then waits for a checkpoint on Ethereum. A checkpoint records Polygon activity so the withdrawal can be proven and claimed on Ethereum. These waits typically run from under an hour to a few hours.

Look up the withdrawal hash on Polygonscan. A completed burn with no available exit claim means the checkpoint stage is still pending. Wait for the checkpoint, then reopen Polygon Portal with the same wallet and check the withdrawal again. The checkpoint is a dependency: the claim relies on it to prove the burn on Ethereum. You can recognise readiness when Portal makes the exit claim available.

After the checkpoint, the claim is a separate Ethereum transaction that you must sign and pay for in ETH. Portal does not send that transaction automatically. This is why many “stuck” withdrawals are already past the burn and checkpoint stages: the remaining action belongs to the user.

Say your withdrawal has reached the claim stage, but the wallet you used has no ETH on Ethereum. The checkpoint is complete, but you cannot submit the claim until that wallet has ETH for gas. Changing that one detail changes what blocks completion; the diagnosis still holds: the burn is finished, and the outstanding step is the user’s Ethereum claim.

Once you send the claim, track its hash on Etherscan. A pending claim is an Ethereum transaction, so use the wallet’s speed-up option if it remains pending and you choose to raise its fee. If the claim confirms but the wallet balance looks unchanged, check that you are viewing the receiving network and the correct token.

Related questions

How to speed up a pending Ethereum transaction

Use the wallet that submitted the transaction and select its speed-up or replacement option. The replacement raises the fee for the pending transaction; it does not bypass the bridge’s later state-sync, checkpoint, or claim stages. Confirm the replacement on Etherscan before treating that stage as complete.

How to check a Polygon bridge transfer status

Use the hash for the stage you are checking: Etherscan shows Ethereum transactions, while Polygonscan shows Polygon activity. For a deposit, look for Ethereum confirmation followed by Polygon-side activity. For a withdrawal, look for the Polygon burn, then the checkpoint and Ethereum claim. This sequence tells you which action, if any, remains.

What to do if bridged tokens don't show in the wallet

First confirm the transfer reached its destination stage on the relevant explorer. Then check that the wallet is set to the receiving network and that you are viewing the right asset. A confirmed source transaction with no destination-side completion points to a pending bridge stage; a completed transfer with no visible balance calls for checking the network and token display.