Skip to main content
Blocktape

Crypto markets, protocols and policy

Ticker or Contract? Verify Before a DEX Swap

How to verify a token contract before a DEX swap: match the network and full address to the issuer’s deployment record before selecting the asset.

The Blocktape Editors 3 min read 4b9de7

Ticker or Contract? Verify Before a DEX Swap

Ticker or contract? Verify the network and full contract address against the issuer’s authoritative deployment record before choosing a token for a DEX swap. The ERC-20 standard makes name and symbol optional metadata, while Circle’s USDC deployment records publish network-specific addresses. This check matters before a cowswap order too: signed trade intents and solver-run batch auctions make CoW Swap a concrete case where the selected asset must match the intended token.

Have the candidate listing, intended EVM network, and authoritative issuer reference ready. Decide whether you want the native asset, a wrapped version, or a bridged representation; each can have a different contract and issuer record. Keep the issuer page or its URL so you can record where the address came from.

How do you verify a token contract before a DEX swap?

  1. Locate the issuer’s deployment address. Navigate independently to the issuer’s official site and find its deployment record for the intended network and asset form. Circle’s records, for instance, list USDC addresses by network. The result is an issuer-published address to compare with the listing.
  2. Inspect that address on the network’s explorer. Open Etherscan for the relevant network and search the full address. Confirm the explorer identifies a token contract. If it is a proxy, note the proxy address and the implementation address separately: the proxy is the token contract address to match against the issuer record, while the implementation contains code the proxy uses. A source-verified label means the published source matches the deployed code; it records a code comparison, not an asset endorsement.
  3. Match the listing to the proxy address. Compare every character of the issuer’s address with the token contract address on Etherscan and the address shown in the DEX selector. Do not substitute a pool or router address: those belong to swap infrastructure, not the asset you intend to trade. The result is one matching contract address for the chosen network.
  4. Record the identity and provenance. Write down the network, asset form, full contract address, and issuer reference. Select the token using that address, then compare the network and address shown by the DEX with your record. The task is complete when the issuer record, explorer token address, and selected token agree.

A ticker is a label that can be copied; the network and issuer-recorded contract address identify the intended listing. Once those match, you have a documented asset identity ready for DEX selection, with any transfer restrictions or liquidity questions left for separate checks.

What should you check after verifying the address?

How do I inspect token transfer restrictions?

Read the verified contract source and issuer materials for transfer controls, such as allowlists, pausing, or fees. For a proxy, inspect the implementation code and the proxy’s current configuration. Record the relevant functions or issuer statements before trading.

How do I assess token liquidity?

Review the relevant trading pools on the intended network. Compare available depth and expected price impact for your trade size, and confirm the pool contains the same token contract address you verified.

How do I revoke a token approval?

Use a reputable approval checker or your wallet’s permissions view on the same network. Find the spender and token contract, then submit a revoke transaction and confirm it on the explorer.

Related stories