Adding a Bridged Token Shows Its Destination-Chain Balance

Adding a bridged token to a wallet usually makes a token contract’s balance visible on the destination network; it does not perform the bridge transfer. The token is a representation issued or released there under the bridge’s rules, while the original asset remains on—or is handled by—the source network.

What does adding a token to a wallet do?

Adding a token tells the wallet which contract to read so it can display the balance and, if supported, prepare transactions. MetaMask’s guidance, for example, says users can import a custom token by entering its contract address on the relevant network. The import changes the wallet display; only a transaction on the blockchain changes ownership or moves funds.

A bridged token can have a different contract address and token name from the asset it represents. For the wider sequence of bridging and swapping, see Biswap’s guide to bridging and swapping crypto. The bridge transfer itself must complete before there is a destination-chain balance to display.

How does a bridge create the destination token?

Bridges use different designs, but a common model locks the original tokens on the source chain and mints a corresponding representation on the destination chain. Ethereum.org describes bridged assets as versions that exist on another network, not the original asset itself. Some systems instead rely on liquidity or other bridge-specific mechanisms, so the token’s redemption path depends on the bridge.

That difference matters when sending the token back. In a lock-and-mint model, the bridge may burn the representation and release the original asset after verifying the transfer. A token with the same ticker or logo can follow a different bridge’s rules and may not be interchangeable.

How can you check and use a bridged token?

Start by selecting the network where the token arrived, then compare its contract address with the bridge’s destination details. A wallet can show a token entry without establishing that it is the expected asset or that an exchange or application supports it.

• Confirm the destination network and token contract from the bridge transaction or its official interface.
• Check that the transfer completed and that the wallet address matches the recipient address.
• Keep the destination network’s native gas token available for transactions.
• Before sending back, confirm which bridge and route can redeem or transfer that representation.

Adding the correct contract is useful for viewing and handling the balance, but it does not make every bridged token liquid or redeemable through every service. The bridge’s supported route determines the next step: use the token on that network, swap it where supported, or send it through a compatible return route.