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

Understanding Token Standards on Coinbase Wallet

1. Coinbase Wallet supports tokens built on Ethereum, Polygon, Arbitrum, Optimism, Base, and other EVM-compatible chains.

2. Most custom tokens follow the ERC-20 standard on Ethereum-based networks, while others may use BEP-20 or similar variants on compatible chains.

3. The wallet does not auto-detect tokens added to your address unless they are already in its internal token registry.

4. Manual import bypasses the need for pre-approval or listing by Coinbase, granting immediate visibility of balances if the contract is valid and deployed correctly.

5. Users must verify the token’s blockchain network, contract address, symbol, and decimals before initiating import—errors here lead to zero balance display or phantom tokens.

Navigating the Import Interface

1. Open Coinbase Wallet app on iOS or Android and ensure you’re on the latest version.

2. Tap the Assets tab at the bottom, then select the + Add assets button in the top-right corner.

3. Choose Import token instead of browsing the default list.

4. Select the correct network from the dropdown—this must match the chain where the token contract resides.

5. Paste the full contract address into the designated field; the app will attempt to fetch name, symbol, and decimals automatically—if it fails, these fields must be entered manually with verified values.

Verifying Contract Authenticity

1. Always cross-check the token contract address on a block explorer like Etherscan, Polygonscan, or Arbiscan before importing.

2. Confirm the contract is verified—unverified contracts carry high risk of scams, minting traps, or locked liquidity.

3. Review the token’s source code, ownership status, and recent transaction history to detect anomalies such as sudden transfers or unrenounced ownership.

4. Check whether the token implements common red flags: hidden transfer functions, unchangeable minting permissions, or abnormal fee structures embedded in the logic.

5. Avoid tokens promoted exclusively through unsolicited DMs, anonymous Telegram channels, or domains mimicking official project sites.

Managing Imported Tokens Post-Addition

1. Once imported, the token appears under Assets but does not auto-enable swapping or staking features unless supported natively by the wallet’s integrated DEXs.

2. Sending custom tokens requires selecting the correct network and ensuring sufficient native gas (e.g., ETH on Ethereum, MATIC on Polygon) remains in the wallet.

3. Balance updates may lag by several seconds or minutes depending on node sync speed and network congestion—refreshing manually does not force real-time reconciliation.

4. Removing an imported token hides it from view but does not delete associated data or transaction history stored locally.

5. Reimporting the same token with mismatched decimals or symbol entries creates duplicate entries—users must delete the incorrect one before reattempting.

Frequently Asked Questions

Q: Can I import tokens from non-EVM chains like Solana or Cardano into Coinbase Wallet?A: No. Coinbase Wallet only supports manual import for EVM-compatible networks. Solana and Cardano tokens require separate wallet integrations and are not accessible via the import flow.

Q: Why does my imported token show zero balance even though I hold it on-chain?A: This occurs when the network selection during import doesn’t match the chain where the token resides, or the contract address was pasted incorrectly—including extra spaces or wrong checksum casing.

Q: Does importing a token grant Coinbase Wallet access to my private keys or control over the asset?A: No. Importing only adds a display layer for balance tracking. Private keys remain fully under user control, and no third party gains authority over transfers or approvals.

Q: Can I import a token that uses a custom decimal value not listed in the dropdown?A: Yes. The interface allows manual entry of decimal values. Entering an incorrect value causes balance misrepresentation—always confirm this number from the contract’s public ABI or verified source code.