Circle’s registry and network-specific notices support checking the exact chain and identifier. Native USDC and bridged representations can share a ticker while remaining distinct assets. That identity check is necessary before a transfer, but it cannot establish that a recipient or service accepts the asset.
Claim & scope
Supported within scopeToken identity is established by the network plus the issuer registry entry or chain-specific mint/contract, not by a ticker, logo or equal dollar display.
USDC deployments documented by Circle and the named network materials reviewed on 2026-09-22. It covers identity checks, not a live deposit test.
Method & review date
Document review completed . Source retrieval dates are listed separately; this is not a live transaction test.
- Read the issuer registry and the issuer notices for Base and Polygon PoS.
- Compare the exact chain and contract or mint with the recipient’s current instructions.
- Separate the identity observation from any inference about service support.
What the documents show
- Circle documents native USDC separately from USDbC on Base and USDC.e on Polygon PoS.
- A chain-specific identifier is a more precise check than a display symbol.
- Circle terms remain relevant after identity is established.
How the conclusion follows
The issuer identifies different contracts for native and bridged tokens. Matching the network and identifier therefore answers which token is involved.
Acceptance belongs to the recipient’s deposit policy, not to the token registry. A registry match alone cannot establish that a deposit will be credited.
Sources and their limits
| Source & date | Supports | Does not establish |
|---|---|---|
| Circle — USDC contract registry (opens in a new tab)issuerPublished: not stated in the reviewed recordRetrieved: Locator: Mainnet contract table | SupportsCircle-published network and contract entries for USDC deployments. | Does not establishIt does not establish a third-party service’s custody, pricing, privacy, refund policy or recipient support. |
| Circle — Native USDC on Base (opens in a new tab)issuerPublished: 2023-09-05Retrieved: Locator: Native USDC and USDbC sections | SupportsCircle’s distinction between native USDC on Base and the earlier bridged USDbC representation. | Does not establishIt does not prove that a named exchange, mixer or recipient accepts either representation today. |
| Circle — Native USDC on Polygon PoS (opens in a new tab)issuerPublished: 2023-10-10Retrieved: Locator: Native USDC and USDC.e sections | SupportsCircle’s distinction between native USDC on Polygon PoS and bridged USDC.e. | Does not establishIt does not establish a service’s deposit policy, fee, custody or privacy practice. |
| Circle — USDC terms (opens in a new tab)issuerPublished: not stated in the reviewed recordRetrieved: Locator: Eligibility and restricted-address provisions | SupportsCircle’s published terms, including eligibility and issuer restriction language. | Does not establishIssuer terms are not a legal opinion for a reader’s circumstances and do not validate a third-party operator. |
Limits & confidence
High for the documented native-versus-bridged distinction; no conclusion about any recipient or service.
- The registry can change; recheck it before acting.
- No named provider, recipient or transaction was tested.
- The sources do not establish pricing, custody, refunds, privacy or legal eligibility.
Next scheduled editorial review: . A material change in a cited source requires an earlier review; this date does not imply continuous monitoring.
Change history
- 2026-09-22 — Initial evidence dossier created from dated issuer and network records.
StableScope is the publisher of this analysis, not the token issuer, network operator or regulator. A link to this dossier does not turn its cited sources into a service endorsement.