Token names are labels; contract addresses establish identity

A token’s name and symbol describe it; its network and contract address identify the on-chain contract. The ERC-20 standard makes name, symbol and decimals optional metadata fields, so matching labels alone cannot establish that a token came from the expected issuer.

Wallets and trading interfaces use metadata to display balances and token amounts. A symbol can be copied by another contract, and decimals determine how raw token units are displayed; neither field proves who deployed the contract. For a closer look at how token checks relate to trading, the base swap guide covers liquidity, fees, positions and withdrawals.

What does token metadata tell you?

Token metadata tells you how a contract presents itself to software, not whether it is authentic. Under ERC-20, a contract can return a name, symbol and decimals value, but the standard treats these fields as optional and does not reserve names or symbols for particular issuers.

That distinction matters when a wallet shows a familiar ticker. Two contracts on the same network can display the same symbol while tracking separate balances and applying different rules. NFT metadata can also include fields such as an image or description, often fetched from a URI; those details add context but do not replace checking the contract address.

How do you check a token’s contract identity?

Start with the exact network and contract address published by the token’s issuer. Ethereum.org’s guidance on identifying scam tokens also advises checking the issuer’s published address, because an impersonating contract can use the same name and symbol as a legitimate token.

• Confirm the network shown in your wallet or trading interface; the same address format can exist on different chains.
• Find the token address on the issuer’s official site or another issuer-controlled channel, then compare every character with the explorer entry.
• Check that the explorer page is for that network and address, rather than a search result for the token’s name.
• Compare the displayed name, symbol and decimals with the issuer’s information as a consistency check, not as proof of identity.

On Base, for example, check the Base network and look up the address in a Base block explorer. A token bridged to another network may have a different contract address there, so confirm the issuer’s published address for the chain you intend to use.

What does verified contract source prove?

Explorer source verification means the published source and build settings correspond to the deployed contract’s bytecode under the explorer’s verification process. Base documentation points developers to contract verification on Basescan and Etherscan to make source code publicly available.

That lets readers inspect what the code says the contract can do, including whether it contains functions for minting, pausing transfers or changing fees. Verification does not certify the issuer, endorse the token or establish that the code is safe; it makes the submitted source easier to compare with the deployed program.

What should you do before trading or approving?

For most readers, the better check is to establish the issuer’s address first, then use the explorer to confirm the network and inspect verified code. If the address is missing from the issuer’s own channels or differs from the explorer result, stop before swapping or granting an allowance.

A contract address answers which contract you are interacting with; metadata answers what the contract calls itself. Check both, and treat verified source as an inspection aid. Before a transaction, compare the final wallet prompt’s network, token and spender with the action you intended; the next step is to proceed only when those details match.