How Ethereum Deposits Become Polygon Credits

A Polygon PoS deposit locks tokens on Ethereum and creates an equivalent mapped balance on Polygon; unlike an exchange transfer or a liquidity bridge, it depends on a two-chain contract process rather than custody or prefunded funds. That gives users a representation they can spend on Polygon while the original asset remains locked, but the balance on each chain is no longer independently available.

How does a deposit become a Polygon credit?

The deposit begins when a user approves and submits a transaction to the Ethereum-side bridge contract. For an ERC-20 token, the contract’s token-specific handler locks the amount, then sends deposit information to Polygon’s child-chain manager through the network’s state-sync system. Once processed there, the mapped child token is minted to the specified Polygon address.

That minted balance is a claim tied to the locked Ethereum asset, not a second, freely created supply. For a closer look at Polygon Bridge’s deposit and return mechanics, see the fuller account of how the two chains coordinate. The distinction matters when checking balances: the Ethereum token and its Polygon counterpart have separate contract addresses, even when a wallet gives them the same ticker and display name.

The asset must also be mapped for the bridge. Mapping pairs the Ethereum token contract with the Polygon representation and defines how deposits and withdrawals are handled. A token with the right name or symbol is not necessarily the mapped asset; the contract address is the useful identifier.

What does the bridge gain, and what does it cost?

The bridge makes an Ethereum asset usable in Polygon applications without asking a market maker to supply the destination funds. That lock-and-mint design keeps the representation tied to the source asset and avoids swapping it for a different token, but a deposit requires an Ethereum transaction and both sides of the bridge must process it.

Other routes make different bargains. An exchange may credit a Polygon withdrawal from its own inventory, which can feel more direct but puts custody and withdrawal rules in the middle. A liquidity bridge can deliver destination tokens quickly from funds already on Polygon, but the received asset and fees depend on that service’s liquidity and settlement design. The native bridge’s accounting is clearer; its route is less like a simple transfer and depends on Ethereum gas, bridge processing and token support.

• Check that the asset is supported and mapped for the Polygon PoS bridge.
• Confirm the destination network and wallet address before signing.
• Allow for the Ethereum transaction fee as well as Polygon gas for later activity.
• Verify the token contract on Polygon if the wallet does not show the expected balance.

How does a Polygon credit return to Ethereum?

A withdrawal reverses the supply change: the Polygon representation is burned, then the user submits an Ethereum-side exit transaction with proof that the burn was recorded and checkpointed. The source tokens are released only after that proof is accepted. This differs from a deposit, which sends state from Ethereum to Polygon, and it makes the return trip a separate process rather than an instant undo.

For most users, the native bridge is the more legible choice when the goal is to preserve a direct claim on a supported Ethereum token and there is no need for an immediate exit. The practical signals to watch are whether the token is mapped, whether the deposit has completed on Polygon, and whether a withdrawal has reached the checkpoint needed for release on Ethereum.