How to fix incorrect token display in Trust Wallet

Understanding Token Display Errors in Trust Wallet

1. Tokens may appear with wrong names or symbols due to incorrect contract address mapping in the wallet’s internal token list.

2. Custom token additions sometimes overwrite official entries when users manually input contract addresses without verifying checksums.

3. Network mismatches—such as adding an ERC-20 token on BSC or vice versa—trigger placeholder or generic asset labels instead of proper branding.

4. Cache corruption from rapid network switching or app updates can freeze outdated token metadata in local storage.

5. Third-party dApps that push token data via WalletConnect may inject malformed display parameters directly into the wallet interface.

Verifying Contract Integrity and Chain Alignment

1. Open the token detail page and tap the ⓘ icon to inspect the raw contract address—compare it byte-for-byte with verified sources like Etherscan or BscScan.

2. Confirm the blockchain network selected matches the token’s native chain: USDT on Ethereum must use ETH network, not Polygon or Arbitrum.

3. Check if the contract implements standard interfaces like ERC-20 or BEP-20—non-compliant tokens often fail name/symbol resolution.

4. Use a blockchain explorer to verify the contract’s verified source code and confirm it publishes name() and symbol() functions correctly.

5. Cross-reference the decimal count—mismatched decimals cause balance misrepresentation and sometimes suppress correct label rendering.

Clearing Local Metadata Cache

1. Navigate to Settings > Wallet > Clear Cache—this forces Trust Wallet to re-fetch token metadata from its canonical registry.

2. Disable and re-enable the affected network under Network Settings to reset chain-specific token lists.

3. Manually remove and re-add the token using the “Add Token” > “Custom Token” flow, ensuring checksummed address entry.

4. Restart the application after cache purge—some display anomalies persist until full process reload.

5. Avoid importing tokens via QR codes from untrusted sources; those often embed spoofed display fields bypassing verification layers.

Handling Community-Submitted Token Lists

1. Trust Wallet relies on community-maintained token lists hosted on GitHub—outdated or malicious PRs may introduce incorrect display data.

2. If a token appears wrong across multiple wallets using the same list, check the trustwallet/assets repository for pending or merged updates.

3. Submit corrections directly to the official assets repo—verified maintainers review and merge changes within 48 hours.

4. Do not rely on unofficial token list mirrors—these lack audit trails and may serve tampered metadata.

5. Monitor the commit history of the token’s folder path to identify recent changes that may explain sudden display shifts.

Frequently Asked Questions

Q: Why does my token show as “Unknown” even though the contract is verified?A: The wallet may not recognize the contract if it’s deployed on a testnet or a non-standard fork not included in Trust Wallet’s supported networks list.

Q: Can I edit token name or symbol locally without changing the contract?A: No—Trust Wallet does not allow manual override of on-chain metadata; any local label edits are discarded on cache refresh or app update.

Q: Does enabling “Show all tokens” affect display accuracy?A: Yes—this setting pulls tokens from explorers dynamically, increasing risk of false positives from contracts mimicking standard interfaces without full compliance.

Q: Why do some tokens display correctly on iOS but not Android?A: Platform-specific caching mechanisms and differing SDK versions cause inconsistent metadata parsing—especially for tokens with Unicode characters in name fields.