Skip to article
Degrees of SatoshiFollow the connections.
SearchTrace an address
Degrees of Satoshi/ Encyclopedia

Encyclopedia Stablecoins · Entry 38

Native, bridged and wrapped stablecoins

AI-assisted research · separate automated verificationCorrections

Theme
Stablecoins
Sources
5 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for Native, bridged and wrapped stablecoins
FactDetailSource
IdentityNetwork and contract identity matter in addition to a symbol.[3][1]
Lock and mintA bridge can hold an original token and issue a representation elsewhere.[1]
Burn and mintCircle CCTP uses native USDC burning and minting across supported networks.[2]
01

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.

02

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.

03

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?”

Direct answers

Questions people ask

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.

Does native mean no risks?

No. It removes a particular wrapped-asset relationship, but issuer, network, transfer and redemption conditions still apply.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

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: Stablecoins · data through 2026-10-02. Verification: verified · 2026-10-02T18:26:58.075Z.

Link to this claim
Identity: Network and contract identity matter in addition to a symbol.

Scope: Stablecoins · data through 2026-10-02. Verification: verified · 2026-10-02T18:26:58.075Z.

Link to this claim
Lock and mint: A bridge can hold an original token and issue a representation elsewhere.

Scope: Stablecoins · data through 2026-10-02. Verification: verified · 2026-10-02T18:26:58.075Z.

Link to this claim
Burn and mint: Circle CCTP uses native USDC burning and minting across supported networks.

Scope: Stablecoins · data through 2026-10-02. Verification: verified · 2026-10-02T18:26:58.075Z.

Link to this claim
Revision history
  1. — First publication after primary-source research and independent automated verification.
  2. — Expanded explanation: Follow the claim behind each token variant. Worked examples are illustrative; source checks and independent verification are recorded separately.

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. Third-Party Bridged USDC TermsCircle

    Bridged tokens and native USDC differ in issuer relationship and bridge dependency.

    Locator: Scope; risks and bridge conversion · Version / scope: Response SHA-256 aeeeba497c6a8aaa31c70867b65eff818ef40eb2e96e7a890c49d48893974137 · Retrieved: 2026-10-02T14:38:48.775643+00:00Open source
  2. Cross-Chain Transfer ProtocolCircle Developer Documentation

    Native cross-chain transfer uses burn/mint and Circle attestations rather than locked wrapped tokens.

    Locator: Burn-and-mint mechanism; attestation · Version / scope: Response SHA-256 58e661e7d7f1b2e214ea9c752b757a102d00551ceeda17522e3003fafeb2e9f9 · Retrieved: 2026-10-02T14:38:47.486192+00:00Open source
  3. ERC-20 Token StandardEthereum Improvement Proposals

    On-chain token ledger operations do not themselves initiate bank payouts.

    Locator: Methods: transfer, transferFrom, approve; Events · Version / scope: Response SHA-256 98bda5e4707841a68684879878c4c165fdaa47d89ed69ebf232ab9be06ff050e · Retrieved: 2026-10-02T14:38:58.506966+00:00Open source
  4. USDC TermsCircle

    USDC backing, conditional redemption, price fluctuations, no intrinsic interest, freezes, fees and eligibility.

    Locator: Sections 1–4 and 13–16 · Version / scope: Response SHA-256 23312ae7a14fc5e876bce04cbc739e473da466c4a2ae2a35531ffc4cda972ca8 · Retrieved: 2026-10-02T14:38:29.678281+00:00Open source
  5. Cross-Chain Transfer ProtocolCircle

    Issuer-described attestation dependency in cross-chain asset transfers.

    Locator: Burn; Attestation; Mint · Retrieved: 2026-10-02T17:33:31.537ZOpen source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

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/