How to add custom tokens to Trust Wallet? (Manual Import)

Understanding Token Standards on Trust Wallet

1. Trust Wallet supports multiple blockchain networks including Ethereum, Binance Smart Chain, Polygon, Solana, and others. Each network has its own token standard—ERC-20 for Ethereum, BEP-20 for BSC, SPL for Solana, and so on.

2. Tokens must comply with the technical specifications of their respective chain. A custom token built on Ethereum but lacking proper ERC-20 interface implementation may not display balances or allow transfers correctly.

3. The wallet does not verify contract legitimacy. Users bear full responsibility for confirming the authenticity of token contracts before importing.

4. Token metadata—including name, symbol, and decimals—is pulled from the contract itself or from decentralized sources like the Trust Wallet Token List repository when auto-detected.

5. Manual import bypasses automatic detection logic, meaning no logo, price data, or description will appear unless added later via community submissions or third-party integrations.

Navigating the Manual Import Interface

1. Open Trust Wallet and tap the Wallet tab at the bottom.

2. Tap the + icon in the top-right corner to access the token search and add screen.

3. Scroll down and select Custom Token, then choose the correct blockchain network from the dropdown menu.

4. Enter the exact contract address as published by the project’s official channels. Any typo or incorrect checksum will result in a failed import or zero balance.

5. Input the token symbol and number of decimals exactly as defined in the smart contract. Mismatched decimals cause balance misrepresentation—for example, showing 0.000001 instead of 1.0.

Verifying Contract Authenticity Before Import

1. Cross-check the contract address on Etherscan, BscScan, or the relevant block explorer using official links from the project’s verified website or Twitter account.

2. Review the contract’s source code if it is verified. Unverified contracts carry higher risk of malicious functions like minting, blacklisting, or uncontrolled transfer restrictions.

3. Check transaction history for abnormal patterns—such as sudden large transfers to unknown wallets or repeated failed interactions—which may indicate scams.

4. Look for audit reports from reputable firms like CertiK, OpenZeppelin, or Quantstamp. Absence of an audit does not guarantee insecurity but increases due diligence burden.

5. Confirm whether the token is listed on major decentralized exchanges like Uniswap or PancakeSwap. Liquidity presence adds another layer of validation, though not infallible.

Managing Imported Tokens Post-Addition

1. After successful import, the token appears under the selected network’s asset list. Its balance updates in real time based on on-chain events.

2. Sending requires selecting the imported token from the asset picker during transaction creation. Gas fees are paid in the native currency of the chain—not the token itself.

3. To remove a custom token, long-press its row in the asset list and select Hide Token. This action does not delete the contract or affect holdings.

4. Hidden tokens can be restored by returning to Custom Token and re-entering the same contract details—no new import is needed.

5. Balance discrepancies may arise if the token uses non-standard interfaces or implements custom balance retrieval logic outside typical ABI expectations.

Frequently Asked Questions

Q: Can I import tokens from chains not listed in the Custom Token dropdown?Trust Wallet only allows manual import for networks it natively supports. Unsupported chains—like Arbitrum Nova or Base before integration—cannot be added manually through this flow.

Q: Why does my imported token show zero balance even though I hold it on-chain?This usually occurs due to incorrect decimal input or a contract that deviates from standard balanceOf() behavior. Verify the contract’s ABI and test balance retrieval using a block explorer’s “Read Contract” tool.

Q: Does importing a token expose my private key to external servers?No. All contract interaction happens client-side. Trust Wallet never transmits private keys or seed phrases to any server during import or usage.

Q: Can I rename an imported token inside Trust Wallet?Not directly. The displayed name comes from the contract’s name() function. Editing it locally is unsupported and would break consistency across devices and future syncs.