Yes — Arc is EVM-compatible, and not in the loose marketing sense. Solidity contracts, MetaMask, Hardhat, Foundry, and the mental models you built on Ethereum carry over unchanged. What differs is everything underneath the EVM: the gas token is USDC, finality is deterministic and sub-second, and the consensus engine is new. This guide sorts what transfers, what's different, and what deserves a test before you rely on it.
What does EVM-compatible actually mean here?
The Ethereum Virtual Machine is the runtime that executes smart contracts. A chain that implements it faithfully can run any contract compiled for Ethereum and speak to any tool that talks the standard JSON-RPC protocol. Arc does both. In practice that means the entire Ethereum stack — languages, wallets, dev frameworks, libraries, indexing patterns — treats Arc as just another network entry, which is precisely why Uniswap, Aave, Aerodrome, and Morpho could commit to being live on Arc at day one: their contracts deploy substantially as-is.
What works without modification?
Contracts and languages. Solidity compiles and deploys unchanged. ERC-20, ERC-721, and the standard interfaces behave as they do on Ethereum. If you want to see it firsthand, the developer quickstart gets a contract on testnet in minutes.
Wallets. MetaMask, Ledger, and Binance Wallet all support Arc at launch — it's added like any custom EVM network (setup guide).
Developer tooling. Foundry, Hardhat, ethers.js, viem — standard tooling works against Arc's RPC (testnet: rpc.testnet.arc.io, chain ID 5042002). The explorer, Arcscan, plays the Etherscan role (how to use it).
Infrastructure. Chainlink is among Arc's day-one integrations, so the oracle patterns you already use are available.
What's different under the hood?
Gas is USDC. No native gas token to acquire, no volatile fee math — fees are quoted and paid in dollars, with testnet transactions averaging around $0.004. This is Arc's signature trait and it changes the economics of using the chain more than any code (gas fees explained).
Native USDC has 18 decimals. The one genuine code-level trap. Anywhere you've assumed USDC means 6 decimals, native Arc USDC will surprise you — it occupies the ETH slot with ETH's decimal convention. The full gotcha guide is required reading before you port payment logic.
Finality is deterministic and sub-second. Arc runs the Malachite consensus engine and finalizes in roughly 780ms. There are no reorgs to design around and no confirmation-count heuristics — final means final. Exchange deposits, payment confirmation flows, and anything that waits N blocks can be simpler on Arc.
Opt-in confidential transfers. Arc offers privacy features built for regulated finance — opt-in, not default. This has no impact on standard contract behavior but expands what's possible for institutional use cases.
What should you test anyway?
Compatibility claims are strongest at the contract layer and get softer toward the edges. Before mainnet (September 16, 2026), run these on testnet: any code that hardcodes token decimals or gas assumptions; monitoring and indexing pipelines, which may make block-time assumptions; and wallet UX, since some wallets cosmetically mislabel the native USDC balance as "ETH." The testnet guide covers faucet funds and first transactions. Mainnet parameters are MAINNET-TBD until launch day — build your configs to swap them in rather than hardcoding anything you'll regret.
Why does compatibility matter this much?
Because it collapses Arc's switching cost to near zero at exactly the moment the chain's distinctive properties — dollar-denominated fees, sub-second finality, validators like BlackRock, Visa, and Mastercard — are pulling serious projects in. A chain with novel properties and a novel programming model asks developers to bet twice. Arc asks them to bet once. For token creators the same logic applies: the audited contracts Team Finance has deployed for 40,000+ projects across 26 chains work on Arc as-is, so minting and locking on Arc inherits years of battle-testing rather than starting from scratch. If you're starting from zero, what is Arc gives the full picture.
FAQ
Can I deploy my existing Ethereum contract on Arc without changes? Almost always yes — Solidity and the EVM behave identically. The exception worth auditing: logic that assumes USDC has 6 decimals, since native Arc USDC has 18.
Does MetaMask work on Arc? Yes — MetaMask is a day-one Arc wallet. You add Arc as a network like any EVM chain; testnet chain ID is 5042002.
Is Arc a Layer-2 on Ethereum? No. Arc is an independent Layer-1 built by Circle. It shares Ethereum's execution environment but has its own validators and its own consensus engine, Malachite.
Do Hardhat and Foundry work with Arc? Yes — point them at Arc's RPC and deploy as usual. No plugins or forks required.
Which major apps are live on Arc at launch? Day-one apps include Uniswap, Aerodrome, Aave, Morpho, Chainlink, and Team Finance, with wallet support from MetaMask, Ledger, Binance Wallet, and Fireblocks.
Put the compatibility to work — create your token on Arc with Team Finance's audited ERC-20 contracts, live on Arc from day one.Open Team Finance →Sources: docs.arc.network, arc.io, Circle pressroom. Compatibility and consensus details verified against Arc documentation, August 2026.
Last verified: August 2026