Trace the token on both chains when using the Polygon bridge: an Ethereum-origin ERC-20 is locked on Ethereum and represented by newly minted tokens on Polygon PoS, then burned on Polygon before the locked tokens are released. That sequence keeps the Polygon representation matched one for one with tokens held on Ethereum. The Polygon bridge moves supported assets between Ethereum and Polygon PoS.
How does the Polygon bridge move an Ethereum ERC-20?
The Polygon PoS bridge locks an Ethereum-origin ERC-20 in a predicate contract, then mints its mapped representation on Polygon. A predicate is the Ethereum contract that handles custody and exit rules for a token type. For a standard ERC-20, that contract is ERC20Predicate.
- RootChainManager accepts the deposit and identifies the token’s predicate.
- ERC20Predicate holds the Ethereum tokens.
- StateSender starts a state sync to Polygon.
- ChildChainManager calls the mapped child token to mint the same amount.
These parts form one deposit path. RootChainManager first requires a mapping between the Ethereum token and its Polygon counterpart. It routes the deposit to ERC20Predicate, which transfers the tokens from the depositor into its own balance. RootChainManager then calls StateSender. Heimdall, Polygon’s validator layer, relays the state-sync event; Bor’s state receiver delivers it to ChildChainManager. The child token’s deposit function mints the corresponding balance for the recipient.
Say you deposit 100 units of a mapped Ethereum ERC-20 to use in a Polygon DeFi contract. After the Ethereum transaction, those 100 units sit in ERC20Predicate, even if the Polygon balance has yet to appear. After state sync, you can spend 100 child-token units on Polygon. The Ethereum tokens have changed custody; they have not been burned.
The Ethereum deposit and the Polygon mint are separate events. A confirmed deposit transaction therefore answers where the original tokens are, while the child-token balance answers whether the representation is ready to use. That distinction is useful when a transfer appears stuck between chains. Ethereum gas pays for the deposit and any separate token approval; the time until the Polygon balance appears depends on Ethereum confirmation and state sync.
What changes when the token starts on Polygon?
A token first created on Polygon can reach Ethereum without an earlier Ethereum deposit: MintableERC20Predicate can mint the Ethereum-side token during exit. This reverses the starting condition in the previous case. The token’s origin determines whether an exit needs an existing Ethereum balance to release.
Hold the amount and mapped token pair constant. In the first case, 100 tokens originated on Ethereum, so ERC20Predicate holds 100 after deposit and returns them after a valid exit. In the second case, 100 tokens originated on Polygon. There may be no corresponding Ethereum tokens in custody when those 100 child tokens are burned. For that mapped mintable token, MintableERC20Predicate supplies the missing Ethereum balance by minting it, then transfers it to the withdrawer. Its contract code checks its balance and mints only the shortfall before transfer.
Later, someone can deposit those Ethereum-side tokens back to Polygon. RootChainManager routes that deposit to MintableERC20Predicate, which locks the deposited tokens and starts the state sync for the Polygon credit. A later exit can release tokens already held there. If its balance covers only part of the exit, the predicate mints the remainder. “First exit mints” describes a fresh Polygon-native token with no Ethereum balance locked; the contract’s actual test is whether its balance covers the requested amount.
This is why “every Polygon token is backed by an Ethereum token in a bridge contract” is too broad. It describes an Ethereum-origin token while its Polygon representation circulates. For a Polygon-native token, the Ethereum-side balance may instead be created on exit. To trace custody, identify the mapped token type and predicate before treating a Polygon balance as a claim on locked Ethereum inventory.
When does a Polygon burn release tokens on Ethereum?
A PoS withdrawal releases Ethereum tokens only after the Polygon burn is included in an Ethereum checkpoint and an exit proof is submitted. The child token’s withdrawal function burns the holder’s balance and emits a transfer-to-zero log. Heimdall checkpoints Polygon blocks to Ethereum; a checkpoint is a commitment to those blocks, not a payout. The exit proof shows that the burn log belongs to a checkpointed block.
RootChainManager verifies that proof, rejects an exit already processed, and calls the mapped predicate’s exit function. ERC20Predicate then transfers the proven amount from its Ethereum balance to the withdrawer. A completed Polygon burn can therefore coexist with an unchanged Ethereum wallet balance while the checkpoint or exit transaction is pending. Polygon gas pays for the burn, and Ethereum gas pays for the exit; the wait depends on checkpoint submission and the Ethereum transaction.
The Plasma path also burns on Polygon, but its withdrawal has a seven-day challenge period before release. Its deposit and exit contracts are separate from the PoS RootChainManager path. A PoS burn awaits a checkpoint and proof; a Plasma burn must also pass its challenge period. Knowing which path carried the token explains why two otherwise similar withdrawals can have very different waits.
Related questions
Where are bridged tokens held on Ethereum?
Ethereum-origin ERC-20 tokens deposited through the PoS path are held by the token’s predicate, typically ERC20Predicate, rather than by RootChainManager. RootChainManager routes the deposit and verifies the exit. The predicate holds and releases the tokens.
What happens to an unmapped token sent to the bridge?
RootChainManager rejects a deposit call for an unmapped token before the predicate locks it. A direct ERC-20 transfer to a contract address bypasses that deposit call and creates no state-sync message or Polygon mint. Inspect the token mapping and transaction method when a balance has moved without a matching bridge event.
Is the Plasma bridge still used?
Plasma remains a distinct route for assets assigned to its contracts, including the native-token path in Polygon PoS bridge design. Whether a particular token uses Plasma depends on its mapping and current supported route. Identify that route before estimating when a burned balance can be claimed on Ethereum.
For any transfer, match the token’s origin and mapped predicate to its deposit, burn, checkpoint, and exit events; that tells you where the tokens are and what must happen next.