How to replace an unsupported token in your wallet

To replace an unsupported token in a wallet, first determine whether the wallet merely cannot display it or whether the token’s issuer has launched a replacement. Those are different problems: importing a token changes what the wallet shows, while migration moves value under rules set by the issuer.

Why does my wallet say a token is unsupported?

A token can be missing because the wallet is on the wrong network, does not list the token automatically, or does not support that token standard. Check the network and the token’s contract address in a block explorer; a matching name or ticker alone does not confirm that you have the right asset.

If the token appears on the correct network but the wallet does not list it, adding its contract address may make the balance visible. A swap route can fail for a separate reason, such as a stalled transfer; Biswap’s guide to where a stalled transfer can pause explains that route problem in more detail.

How do I make a missing token appear?

Use the wallet’s custom-token or import function, and select the network where the token contract exists. The token address tells the wallet which contract to read; the wallet may then display the balance associated with your account.

• Confirm the network shown in the wallet matches the token’s network.
• Copy the contract address from a trusted project announcement or the relevant network’s block explorer.
• Paste the address into the wallet’s token-import screen and check the token details before saving.
• Reopen the asset list and confirm the balance; importing a token does not move or exchange it.

If the wallet still cannot read the token, it may not support that network or token standard. A compatible wallet may show the same account on that network, but only use a wallet you trust and follow its official recovery process.

When does replacing the token require a migration?

A migration is needed when the issuer has moved the token to a new contract and provided a process for holders to exchange the old asset. Check the issuer’s official channels for the migration terms, deadline, supported networks and any required transaction; importing the new contract alone will not exchange the old token.

Keep enough of the network’s native asset to pay any transaction fee, and review the destination address and transaction details before signing. If there is no verified migration announcement, treat an unsolicited “replacement” offer as unconfirmed. The next step is to identify whether you need a display fix, network support or an issuer-led exchange.