Identify a Token by Network and Contract, Not Symbol

Names, tickers and logos make tokens recognizable, but they are not unique identifiers. For an ERC-20 asset, use the network and full token contract together when deciding which asset a balance describes.

Begin with a source independent of the token entry

Locate the issuer’s contract registry or the network’s official deployment reference independently. Compare the registry’s network label and complete contract with the entry you are inspecting. ERC-20 defines name and symbol as optional metadata methods; a convincing name alone is not identity evidence. Do not use an unsolicited token’s own website as the only source confirming its legitimacy.

Separate the asset from its owner

The token contract identifies the asset’s contract on a chain. Your public account address identifies the account whose balance you want to inspect. They are not interchangeable destinations. On an explorer, confirm that you are looking at the token contract and then the intended account’s holding of that token. Copying an issuer’s contract into a recipient field does not mean you have selected a token for a transfer.

Work through a Base example

Circle’s registry lists native Base USDC at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. Base’s registry lists WETH9 at 0x4200000000000000000000000000000000000006. Compare these references with Base mainnet, chain ID 8453, rather than assuming the address string alone determines the chain. Other assets with similar symbols, and deployments on other networks, require their own identity evidence. These contract examples are not payout or recipient addresses.

State what a match does and does not prove

A matching registry entry helps establish which contract you are discussing. It does not prove that a website’s route executes, that a permission request has the right spender or that a token has a guaranteed value. Keep balance quantities, decimals and allowance checks as separate questions. RunixCoin’s catalog is illustrative, and the public estimate form does not establish an executable route for every listed asset. If the registry and interface disagree, leave the identity unresolved.

References and verification

Reviewed 10 November 2026. Product details reflect inspected interface code; camera scanning, browser behavior and mainnet execution were not verified.