kendra-koepp

Bridged Tokens Not Showing in Wallet After Transfer: Find Them

Bridged tokens usually arrived; your wallet has not listed them. For a cBridge transfer, confirm the balance at the destination token contract and import that contract into the wallet. A pending transfer needs more time or investigation, while a refunded transfer leaves funds claimable on the source chain.

  • Delivered: Find the destination token contract and query the recipient’s balance.
  • Pending: Use the source transaction hash to find the transfer status.
  • Refunded: Look for the refund on the source chain.

Keep three inputs together: the source transaction hash, destination chain ID and recipient address. The cBridge site lets you look up the source transaction and see whether the transfer has a separate destination delivery transaction. For a delivered transfer, record that delivery transaction hash and the destination token contract address.

Trace the Transfer on Both Chains

A delivered transfer has a destination transaction separate from its source deposit. Open the delivery transaction on the destination chain’s explorer and identify the token contract and recipient in its token transfer or mint event. Use that contract address, not a token symbol, for the balance check.

Call balanceOf(recipient) on the destination token contract through that chain’s RPC, using the recipient address from the transfer. A positive result at the latest block confirms that the contract holds tokens for that address. The call returns an integer in the token’s smallest units; read decimals() from the same contract if you need a human-readable amount. This contract balance is the ground truth for whether those tokens are there. Wallet displays and indexer APIs rely on token lists or indexing, so a new token can be omitted or appear late.

When the balance is positive but MetaMask shows nothing, select the destination network and import a custom token using that contract address. Confirm the address against the destination transaction before importing it. A wallet connected to Polygon will not display a balance held on BNB Chain.

An xAsset transfer can mint a pegged token at its own contract address on the destination chain. Say you expected the source token’s familiar contract after bridging to Polygon: querying that address may return zero while balanceOf(recipient) at the pegged xAsset contract is positive. Import the pegged contract. The balance check still decides whether the recipient received that token; only the contract address used in the call changes.

If no destination delivery transaction exists, look up the source hash in cBridge transfer history. A pending status means the destination transfer has not completed; keep the source hash and watch for a delivery or refund status. A refunded status means the funds are on, or claimable through, the source chain. Inspect the source-chain refund transaction or claim action before expecting a destination balance.

When the reported status and on-chain results disagree, compare the destination chain ID, recipient, token contract and delivery transaction logs. A delivered transaction to another recipient puts the balance at that address. A failed destination transaction or a zero balance at the contract identified by its logs needs investigation using both transaction hashes and the transfer record.

How to Add a Custom Token to MetaMask?

Select the destination network, choose the custom-token import option and enter the contract address from the delivery transaction. MetaMask can then display the recipient’s balance for that token.

cBridge Transfer Stuck Pending?

Find the transfer using its source transaction hash and inspect its latest status. A pending record calls for monitoring the destination transaction; a refund record directs you to the source chain to locate or claim the funds.