How to add custom tokens to Trust Wallet? (Contract Address Guide)

Understanding Custom Token Integration

1. Trust Wallet supports Ethereum, BSC, Polygon, Avalanche, and other EVM-compatible blockchains for custom token additions.

2. Users must verify the exact contract address of the token before initiating the import process.

3. A single typo in the contract address can lead to irreversible loss of funds or incorrect token display.

4. The token’s network must match the wallet’s active network setting—switching networks incorrectly results in failed detection.

5. Trust Wallet does not validate token legitimacy; users bear full responsibility for verifying authenticity through official sources.

Navigating the Token Import Interface

1. Open Trust Wallet and tap the wallet tab at the bottom navigation bar.

2. Scroll down and select Add Custom Token located beneath the token list.

3. Choose the correct blockchain network from the dropdown menu—options include Ethereum, BSC, Polygon, etc.

4. Paste the verified contract address into the designated field without spaces or extra characters.

5. Tap Next, then confirm the token symbol, decimals, and name as displayed by the wallet.

Verifying Token Metadata Accuracy

1. After importing, Trust Wallet fetches metadata such as logo, symbol, and decimal places from on-chain data or community-submitted assets.

2. Discrepancies in decimals may cause balance misrepresentation—always cross-check with explorers like Etherscan or BscScan.

3. If the logo fails to load, it indicates missing or unverified asset information on the Trust Wallet token list repository.

4. Token balances may take several seconds to appear due to node synchronization delays across different RPC endpoints.

5. Some tokens require manual balance refresh by pulling down the token list screen after import completion.

Troubleshooting Failed Imports

1. An “Invalid contract address” error usually stems from using a non-checksummed address or selecting the wrong network.

2. Zero balance display often occurs when the wallet is connected to a testnet instead of mainnet or when the address has no holdings.

3. Missing transaction history post-import suggests the token was added to a wallet that never interacted with that contract before.

4. Repeated failures may indicate the token uses an unsupported standard—only ERC-20, BEP-20, and ERC-721 are natively supported for custom addition.

5. Clearing app cache or reinstalling Trust Wallet does not restore lost tokens but may resolve UI rendering issues related to cached metadata.

Frequently Asked Questions

Q: Can I add a token using only its ticker symbol?A: No. Trust Wallet requires the full contract address and correct network selection. Ticker symbols alone cannot uniquely identify tokens across chains.

Q: Why does my imported token show 0 balance even though I hold it on-chain?A: This commonly happens if the wallet is set to the wrong network, the contract address is incorrect, or the token uses a non-standard implementation not recognized by Trust Wallet’s parser.

Q: Is it safe to import tokens from unofficial Telegram groups or social media links?A: It is extremely unsafe. Malicious actors frequently distribute fake contract addresses designed to drain wallets. Always obtain addresses from official project websites or verified blockchain explorers.

Q: Do I need to pay gas fees to add a custom token?A: No. Adding a custom token is a client-side operation and incurs no blockchain transaction or gas cost. Gas is only required when sending or interacting with the token.