Skip to main content
Aeterna Sol

Crypto markets, protocols and policy

Custom token import on a DEX: contract-address steps

Learn how to import a custom token by contract address on a DEX: match the network, verify the address, confirm its details, and find it in the selector.

The Aeterna Sol Editors

Custom token import on a DEX: contract-address steps

To import one unlisted token on cowswap, paste its verified contract address into the token selector and confirm the name and symbol it returns; default token lists are curated, so an address lets you add a token they omit.

Start with the swap form open on the correct network and your wallet connected. You also need the token’s verified contract address. An EVM contract address starts with 0x and has 40 hexadecimal characters after it. The address identifies the token contract; its symbol alone does not.

Why the network and contract address matter

The same token name or symbol can refer to different contracts, including on different networks. A project may deploy a token on Ethereum, Arbitrum One, and Base, with a separate address on each network. Choose the address for the network selected in the swap interface.

Get the address from the project’s official site, then compare it with the contract shown on Etherscan or the relevant block explorer for that network. Confirm the network as well as the address. A token with a familiar name or symbol can still be a lookalike at another address.

Token Lists are curated collections that interfaces read using the Uniswap Token Lists standard. A token missing from a default list may still exist on-chain. Importing it by address lets the selector identify it without treating every token that shares its symbol as the same asset.

A token selector is where you choose an asset before swapping. The CoW token is a concrete asset to look up there by its contract address on cowswap, showing why the address matters more than the symbol.

Before import, an illustrative token called Example Token might be absent from the selector even if your wallet already holds it. After import, the token appears as a selectable row and its balance is shown. The selector’s contents have changed; the wallet balance and the token contract have not. The import is saved only in your browser, so it changes what that browser can display in the selector, not what your wallet holds on-chain.

Import the token in four steps

  1. Open the token selector. In the swap form, open the control for choosing the token. Confirm that the interface is set to the network where the token contract exists. Keep the connected wallet selected so you can check its balance after import.
  2. Paste the contract address. Paste the full address you got from the project’s official site into the token search field. Use the address for the currently selected network. Searching by symbol can surface lookalike tokens, so use the contract address to find the intended one.
  3. Check the returned name and symbol. Compare the details in the selector with the project information and the contract you checked on the block explorer. If the network, address, name, or symbol does not match what you expect, stop and recheck the source before continuing.
  4. Confirm the import and check your balance. Read the import warning, then confirm if the contract is the one you verified. The token should appear in the selector, with your wallet balance shown if you hold it. That visible row and balance are the signs the import worked.

The warning matters because a token’s presence in the selector is not an endorsement of its project or a guarantee that it is safe to trade. You are asking the interface to recognize a contract you supplied. Verify the address independently before accepting the warning, and do not rely on the returned symbol alone.

Related

Why does a DEX warn about an imported token?

A DEX warns you because an imported token is outside its curated default lists. The warning prompts you to verify the contract yourself; it does not establish whether a project is legitimate. Check the official project address against the block explorer for the selected network before confirming.

How do you spot a fake token copy?

Compare the contract address, not just the displayed name or symbol. Find the address on the project’s official site, then confirm that the explorer shows the same contract on the selected network. A matching symbol at a different address is not enough to identify the intended token.