Skip to content
ChainBrief

News from across Web3

How to Add a Bridged Token to MetaMask by Contract

To add a custom token in MetaMask, paste its contract address instead of searching. Find the received token on the destination explorer and verify the balance.

The ChainBrief Editors

How to Add a Bridged Token to MetaMask by Contract

Add a bridged token to MetaMask by pasting its contract address on the destination network, rather than choosing a search result: bridged tokens can share a symbol with other contracts on that chain.

The contract identifies the token you received, so importing by address helps you see the right balance.

Why use the contract address?

MetaMask imports tokens separately for each network. A search by symbol can return a different contract, including another version of a token or a fake with the same name. The symbol alone does not establish that the result is the asset delivered to your wallet.

For a cBridge transfer, the destination network is where you need to find the received token’s contract. The cbridge supported chains helps identify which destination network to select before importing the token.

Use the delivery transaction as your source. Its token-transfer line records the contract involved in the transfer, so copying the address there ties the import to the asset shown as received. On a destination explorer such as BscScan or Arbiscan, open that transaction and locate the received token’s transfer entry.

Have the delivery transaction hash ready, or use your cBridge history to find the transfer and its transaction. The address you need is the token contract, not your wallet address, the transaction hash, or the token’s ticker symbol.

Import the token in MetaMask

Paste the contract into MetaMask’s custom-token import on the destination network, then compare the wallet balance with the explorer.

  1. Open the delivery transaction on the destination explorer using its transaction hash. Find the token-transfer line for the asset sent to your wallet.
  2. Copy the received token’s contract address from that line. Make sure you have the token contract, rather than the recipient address or a similarly named token elsewhere on the page.
  3. Switch MetaMask to the destination network shown for the delivery transaction. Token imports are network-specific, so the network needs to match the chain where the balance arrived.
  4. Open Import tokens, choose Custom token, and paste the contract address. For a valid contract on the selected network, MetaMask autofills the token symbol and decimals. If the decimals do not autofill, the wallet may be on the wrong network or the address may be wrong; confirm both before continuing.
  5. Confirm the autofilled symbol and decimals, then import the token. The symbol can help you recognize the asset, but the contract address is the identifier to rely on.
  6. Compare the imported balance in MetaMask with the amount shown for your wallet on the destination explorer. When the amounts match, the token is visible in MetaMask as expected.

For an ERC-20 token, use the contract recorded for the received token on its destination chain. If you selected a search result earlier and the balance is missing or unexpected, repeat the import with the address from the delivery transaction. Use that contract address for this token import.