Polygon Bridge: Four Checks Before Moving Tokens

Polygon Bridge moves assets between Ethereum and Polygon PoS by locking tokens on the source chain and minting mapped tokens on Polygon, then burning those tokens to unlock the originals on return. The route matters: a deposit is not the same process as a withdrawal, and Polygon PoS is a different network from Polygon zkEVM. Before confirming a transfer, check four things: the networks, the token contract, the recipient and the exit steps. The Polygon Bridge reference belongs in that route check, alongside the transaction details shown by your wallet.

Which Polygon network and bridge route are you using?

Start by identifying the source and destination networks and the bridge path selected for the transfer. A wallet showing “Polygon” does not establish that a token is on Polygon PoS; Polygon zkEVM and other networks have separate bridge contracts and transfer flows. A transaction sent through one system cannot be assumed to complete on another.

For the PoS bridge, the Ethereum-to-Polygon path uses the RootChainManager contract. For a mapped ERC-20, the manager checks that the token is mapped, then calls its registered predicate to lock the source tokens. It sends a state-sync message so the corresponding child-chain token can be credited on Polygon. In the reverse direction, the child token is burned; the Ethereum-side exit later releases the locked tokens.

Make sure the bridge’s displayed route matches the networks in your wallet, and that you are signing on the chain the transfer starts from. If the asset is on zkEVM or another network, use the bridge path for that network rather than assuming the PoS flow applies.

Does the token contract match on both chains?

Check the token contract address on the source chain and confirm the destination asset is the mapped representation of that same asset. Tickers and logos are labels, not proof of identity: unrelated tokens can share a symbol, and a bridged token may have a different contract address from its Ethereum counterpart.

In the PoS bridge, the RootChainManager’s mapping links a root token to a child token and a token type. The token predicate handles the asset-specific lock and exit operations. A token that is not mapped cannot use that route; an asset shown with a familiar name may still be the wrong contract. Compare addresses using a trusted record for the asset and network, and confirm the destination wallet supports the token contract that will arrive.

Also check whether the interface is offering the route you intend. The standard PoS route uses lock-and-mint on deposit and burn-and-unlock on withdrawal. Those steps preserve the link to the original asset, but they do not make every token with the same symbol interchangeable.

Who receives the tokens, and what will the transfer cost?

Confirm the recipient address and the amount on the destination side before signing. Some flows let the sender specify a different recipient; if so, verify every character of that address and check that it is controlled by the intended wallet or service on the destination network. A correct source transaction sent to the wrong destination address may not be recoverable.

Review the fee asset and transaction details on both chains. The source transaction needs enough native gas token for execution, and a later withdrawal exit requires a transaction on Ethereum. The amount displayed as arriving can differ from the amount sent if the route applies fees or token-specific handling. Check the actual quoted amount and network fee in the confirmation screen; do not infer them from a token’s ticker or from a previous transfer.

• Source and destination network names match the route you selected.
• The source token contract is the intended asset and the destination representation is mapped.
• The recipient is correct for the destination chain.
• The displayed arrival amount and required gas fees are acceptable.

What happens when you withdraw from Polygon PoS?

A PoS withdrawal is a two-step exit: burn on Polygon, then prove that burn to the RootChainManager on Ethereum. The burn transaction must be included in a Polygon block that validators have checkpointed on Ethereum. The exit call supplies a receipt proof and block-in-checkpoint proof; the manager verifies the checkpoint inclusion and passes the relevant log to the token predicate, which releases the asset.

This means a successful burn is not the same as completed delivery on Ethereum. The checkpoint is a protocol step, and the exit transaction is a separate Ethereum transaction with its own gas cost. Before starting, be prepared to wait for the checkpoint and to submit the exit. Polygon’s support material says a started withdrawal cannot be cancelled; once the tokens are burned, completing the exit is the remaining path to release them.

For most users, the better choice is to confirm the route and token contract first, then treat the quoted arrival amount and the full exit process as part of the transfer decision. A bridge transaction changes where an asset is represented and which contract controls the next step. Reading those details before signing is what makes the transfer predictable.