LogoLogo
WebsiteTwitterGitHub
  • Introduction
    • Bridge
  • Wallets
    • fWallet
    • Rabby
    • MetaMask
    • Coinbase Wallet
    • Ledger
  • Staking
    • Overview
    • Stake FTM
    • Liquid Staking
    • Governance
  • Build on Opera
    • Overview
    • Tutorials
      • Deploy Contract
      • Verify Contract
      • Unit Test Contract
      • Create Fixed-Cap Asset
      • Create Variable-Cap Asset
      • Proxy Pattern
      • Diamond Proxy Pattern
    • Oracles
      • Chainlink
      • Band Protocol
      • API3
    • API
      • Public Endpoints
      • Transaction Tracing
      • Web3 API
      • GraphQL
        • Getting Started
        • Installation
        • Schema Basics
        • Schema Structure
        • Implementation Details
    • Providers
      • Contracts
        • Chainstack
        • thirdweb
        • GetBlock
      • API
        • The Graph
        • Covalent
        • Moralis
  • Funding
    • Gas Monetization
  • Run a Node
    • Overview
    • Node Providers
    • Mainnet
      • Run Validator Node
      • Run API Node
    • Testnet
      • Run Validator Node
      • Run Read-Only Node
    • Troubleshooting
    • FAQ
  • Technology
    • Overview
    • Consensus
    • Database Storage
    • Proof of Stake
    • Transaction Fees
    • Stablecoin
    • FAQ
  • Security
    • Contract Library
    • Fantom Safe
Powered by GitBook

© 2024 Fantom Foundation

On this page
  • Bridge USDC to Opera
  • Native vs. Bridged USDC
  • Pathway to Native USDC
Export as PDF
  1. Technology

Stablecoin

PreviousTransaction FeesNextFAQ

Last updated 7 months ago

Opera's canonical stablecoin is USDC.e, supported by Circle and Wormhole.

USDC.e on is bridged from native USDC, located in a smart contract on Ethereum, and holds the potential to be upgraded to native USDC in the future by . It's the official, endorsed stablecoin of the Opera ecosystem.

Bridge USDC to Opera

To bridge USDC from Ethereum to Opera, use . You will receive USDC.e on Opera upon completion, which is the canonical stablecoin for our chain.

You can only bridge USDC from Ethereum and not from any other chains. For other assets, please refer to .

Native vs. Bridged USDC

According to Circle, the differences between native USDC and bridged USDC are:

Unlike native USDC, bridged USDC isn’t minted by Circle itself. On Opera, USDC.e is minted by Wormhole, bridged from native USDC located in a smart contract on Ethereum. At any point, Circle can then obtain ownership of the USDC.e token contract on Opera and upgrade it to native USDC.

Pathway to Native USDC

Circle has outlined these steps for upgrading bridged USDC to native USDC:

  1. Wormhole has deployed USDC.e on the network

  2. USDC.e is used to bootstrap initial liquidity in the ecosystem

  3. USDC.e reaches a significant supply, amount of holders, and number of app integrations

  4. Circle and the Fantom Foundation/Wormhole jointly elect to securely transfer ownership of the USDC.e token contract to Circle

  5. Upon obtaining ownership, Circle upgrades USDC.e to native USDC and seamlessly retains existing supply, holders, and app integrations

The Fantom Foundation will provide liquidity for the USDC.e stablecoin on Wormhole, making it easy for the token to spread across the network and for users to bridge assets to Opera. As USDC.e begins to proliferate and gain a vast amount of holders and app integrations, Circle may consider stepping in to upgrade its token contract to native USDC.

In this scenario, the upgrade would be seamless and wouldn’t require developers to update contract addresses or users to swap to the new token. The automatic changeover ensures that native USDC on Opera can leverage the built-up USDC.e liquidity so there isn't any interruption on the network.

Native USDC

  • Issued by Circle, a regulated fintech company

  • Backed by US dollars and always redeemable 1:1

  • Official form of USDC on a given blockchain

  • Interoperable with multiple blockchain networks via Circle’s Cross-Chain Transfer Protocol

Bridged USDC

  • Created by a third party, e.g. Wormhole

  • Backed by native USDC on another blockchain locked in a smart contract

  • Not compatible with Circle’s Cross-Chain Transfer Protocol

  • Upgradable to native USDC

Wormhole
Circle
PortalBridge
Squid Router