How to Enable a Token That Is Not Showing in Trust Wallet

Understanding Token Visibility in Trust Wallet

1. Trust Wallet relies on a curated token list maintained by its internal team and community contributors via GitHub repositories.

2. A token may not appear even if it is deployed on a supported chain due to missing metadata such as name, symbol, decimals, or logo URI.

3. Tokens without verified contract ownership or those flagged for suspicious behavior are automatically excluded from the default display.

4. The wallet does not auto-detect tokens solely based on balance changes — users must manually add them using contract addresses.

5. Some tokens use non-standard ERC-20 interfaces or proxy patterns that prevent automatic recognition during balance scanning.

Manual Addition via Contract Address

1. Open Trust Wallet and navigate to the wallet tab for the target blockchain (e.g., Ethereum, BSC, Polygon).

2. Tap the '+' icon in the top-right corner and select “Add Custom Token”.

3. Choose the correct network and paste the verified contract address into the designated field.

4. Confirm the token’s symbol and decimal places — mismatched decimals cause incorrect balance display.

5. Save the entry; the token should appear immediately if the contract responds correctly to balanceOf() calls.

Metadata Submission Process

1. Token creators must submit a pull request to the trustwallet/assets GitHub repository.

2. Required files include info.json (with name, symbol, description), logo.png (256x256, transparent background), and optional links to website and social media.

3. All contracts must be verified on Etherscan or equivalent explorers before submission.

4. Pull requests undergo automated checks for duplicate symbols, invalid URIs, and inconsistent naming conventions.

5. Approved submissions typically appear in the wallet within 48 hours after merge, provided the app updates its asset cache.

Risks of Unlisted Tokens

1. Tokens absent from official lists often lack audit reports or have unverified developers behind them.

2. Fake tokens mimicking popular projects frequently use similar names and logos to deceive users during manual addition.

3. Contracts with hidden transfer functions or owner-controlled minting capabilities may drain balances silently after approval.

4. Some tokens implement dynamic fee mechanisms that alter transaction costs based on sender address or time, bypassing standard gas estimation.

5. Wallets do not validate token logic at runtime — once added, all interactions depend entirely on the contract’s on-chain behavior.

Common Questions and Answers

Q: Why does my token show zero balance after adding it manually?A: This usually occurs when the contract address is incorrect, the network selection does not match deployment, or the token uses a non-standard interface that prevents balanceOf() from returning accurate values.

Q: Can I add a BEP-20 token to my Ethereum wallet view?A: No. Trust Wallet separates networks strictly — BEP-20 tokens only appear under Binance Smart Chain, not Ethereum, regardless of identical contract logic.

Q: Does adding a custom token expose my private key to external servers?A: No. All operations occur locally; Trust Wallet never transmits private keys or seed phrases outside the device.

Q: What happens if the token’s contract gets upgraded or replaced?A: The wallet continues displaying the original contract address. Users must manually remove and re-add the new address to reflect updated functionality or balances.