Why a bridged token has a different address

A bridged token has a different address because it is a separate contract on the destination blockchain. The bridge links that contract to the original asset and controls how tokens move between the two chains.

For example, Polygon’s mapped-token list gives PoS-USDC one address on Ethereum and another on Polygon. The ticker and name may look familiar, but a token address only identifies a contract on a particular chain. A guide to Polygon Bridge routes for treasury transfers covers route choices in more detail.

What happens to the original token?

In Polygon’s PoS bridge, the token sent from Ethereum is locked, and the bridge mints a corresponding amount on Polygon. This destination version is often called a mapped token: a token contract associated with the source token through the bridge.

When the tokens return, the Polygon version is burned, meaning it is removed from circulation, and the original tokens are unlocked on Ethereum. That link between locking and minting is what lets the two contracts represent related balances without sharing one address.

Other bridges can use different designs. Some move tokens through pools of available funds instead of locking each deposit and minting a matching token. So “bridged token” describes an outcome, not one universal mechanism.

Why can’t one address work on both chains?

A contract lives on the blockchain where it was deployed. Ethereum and Polygon keep separate records of contracts and balances, so the same address can refer to different code or tokens on each chain. A token’s name and ticker are labels; they do not prove that two contracts are linked.

Your wallet address may be the same on both chains, but that does not make the token contracts the same. Think of it as one account with separate balances in two systems: each system needs its own record for the asset.

How can you check a bridged token?

Check the chain and contract address together. For a Polygon PoS transfer, compare the source and destination addresses against Polygon’s mapped-token reference or the bridge’s own verified details. Check the route too, because another bridge may issue a different destination token for the same asset.

• Confirm the wallet is showing the intended chain.
• Match the token’s contract address, not just its name or ticker.
• Check which bridge created the destination token and how it can be redeemed.

A different address is expected when the destination chain uses its own mapped contract. The useful question is whether that contract is the one linked to the asset and bridge route you intended to use.