Which Token Contract Should the Wallet Display?

A token can be present at an address but absent from the wallet’s token list. Adding it manually is a display operation, not a blockchain transaction. The dangerous part is choosing the wrong contract, because unrelated or malicious tokens can use the same name and symbol.

Use the Contract Identity Import Protocol

Do not import by token name alone.

• Correct blockchain network
• Receiving address owns the token on the explorer
• Contract address from an authoritative source
• Contract matches the explorer transfer
• Symbol and decimals load consistently
• Wallet supports the network and token standard
• No approval or website interaction is required merely to display it

First prove that the token exists at your address

Paste the receiving address into the explorer for the network used. Check the token holdings or transfer logs. If no token appears, importing a contract cannot create the missing asset.

Open the exact network before importing

MetaMask supports manual token display on supported EVM networks, Solana and Tron. The same contract field or ticker can represent different assets on different chains, so select the chain first.

Use the contract from the transaction or official project

MetaMask recommends locating token contracts through the relevant explorer or a reputable token listing. Compare the address with the contract recorded in the transfer rather than trusting a search advertisement, comment or direct message.

Token name and symbol are not unique identifiers

Anyone can deploy a contract using a familiar symbol such as USDT. The contract address on one network is the identity that must match the received asset.

Decimals affect display, not ownership

The wallet uses token decimals to format the integer balance. An incorrect value can make the amount look too large or too small. Modern wallets often retrieve this metadata automatically from the contract after the address is entered.

Automatic detection is helpful but not authoritative

MetaMask displays many popular tokens automatically and also offers enhanced detection. Its help centre notes that no centralized list can be complete in a permissionless ecosystem, so a missing token does not prove that the asset is invalid.

Importing should not require a transaction

Adding a token to the interface should not request gas, a signature, token approval or a website connection. Those actions involve blockchain permissions and are unrelated to showing an existing balance.

A token can display without having market value

The wallet may show a quantity but no fiat price. Price feeds and liquidity are separate from the contract balance. Do not treat an arbitrary displayed dollar value as proof that the token can be sold.

Unsolicited tokens require extra caution

Random tokens can contain promotional names or direct users to malicious websites. Hiding them is safer than visiting a linked site, approving a contract or paying gas to remove them.

Use a Contract Source Record

Save the network, transaction hash, contract address, official project source, explorer page and date checked. This prevents the same symbol from being imported from another network later.

Import through the wallet’s own token controls

In MetaMask, use Manage tokens or Add custom token, paste the verified contract, review the detected details and confirm display. Avoid third-party pages that ask to connect the wallet merely to add an asset.

Worked token import

The explorer confirms a USDC transfer on Polygon to the correct address. MetaMask is on Polygon but does not list it. The user copies the exact Polygon contract from the explorer, imports it and sees the existing quantity. No transaction or approval occurs.

When manual import does not solve the problem

Return to transaction diagnosis when the explorer lacks the token, the destination is different, the chain is unsupported or the transfer failed. Return to account recovery when the token belongs to another derived or imported address.

Current conclusion

A safe token import is an identity check followed by a display change. Verify the chain, receiving address and contract, then use the wallet’s built-in control without signing or paying anything.

Evidence boundaries

MetaMask documentation supports current token detection, contract discovery and manual display steps. Other wallets can use different menus and supported token standards.

Contract-display documentation — July 29, 2026

Token detection, contract lookup and balance-diagnosis material supports the import process.

• MetaMask displaying tokens: https://support.metamask.io/manage-crypto/tokens/how-to-display-tokens-in-metamask/
• MetaMask finding a token contract: https://support.metamask.io/manage-crypto/tokens/how-to-find-a-token-contract-address/
• MetaMask missing token diagnosis: https://support.metamask.io/manage-crypto/tokens/what-to-do-when-your-balance-of-tokens-is-incorrect/

FAQ