Polygon bridge: how deposits and withdrawals work
How does Polygon bridge work? Ethereum tokens are locked and matched with Polygon PoS copies; withdrawals burn those copies before an Ethereum claim.
The Chainvane Desk5 min read

The Polygon bridge moves supported assets between Ethereum and Polygon PoS by locking tokens on one chain and creating or releasing the matching amount on the other. A deposit locks tokens on Ethereum before minting copies on Polygon PoS; a withdrawal burns those copies, then releases the originals after a checkpoint and an Ethereum claim.
- Deposit: Approve the token and lock it on Ethereum; the matching Polygon token is minted after the deposit is relayed.
- Withdrawal: Burn the Polygon token, wait for a checkpoint on Ethereum, then submit a separate claim.
- Costs and time: Deposits depend on Ethereum confirmations; withdrawals also wait for a checkpoint. Gas is paid in ETH on Ethereum and POL on Polygon PoS.
The bridge matches an Ethereum token with a Polygon counterpart
The Polygon PoS Bridge connects mapped token pairs, so the asset available on Polygon PoS represents the Ethereum token held by the bridge. “Moving” a token does not send the same token through a shared space between chains. Ethereum and Polygon PoS each track their own state, so bridge contracts and validators coordinate the lock, mint, burn and release.
Polygon Portal is the place the reader encounters in this process: it provides access to the Polygon bridge for moving supported assets between Ethereum and Polygon PoS. The important distinction is which chain holds the original token and which holds its counterpart. A token must have a mapping between the two chains to cross through this bridge.
A deposit locks tokens on Ethereum before a state sync mints copies
A deposit starts with approval, then a lock. The wallet first authorizes the relevant Ethereum contract to use the chosen token. The user then submits the deposit, which locks that token in a predicate contract on Ethereum. Approval and deposit are separate actions because the contract needs permission before it can hold the asset.
After the lock, Heimdall validators run the state sync mechanism that relays the deposit event to Polygon PoS. That event is the link between the Ethereum lock and the Polygon mint: the second chain can act on the deposit because validators relay its confirmed state. Bor produces Polygon PoS blocks, including the block where the child token is minted. The user sees a matching amount on Polygon PoS, while the original remains locked on Ethereum.
The Polygon bridge handles the cross-chain movement by coordinating those two sides. For someone bridging assets to Polygon, the practical sequence is approval, deposit, relay and mint. Ethereum confirmations affect how soon the deposit can be relayed, so the wallet’s transaction confirmation is not the same thing as the Polygon-side mint being complete.
A withdrawal burns on Polygon before a separate Ethereum claim
A withdrawal begins by burning the mapped token on Polygon PoS. Burning removes those copies from circulation there; it does not immediately unlock the Ethereum original. The burn must first be included in a Heimdall checkpoint on Ethereum so the Ethereum-side bridge can verify that the Polygon tokens were destroyed.
Once the relevant checkpoint is on Ethereum, the user makes a second transaction: the exit claim. That claim submits proof of the Polygon burn so the Ethereum contract can release the corresponding locked tokens. The proof matters because Ethereum needs verifiable evidence from Polygon PoS before it changes its own state and releases the original.
This two-transaction withdrawal is the key difference from a deposit. The burn happens on Polygon; the claim happens on Ethereum. The user therefore needs POL for gas on Polygon PoS and ETH for the exit transaction on Ethereum. Completing the burn alone does not complete the withdrawal, and the claim cannot be made until the checkpoint is available.
Timing and gas depend on which chain must act
Deposits take minutes, with the precise wait set by Ethereum confirmations and the state sync that follows. Withdrawals take longer because the burn must be included in a checkpoint on Ethereum before the exit claim can run. The checkpoint interval and the time for the claim transaction to confirm both affect the total wait; there is no single duration that applies to every transfer.
Gas follows the chain where each action occurs. Ethereum approval, deposit and exit transactions require ETH for gas. Polygon PoS actions, including a withdrawal burn, require POL, the network’s gas token after it replaced MATIC in 2024. A user should keep enough of each gas token for the steps their direction of travel requires.
An unmapped token cannot use the same lock-and-mint route
Change one detail: the asset in the wallet has no mapped Polygon counterpart. It cannot follow this bridge’s lock-and-mint route, because there is no paired child token to mint on Polygon PoS. The eligibility changes, but the core explanation still holds for mapped assets: deposits lock the Ethereum original before minting its counterpart, and withdrawals burn the counterpart before releasing the original.
Before starting, confirm that the token is mapped and identify which wallet actions belong to each chain. For a withdrawal, plan for both the Polygon burn and the later Ethereum claim, with POL and ETH available for their respective gas costs.