Why is my token's price or logo not showing correctly in Trust Wallet?

Token Contract Verification Issues

1. Token contracts deployed on EVM-compatible chains must be verified on the respective block explorer before Trust Wallet displays accurate price and logo data.

2. Unverified contracts trigger fallback behavior where Trust Wallet pulls generic placeholder icons and omits price feeds entirely.

3. Verification requires submitting source code, compiler version, optimization settings, and constructor arguments to match on-chain bytecode exactly.

4. Contracts deployed via proxy patterns or with complex initialization logic often fail verification unless all upgradeable components are submitted separately.

5. Even after successful verification, caching layers inside Trust Wallet may delay updates by up to 72 hours without manual cache clearing or wallet restart.

Logo Hosting and Format Requirements

1. Trust Wallet only accepts logos hosted on HTTPS endpoints with direct image access—no redirects, authentication walls, or dynamic CDN tokens allowed.

2. Supported formats include PNG and SVG; JPEG files are rejected silently even if served over valid HTTPS.

3. Dimensions must be square and at least 256×256 pixels; smaller sizes cause rendering failures or pixelation across device densities.

4. File names must contain no special characters or spaces—only alphanumeric characters and hyphens are permitted in the path.

5. CORS headers must explicitly allow requests from trustwallet.com and related subdomains, otherwise the image load fails client-side.

Price Feed Integration Dependencies

1. Price data relies exclusively on CoinGecko’s token list and API indexing—not CoinMarketCap or other aggregators.

2. Tokens must be added to the official CoinGecko token list with correct contract address, chain ID, and symbol mapping before Trust Wallet retrieves real-time pricing.

3. Missing or mismatched decimals in the CoinGecko entry cause price scaling errors—displaying $0.0001 instead of $100 due to incorrect base-10 division.

4. Tokens bridged across multiple chains require individual listings per network; a BSC listing does not auto-propagate to Polygon or Arbitrum.

5. Delays in CoinGecko’s daily sync cycle mean newly listed tokens may appear with stale or missing prices for up to 24 hours post-approval.

Wallet Cache and Local Storage Behavior

1. Trust Wallet stores token metadata—including logo URLs and price timestamps—in local SQLite databases that do not auto-refresh on contract changes.

2. Users must manually remove and re-add the token using its full contract address to force a fresh metadata fetch.

3. Android and iOS versions handle cache invalidation differently—iOS retains outdated assets longer unless background app refresh is enabled.

4. Clearing app storage resets all custom token preferences and requires re-importing watchlist entries individually.

5. Network switching (e.g., from Ethereum Mainnet to Base) does not purge cached assets from prior chains, leading to cross-chain logo mismatches.

Frequently Asked Questions

Q: Does Trust Wallet support custom RPC endpoints for token discovery?A: No. Trust Wallet only recognizes tokens registered on its internal list or those matching known contract addresses on default RPCs. Custom endpoints are ignored during token scanning.

Q: Can I force a logo update without redeploying the contract?A: Yes—if the logo URL remains unchanged but content is updated, you must invalidate the CDN cache and confirm the new image loads correctly in a browser before Trust Wallet detects it.

Q: Why does my token show correct data on MetaMask but not Trust Wallet?A: MetaMask uses decentralized token lists like tokenlists.org and allows user-submitted metadata, while Trust Wallet enforces centralized validation through CoinGecko and its own verified asset registry.

Q: Is there a way to test logo and price display before mainnet launch?A: Yes—deploy identical contract logic and metadata on testnets supported by Trust Wallet (e.g., Sepolia, Mumbai), then verify and host assets there first to validate rendering behavior.