# Native, bridged and wrapped stablecoins A native stablecoin is issued through the issuer’s supported arrangement on that network. A bridged or wrapped version usually represents an asset held or controlled elsewhere, adding a conversion dependency. A familiar ticker is not enough to establish equivalence: identify the network, contract, issuer relationship and exit route. Evidence: [Third-Party Bridged USDC Terms](https://www.circle.com/legal/bridged-usdc-terms); [Cross-Chain Transfer Protocol](https://developers.circle.com/cctp) Canonical: https://degreesofsatoshi.com/encyclopedia/native-bridged-wrapped-stablecoins/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T18:26:58.075Z 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 - **Identity:** Network and contract identity matter in addition to a symbol. ([ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20); [Third-Party Bridged USDC Terms](https://www.circle.com/legal/bridged-usdc-terms)) - **Lock and mint:** A bridge can hold an original token and issue a representation elsewhere. ([Third-Party Bridged USDC Terms](https://www.circle.com/legal/bridged-usdc-terms)) - **Burn and mint:** Circle CCTP uses native USDC burning and minting across supported networks. ([Cross-Chain Transfer Protocol](https://developers.circle.com/cctp)) ## Follow the claim behind each token variant For a conventional wrapped route, ask what asset is held elsewhere and which mechanism permits release of that backing. The wrapper adds a dependency on that conversion path. Native issuance uses the issuer’s supported arrangement on the destination network. CCTP’s native USDC route illustrates a different design: source burning, attestation and destination minting. It avoids that conventional locked-token wrapper while retaining issuer and cross-chain dependencies. Expanded CCTP asset routes can have different semantics, so identify the exact asset and version. Evidence: [Cross-Chain Transfer Protocol](https://developers.circle.com/cctp); [Cross-Chain Transfer Protocol](https://www.circle.com/cross-chain-transfer-protocol) ## Cross-chain does not always mean wrapped Circle’s CCTP documentation accessed on 2 October 2026 describes burning native USDC on one supported network and minting it on another after the protocol’s attestation process. That is different from keeping the original token locked behind a transferable bridge receipt. Burn-and-mint still has dependencies: source-chain confirmation, attestation, destination execution and the issuer’s token rules. Calling the output native answers a token-identity question; it does not eliminate operational or issuer risk. Avoid attaching a universal completion time to all network pairs. Evidence: [Cross-Chain Transfer Protocol](https://developers.circle.com/cctp) ## Follow the complete route out Record the chain and exact contract or asset identifier, then match it to the issuer or bridge documentation. ERC-20 names and symbols are descriptive fields, not globally unique identifiers. A token can display a familiar name without having the expected backing or authority. Circle’s bridged-USDC terms explicitly distinguish third-party bridged tokens from USDC it issues. They describe unbridging as a prerequisite in the covered route. The useful comparison is therefore “Which asset can this balance become, through which steps?” rather than “Do both wallets show the same ticker?” Evidence: [Third-Party Bridged USDC Terms](https://www.circle.com/legal/bridged-usdc-terms); [ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20); [USDC Terms](https://www.circle.com/legal/usdc-terms) ## Questions ### Are all tokens called USDC the same asset? No. Check the network, contract and native or bridge status. A ticker alone does not establish the issuer relationship. Evidence: [Third-Party Bridged USDC Terms](https://www.circle.com/legal/bridged-usdc-terms); [ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20) ### Does native mean no risks? No. It removes a particular wrapped-asset relationship, but issuer, network, transfer and redemption conditions still apply. Evidence: [Cross-Chain Transfer Protocol](https://developers.circle.com/cctp); [USDC Terms](https://www.circle.com/legal/usdc-terms) ## Claims and scope ### native-bridged-wrapped-stablecoins-quick-answer A native stablecoin is issued through the issuer’s supported arrangement on that network. A bridged or wrapped version usually represents an asset held or controlled elsewhere, adding a conversion dependency. A familiar ticker is not enough to establish equivalence: identify the network, contract, issuer relationship and exit route. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ### native-bridged-wrapped-stablecoins-fact-identity Identity: Network and contract identity matter in addition to a symbol. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ### native-bridged-wrapped-stablecoins-fact-lock-and-mint Lock and mint: A bridge can hold an original token and issue a representation elsewhere. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ### native-bridged-wrapped-stablecoins-fact-burn-and-mint Burn and mint: Circle CCTP uses native USDC burning and minting across supported networks. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Third-Party Bridged USDC Terms](https://www.circle.com/legal/bridged-usdc-terms) — Circle. Bridged tokens and native USDC differ in issuer relationship and bridge dependency. Locator: Scope; risks and bridge conversion. Retrieved: 2026-10-02T14:38:48.775643+00:00. - [Cross-Chain Transfer Protocol](https://developers.circle.com/cctp) — Circle Developer Documentation. Native cross-chain transfer uses burn/mint and Circle attestations rather than locked wrapped tokens. Locator: Burn-and-mint mechanism; attestation. Retrieved: 2026-10-02T14:38:47.486192+00:00. - [ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20) — Ethereum Improvement Proposals. On-chain token ledger operations do not themselves initiate bank payouts. Locator: Methods: transfer, transferFrom, approve; Events. Retrieved: 2026-10-02T14:38:58.506966+00:00. - [USDC Terms](https://www.circle.com/legal/usdc-terms) — Circle. USDC backing, conditional redemption, price fluctuations, no intrinsic interest, freezes, fees and eligibility. Locator: Sections 1–4 and 13–16. Retrieved: 2026-10-02T14:38:29.678281+00:00. - [Cross-Chain Transfer Protocol](https://www.circle.com/cross-chain-transfer-protocol) — Circle. Issuer-described attestation dependency in cross-chain asset transfers. Locator: Burn; Attestation; Mint. Retrieved: 2026-10-02T17:33:31.537Z. ## Revision history - 2026-10-02: First publication after primary-source research and independent automated verification. - 2026-10-02: Expanded explanation: Follow the claim behind each token variant. Worked examples are illustrative; source checks and independent verification are recorded separately. ## Cite this entry Degrees of Satoshi editorial project. “Native, bridged and wrapped stablecoins.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/native-bridged-wrapped-stablecoins/