# Finding the correct stablecoin contract for a network A stablecoin’s symbol is not a unique identifier. On contract-based networks, identify the asset by the chain and contract address, then compare it with the issuer’s official deployment list. Native, bridged and test versions can have similar names while representing different assets and redemption paths. Evidence: [USDC Contract Addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses); [ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20) Canonical: https://degreesofsatoshi.com/encyclopedia/stablecoin-contract-addresses/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T18:15:23.891Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Names:** ERC-20 name and symbol fields do not enforce global uniqueness. ([ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20)) - **Network:** Circle publishes chain-specific USDC contract identifiers. ([USDC Contract Addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses)) - **Environment:** Mainnet and testnet deployments must be distinguished. ([USDC Contract Addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses)) ## Use a chain-and-contract pair Choose the intended network first, then compare the full contract address with an issuer-controlled source. A search-engine result or a token’s chosen symbol is weaker evidence than an official deployment record. This article links to the authoritative list rather than copying high-entropy identifiers into prose, where a typo or an outdated deployment could be hard to spot. Evidence: [USDC Contract Addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses) ## A familiar name does not carry issuer authority A different contract can expose the same name, symbol and decimals. An explorer can display those fields faithfully while the asset is unrelated to the issuer. An authentic bridged representation can also differ from native issuance. Identify its bridge and backing path instead of assuming every matching symbol is either native or fraudulent. Evidence: [ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20); [USDC Contract Addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses) ## Check the receiving service’s exact support An exchange or custody service may support only selected deployments. Sending a real token on an unsupported chain can still create a recovery problem. Match the service’s deposit instructions to the issuer’s network record before using a destination. Token authenticity and destination support are separate checks. Evidence: [USDC Contract Addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses); [USDC Terms](https://www.circle.com/legal/usdc-terms) ## Questions ### Does a verified token contract prove it is the issuer’s official stablecoin? No. Source verification concerns code matching. Issuer identity must be established through the issuer’s own deployment records for the intended network. Evidence: [USDC Contract Addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses); [Navigating the Contract Code tab](https://kb.etherscan.com/navigating-the-contract-code-tab) ## Claims and scope ### stablecoin-contract-addresses-quick-answer A stablecoin’s symbol is not a unique identifier. On contract-based networks, identify the asset by the chain and contract address, then compare it with the issuer’s official deployment list. Native, bridged and test versions can have similar names while representing different assets and redemption paths. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ### stablecoin-contract-addresses-fact-names Names: ERC-20 name and symbol fields do not enforce global uniqueness. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ### stablecoin-contract-addresses-fact-network Network: Circle publishes chain-specific USDC contract identifiers. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ### stablecoin-contract-addresses-fact-environment Environment: Mainnet and testnet deployments must be distinguished. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [USDC Contract Addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses) — Circle. Network-specific canonical contract identifiers and the distinction from test deployments. Locator: Mainnet; Testnet. Retrieved: 2026-10-02T17:03:43.107Z. - [ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20) — Ethereum Improvement Proposals. Token supply, displayed units and balance accounting. Locator: totalSupply; balanceOf; transfer; decimals; approve; allowance; transferFrom; Transfer. Retrieved: 2026-10-02T17:03:45.826Z. - [USDC Terms](https://www.circle.com/legal/usdc-terms) — Circle. Non-EEA USDC holder terms, eligibility, redemption and restrictions; not an unconditional promise to every holder. Locator: Sections 1–4, 8, 13, 15–17. Retrieved: 2026-10-02T17:03:43.080Z. - [Navigating the Contract Code tab](https://kb.etherscan.com/navigating-the-contract-code-tab) — Etherscan. Published source and compiler settings are checked against deployed bytecode. Locator: Source Code Verification; Compiler; Optimization; Similar Match. Retrieved: 2026-10-02T17:29:13.898Z. ## Revision history - 2026-10-02: First publication after primary-source research and independent automated verification. ## Cite this entry Degrees of Satoshi editorial project. “Finding the correct stablecoin contract for a network.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/stablecoin-contract-addresses/