Chain profile
Permissioned
Arc.
Abstract. Circle Internet Financial (sole Sequencer operator at launch; decentralization on roadmap)
Facts
Chain identity at a glance.
- Type
L2-optimistic
- Native settlement
- USDC (gas + settlement) · EURC (VERIFY parity with USDC on Arc at cutoff)
- Account model
- ERC-4337 account-abstraction · USDC-as-gas (paymaster semantics native to the chain rather than a third-party AA paymaster overlay)
Important — verify before relying
Show our work.
This profile carries inline VERIFY markers on
every field whose value depends on the model's recollection
rather than independent primary-source confirmation.
Renderers and compliance officers MUST verify each claim
against the operator's primary documentation before any
client-facing reliance.
Full discipline header — including sources,
architectural-distinctness narrative, and per-field VERIFY
inventory — at compliance/registries/chains/arc.ts.
Vendor stack · L5 → L1
The 5-layer Stable Stack.
Each row is one named vendor slot from the chain's vendorStack. Solid markers are code-enforced
(the chain blocks or signs); dashed markers are
policy-enforced (the chain flags, humans or systems act on
the signal).
L5 → L1 — application down to network
L5 · Application
wallet
Circle Smart Wallet · Circle Mint (issuer-facing surface · institutional onboarding)
C1C14 ◇ policy-enforced
payment-network
Circle Payments Network (CPN — institutional-payment orchestration over Arc and other Circle-supported chains)
C6C8 ◇ policy-enforced
compliance-pipeline
Circle Compliance Engine (sanctions · BSA/AML · OFAC SDN integration)
C2C3 ◇ policy-enforced
L4 · Account
account
Arc Smart Account (ERC-4337 account-abstraction · USDC-paid gas semantics)
C1 ◆ code-enforced
custody
Circle Mint custody (institutional · custody of USDC reserve issuance pipeline) · third-party institutional custodians (Anchorage · BitGo · Coinbase Custody)
C1 ◇ policy-enforced
L3 · Execution
swap
Arc DEX (native AMM primitive)
C13C16 ◆ code-enforced
sanctions-oracle
Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer)
C2 ◆ code-enforced
bridge
Circle CCTP v2 (canonical USDC cross-chain bridge — burn-and-mint model · regime-crossing primitive for USDC issuance across Arc, Ethereum, Base, Solana, and other CCTP-supported chains)
C7 ◆ code-enforced
confidential
Arc Confidential Transfers (opt-in transactional privacy — Circle has stated opt-in privacy but not publicly committed to a specific construction)
C15C16 ◆ code-enforced
L2 · Consensus
sequencer
Circle Sequencer (Circle-operated at launch · decentralization on roadmap · OP Stack-derived sequencing semantics)
C10 ◆ code-enforced
L1 · Network
da
Ethereum (via OP Stack) — Arc posts batch data to Ethereum for DA + finality anchoring; security inherits from Ethereum L1 subject to fault-proof activation status
◆ code-enforced
Fig. 1 —
Vendor slot per layer; solid border = code-enforced, dashed
border = policy-enforced.
Bridges supported
Cross-chain transport surface.
- CCTP v2 (canonical USDC burn-and-mint cross-chain transport)
- Circle Payments Network (CPN — institutional-payment overlay across Circle-supported chains)
Related paths
Paths that route through Arc.
Compliance paths whose settlementChains
include arc or whose steps execute
on this chain.
Source
Where the truth lives.
compliance/registries/chains/arc.ts —
full discipline header, sources, and per-field VERIFY
inventory live in the chain-profile source file. See the path resolver to see
this chain in a resolved compliance journey.
Explore the architecture
Pick a thread.