How to add custom tokens to your Exodus wallet?

Understanding Custom Token Support in Exodus

1. Exodus wallet natively supports Ethereum-based ERC-20 tokens, Binance Smart Chain BEP-20 tokens, and Solana SPL tokens without requiring manual configuration for most popular assets.

2. Tokens listed on major decentralized exchanges like Uniswap or PancakeSwap are often auto-detected when their contract addresses are verified by Exodus’ internal token registry.

3. If a token does not appear in the asset list after connecting your wallet to a DApp or checking the portfolio view, it may be absent from the official token database.

4. Exodus does not allow arbitrary token addition via raw JSON or custom RPC endpoints — only tokens matching known chain standards and verified contract patterns can be enabled.

5. Users cannot import tokens using private keys or seed phrases directly into the token management interface; all custom additions rely on verified blockchain parameters.

Prerequisites Before Adding a Token

1. You must know the exact blockchain network where the token resides — Ethereum, Polygon, BSC, Avalanche C-Chain, or Solana.

2. The full contract address is mandatory; any typo or checksum mismatch will prevent recognition or cause balance display errors.

3. You need the correct token symbol and decimal places — these values are hardcoded into the token’s smart contract and must match what Exodus expects.

4. Your Exodus desktop or mobile app must be updated to version 24.0 or higher to ensure compatibility with newer token standards and multi-chain detection logic.

5. Network-specific RPC settings are preconfigured in Exodus; manual RPC changes are unsupported and may break wallet functionality.

Step-by-Step Token Addition Process

1. Open Exodus and navigate to the Portfolio tab, then click the + icon in the top-right corner of the asset grid.

2. Select the appropriate blockchain from the dropdown — options include Ethereum, Polygon, BSC, Avalanche, and Solana.

3. Paste the verified contract address into the input field labeled Contract Address.

4. Exodus will automatically fetch metadata including name, symbol, and decimals if the contract is live and indexed — otherwise, manual entry fields appear.

5. Confirm the details and click Add Token; the asset appears instantly in your portfolio if the network connection is active and the contract responds.

Common Issues and Their Causes

1. A token shows zero balance despite confirmed on-chain transfers — this usually occurs when the wallet address was not used as the recipient during the transaction or the token uses a non-standard transfer mechanism.

2. “Invalid contract” error appears after pasting an address — this indicates either a checksum mismatch (Ethereum-style address casing), wrong network selection, or an unverified proxy contract.

3. Token name displays as “Unknown Token” — Exodus failed to resolve metadata due to missing or malformed URI in the contract’s name() or symbol() functions.

4. Balance updates lag significantly — this happens when the selected network’s public RPC endpoint is overloaded or the token has low event emission frequency.

5. Solana SPL tokens require explicit mint address entry and do not support automatic discovery like EVM chains — omission of the correct mint key results in no balance detection.

Frequently Asked Questions

Q: Can I add tokens from obscure Layer 2 networks like Arbitrum Nova or zkSync Era?A: No. Exodus currently only supports Arbitrum One and zkSync Era mainnets. Networks without stable block explorers or consistent RPC infrastructure are excluded.

Q: Why does my BEP-20 token show up on BSC Testnet but not Mainnet?A: Testnet contracts are indexed separately. Mainnet tokens require verification against BSCScan’s verified contract list — unverified deployments won’t load.

Q: Is it safe to paste contract addresses from Telegram groups or anonymous websites?A: Not recommended. Malicious actors frequently deploy fake tokens with identical names and symbols. Always cross-check contract addresses on official project channels and block explorers.

Q: Do custom tokens sync across Exodus devices using the same seed phrase?A: Yes. Token configurations are stored locally but restored from on-chain data during wallet initialization — no cloud backup is required for visibility.