Circle has announced cirBTC, its institutional wrapped Bitcoin, and confirmed Ethereum mainnet as one of two launch venues alongside Arc, Circle's L1. cirBTC is not live yet. The waitlist is open at circle.com/cirbtc and Circle has stated the token is subject to regulatory approvals. This article explains what to expect when the Ethereum deployment goes live: the likely contract pattern based on USDC precedent, how to verify the token on Etherscan, how to add it to a wallet, how to inspect supply, and which DEX and lending integrations are most plausible at launch.
Will cirBTC launch as a standard ERC-20 on Ethereum?
Yes. Circle has confirmed cirBTC will be an ERC-20 on Ethereum mainnet at launch, mirroring the deployment model used for USDC and EURC. ERC-20 is the standard fungible-token interface on Ethereum and the format every major wallet, DEX, custodian, and lending protocol already supports.
Treating cirBTC as a normal ERC-20 means existing infrastructure works without bespoke integration. Wallets like MetaMask, Rabby, and Safe will recognize it once the contract is published. Block explorers will index transfers automatically. The interesting questions are not whether it is ERC-20, but which optional features the contract includes: upgradeability, blacklist, pause, and mint authorization.
What contract pattern will Circle likely use?
Circle has not published the cirBTC contract source as of this writing. The strongest signal for what to expect is Circle's existing playbook on USDC, which has been Ethereum's reference implementation for a regulated, centrally-issued ERC-20 since 2018.
USDC on Ethereum uses a transparent upgradeable proxy in front of a FiatTokenV2_2 implementation. The proxy holds storage and forwards calls to whichever implementation Circle has authorized. Pauser, blacklister, and master minter roles are separated, and minting is gated to addresses Circle explicitly authorizes with per-minter allowances. Pausing halts all transfers globally. Blacklisting freezes specific addresses. Burning is restricted to authorized minters acting on tokens they hold.
cirBTC almost certainly follows this same pattern. Circle's compliance posture, audit history, and operational tooling are built around it. Expect: upgradeable proxy, role-separated administration, mint authorization for the Bitcoin custody bridge that issues new cirBTC against verified BTC reserves, and blacklist plus pause functions for sanctions compliance.
How will cirBTC's contract compare to USDC and wBTC?
Feature | cirBTC (expected) | USDC | wBTC |
Standard | ERC-20 | ERC-20 | ERC-20 |
Decimals | 8 (BTC convention) | 6 | 8 |
Proxy pattern | Upgradeable (transparent proxy expected) | Upgradeable (transparent proxy) | Non-upgradeable |
Mint authorization | Circle-controlled, role-gated | Master minter delegates to per-minter allowances | Single owner (BitGo / BiT Global custodians) |
Blacklist | Expected (USDC pattern) | Yes | No |
Pause | Expected (USDC pattern) | Yes | No |
Reserves | Native BTC, 1:1, onchain attestations | Cash plus short-duration Treasuries | Native BTC held by BitGo and BiT Global |
Issuer | Circle | Circle | BitGo, BiT Global |
The most consequential differences from wBTC: upgradeability and the blacklist. wBTC's contract is intentionally immutable and has no freeze function. cirBTC will almost certainly include both, reflecting Circle's regulated-issuer posture. For institutions this is a feature. For DeFi natives it is a tradeoff worth understanding before integrating.
How do you verify cirBTC on Etherscan when it goes live?
When Circle deploys, the canonical cirBTC contract address will be published on circle.com/cirbtc and announced through Circle's official channels. To verify:
Open the address on Etherscan. Confirm the contract is verified (green checkmark) and the source code matches Circle's published reference.
Check the "Contract Creator" field. It should trace back to a Circle-controlled deployer address consistent with USDC's deployment history.
On the Read Contract tab, call
symbol(),name(), anddecimals(). Expect symbol cirBTC, name something like "Circle Wrapped Bitcoin," and decimals 8.Inspect
totalSupply()and divide by 10^8 to get circulating BTC equivalent.If the contract is a proxy, click through to the implementation contract and verify that source is also published.
Do not trust addresses scraped from social media or unofficial token lists for the first 72 hours after launch. Cross-reference at least two of: circle.com, Etherscan's "Token Info" verified badge, and the CoinGecko or CoinMarketCap entry that links back to Circle.
How will you add cirBTC to a wallet?
Once the contract is live, adding cirBTC to MetaMask, Rabby, or any EVM wallet is the standard ERC-20 flow:
Copy the verified contract address from circle.com/cirbtc.
In the wallet, choose "Import token" or "Add custom token."
Paste the address. The wallet should auto-fill symbol (cirBTC), decimals (8), and name.
Confirm. The token will appear with your balance, which is zero until you acquire some via Circle Mint, an authorized participant, or a DEX.
Within a few weeks of launch, expect cirBTC to appear in default token lists shipped by MetaMask, Uniswap, 1inch, and major aggregators. At that point manual import will be unnecessary.
How will you view cirBTC supply onchain?
Circle has stated cirBTC reserves will be verifiable onchain, consistent with how USDC reserves are reported through monthly attestations and how cbBTC publishes proof-of-reserve. Two ways to read supply directly:
Etherscan: the token's contract page shows
totalSupplylive. Divide by 10^8 for BTC-denominated supply.Dune or Allium dashboards: within days of launch, community analysts will publish dashboards tracking cirBTC mints, burns, holder distribution, and DEX liquidity. Expect dashboards modeled on the established USDC and cbBTC trackers.
DeFiLlama will list cirBTC under wrapped Bitcoin alongside wBTC, cbBTC, tBTC, and FBTC once it has sufficient supply and liquidity.
Which DEX and lending integrations are realistic at launch?
Circle has publicly named lending protocols, market makers, and OTC desks as the institutional audience for cirBTC. Translating that into specific integrations, the realistic launch and post-launch sequence on Ethereum mainnet:
Uniswap v3 and v4: cirBTC/USDC and cirBTC/WETH pools are the obvious first venues. Concentrated liquidity favors stable BTC-to-stablecoin and BTC-to-ETH pairs. Expect early liquidity seeded by Circle partners and market makers within the first weeks.
Aave: wBTC and cbBTC are both Aave V3 collateral. cirBTC is a natural addition once it passes Aave governance, which typically requires a Chaos Labs or LlamaRisk risk assessment, several weeks of supply and liquidity history, and a community vote.
Morpho: Morpho's permissionless market model means cirBTC can be listed as collateral or loan asset by any curator the day the contract is live. Expect curators like Gauntlet, Steakhouse, and MEV Capital to spin up cirBTC markets quickly, paired with USDC or WETH.
Sky (formerly MakerDAO): Sky has historically been conservative about wrapped BTC collateral. wBTC was onboarded years ago. cirBTC inclusion would require a Spark or Sky governance process and is more likely months after launch than weeks.
Curve: a cirBTC/wBTC or cirBTC/cbBTC stable pool is plausible once enough supply exists to make peg-stability trading useful for arbitrageurs.
Aggregators like 1inch, CoW Swap, and Odos will route through whichever pools have liquidity, so DEX integration is effectively automatic once Uniswap or Curve pools exist. Cross-chain orchestrators including Eco Routes can route cirBTC across chains once the Arc deployment and any subsequent L2 deployments come online.
What should developers prepare for now?
Even before launch, three things are worth doing:
Treat cirBTC as 8-decimal: if your codebase hardcodes 6 decimals for Circle assets (USDC, EURC), that assumption breaks for cirBTC. Read
decimals()from the contract, never hardcode.Plan for blacklist semantics: if your protocol holds user funds in pooled contracts, understand that a blacklisted address upstream can create accounting edge cases. wBTC has no such function; USDC and cirBTC do.
Subscribe to the waitlist: circle.com/cirbtc is the canonical source for the contract address and launch date. Do not rely on third-party token lists for the first day.
Methodology and sources
This article is based on Circle's public cirBTC announcement at circle.com/cirbtc and Circle's published USDC contract architecture as the precedent template. Comparison data for wBTC reflects BitGo and BiT Global's published custodian disclosures and the wBTC contract on Etherscan. DEX and lending protocol behavior reflects current Aave V3, Morpho, and Uniswap v3/v4 onboarding processes as of May 2026. All claims about cirBTC contract specifics are framed as expectations because the token has not yet deployed. We will update this article when the contract is published.
Sources: circle.com/cirbtc, Circle's USDC contract documentation, Etherscan (USDC and wBTC contracts), DeFiLlama (wrapped BTC supply), Aave governance forum, Morpho documentation.
Related reading
support/en/articles/15220187
support/en/articles/15220194
support/en/articles/15220196
support/en/articles/15220207

