A wallet-to-wallet send on one chain updates balances in one ledger; a cross-chain transfer uses a bridge to lock or burn tokens on one chain and mint or release a corresponding token on another.
- A same-chain send changes balances in one transaction on one chain.
- A bridge coordinates transactions and messages across two chains.
- The destination token has its own contract and depends on the bridge’s backing and verification.
Ethereum.org’s “Introduction to blockchain bridges” describes bridges as connections that carry assets and information between separate blockchain ecosystems. The what a Polygon bridge is connects Ethereum and Polygon PoS, so its transfer has steps beyond an ordinary send.
What happens when you deposit 100 USDC from Ethereum to Polygon PoS?
A Polygon bridge deposit locks the 100 USDC on Ethereum and mints 100 bridged USDC on Polygon PoS. The original tokens stay in an Ethereum contract; the Polygon tokens are a separate representation that can be used on the destination chain.
- Ethereum: RootChainManager routes the deposit to the ERC20Predicate, which holds the deposited tokens.
- Between chains: a state sync relays the deposit information to Polygon PoS.
- Polygon PoS: the mapped child token is minted to the recipient.
Polygon’s PoS bridge documentation describes this predicate lock and child-token mint through state sync. Because Polygon PoS has its own ledger, the bridged USDC has a different contract address there than USDC on Ethereum. A matching name or ticker does not make the two contracts identical.
The child token represents a claim backed by the locked Ethereum tokens. One useful consistency check is whether the ERC20Predicate’s balance of the Ethereum token covers the mapped child token’s total supply on Polygon PoS. Compare the correct token and child-token contracts; a ticker alone is not enough to establish that you are checking the right pair.
This check helps you understand the bridge’s backing at that moment, but it does not remove the bridge’s other risks. The bridge contracts must handle deposits, messages, and withdrawals correctly, and the cross-chain process relies on Polygon’s validators to confirm and relay state. A regular send relies on the security of the one chain it uses; a bridge adds another system to assess.
Why does bridging take longer and cost gas on two chains?
A same-chain transfer updates the sender’s and recipient’s balances in one transaction. It is complete according to that chain’s confirmation and finality rules. A bridge deposit first needs Ethereum confirmations, then the state sync relay must deliver the deposit to Polygon PoS before the child token can be minted.
That cross-chain handoff explains the delay: the Polygon transaction depends on information from an Ethereum transaction, and the chains do not read each other’s state directly. The bridge carries and verifies the message between them. Congestion and the bridge’s confirmation requirements affect how long the handoff takes.
Gas is also paid separately on each chain when you make transactions on both. The deposit costs ETH for Ethereum execution; using the bridged tokens on Polygon PoS costs POL for Polygon transactions. The bridge itself may also charge a fee, depending on the route and service.
Change the deposit from 100 USDC to 80 USDC and, assuming the same route and no other changes, 80 USDC is locked and 80 bridged USDC is minted. The amount changes; the separate ledgers, relay, gas costs, and added bridge trust layer still apply.
Related questions
Can a cross-chain transfer be reversed?
A completed bridge transfer is not undone by reversing one transaction across both chains. To move the value back, you generally make a new transfer in the opposite direction, which has its own steps and costs. A pending or failed transfer may have a recovery path set by that bridge, so check its status and rules before assuming the funds are lost or returned.
Why do I pay gas twice when bridging?
Ethereum and Polygon PoS have separate ledgers and transaction fees. You pay ETH for the Ethereum deposit, then POL for transactions that use the bridged tokens on Polygon PoS. Each fee pays for execution on its own chain.
Is a bridged token the same token?
It represents the same asset value through the bridge’s lock-and-mint arrangement, but it is not the same token contract. The Ethereum USDC remains locked in the predicate while a mapped child token circulates on Polygon PoS. Confirm the destination contract and its backing before treating a token with a familiar name as interchangeable.
When choosing between a regular send and a bridge, check the destination chain and mapped token contract, then decide whether the extra delay, fees, and bridge trust assumptions suit the transfer.