How to Add a Custom Asset to Exodus Wallet

Accessing the Asset Management Interface

1. Open the Exodus desktop or mobile application and ensure you are logged into your wallet.

2. Navigate to the Portfolio tab located at the bottom of the mobile app or left sidebar in the desktop version.

3. Tap or click the '+' icon labeled 'Add Asset' — this triggers the asset discovery module.

4. Select “Custom Token” from the list of available options, not “Search Assets” or “Popular Tokens”.

5. Confirm that the network selection matches the token’s underlying blockchain — for example, Ethereum (ERC-20), BSC (BEP-20), or Polygon (ERC-20).

Entering Contract Address and Token Details

1. Paste the verified contract address into the designated field — accuracy is critical; a single incorrect character invalidates recognition.

2. Input the token symbol exactly as published by the project’s official documentation or verified explorers like Etherscan or BscScan.

3. Specify the number of decimals used by the token — common values include 18, 8, or 6, and mismatched decimals cause balance display errors.

4. Provide a recognizable name for internal reference — Exodus uses this label in portfolio views and transaction history.

5. Avoid using placeholder names like “MyToken” or generic acronyms unless they match official branding.

Validation and On-Chain Verification Steps

1. Exodus performs an automatic on-chain lookup once the contract address is submitted — it fetches ABI data and confirms deployer authenticity.

2. The interface displays a green checkmark only after verifying the contract is non-malicious and has active transfer functions.

3. If verification fails, the system shows “Contract not found” or “Invalid bytecode” — double-check the chain selection and address checksum format.

4. Manual override is disabled; no custom RPC or node configuration bypasses this security layer.

5. Verified tokens appear instantly in the asset list but require at least one on-chain transaction to populate historical balance data.

Display Behavior and Portfolio Integration

1. Newly added assets appear under the “Custom” section in the Portfolio view, separated from default listings.

2. Real-time price feeds rely on CoinGecko integration — if the token lacks a public market pair, its value defaults to $0.00 until manually overridden.

3. Transaction history includes inbound/outbound transfers but excludes DEX swaps unless routed through Exodus Swap.

4. Asset icons are pulled from the token’s registered metadata URI — missing icons show a generic polygon-shaped placeholder.

5. Balance discrepancies may occur if the token implements dynamic supply mechanics like rebasing or mint/burn events not tracked by Exodus’ indexer.

Frequently Asked Questions

Q: Can I add a token with no verified contract on Etherscan?A: No. Exodus requires on-chain proof of deployment and function signature validation. Unverified contracts are rejected outright.

Q: Why does my custom token show zero balance after adding it?A: This occurs when the wallet address holds no tokens on that specific chain, or when the token uses a non-standard balanceOf implementation incompatible with Exodus’ read calls.

Q: Is it possible to remove a custom asset once added?A: Yes. Long-press (mobile) or right-click (desktop) the asset tile and select “Remove from Portfolio”. This action does not delete private keys or affect on-chain holdings.

Q: Do custom assets support staking or governance features inside Exodus?A: No. Staking, voting, or contract interaction beyond send/receive is unavailable for user-added tokens. Only officially integrated assets provide those interfaces.