Summary
This analysis covers the proposed assets for the initial V4 listing on Arc, specifically cross-chain assets already listed on Aave instances. This review provides an overview of key aspects, including chain-specific characteristics, bridging infrastructure, contract implementations, access control, liquidity, and other risk-related factors.
The key findings include that access control across all contracts, including both assets and bridge contracts in scope, relies on EOAs with keys held under Circle’s enterprise-grade key management program, which they claim maintains SOC 2 Type 2 attestation and follows NIST frameworks across the infrastructure. Further, no timelocks gate sensitive contract upgrades, consistent with Circle’s operational model for USDC, EURC, and cirBTC on other networks. For privileged roles, different assigned addresses were observed across the contracts, with no reassignments recorded.
WETH has a different implementation as it is not natively minted on Arc, with its backing escrowed on Ethereum. Its owner and pauser slots remain unclaimed, meaning no party can currently modify its privileged roles or pause the token. However, the Cross Chain Token Service (CCTS) retains ownership assignment authority and can resolve the unclaimed state at any time. The WETH token and the bridge minter contracts for cirBTC, EURC, and WETH, represented by their respective TokenManager contracts, are beacon proxies that do not pin their own implementation and instead resolve it through the CCTS singleton at call time. Consequently, the CCTS owner can replace the implementation for all of these contracts on the chain in a single action. Additionally, WETH has no native blacklist and instead inherits the blacklist functionality of Arc USDC.
Bridge rate limits are also implemented for each asset via their respective bridge minter contracts.
Comparative table
| Asset | Issuance | Bridge Verifier Setup | Rate Limits | Token Upgradeable |
|---|---|---|---|---|
| USDC | Native mint & bridgeable via CCTP | CCTP (burn/mint), 2/2 attester set. | Per-account limits via Circle Mint: Account-specific, Per-transfer limit via TokenMinterV2: 10M USDC | Yes (via FiatTokenProxy owner) |
| EURC | Native mint & bridgeable via CCTPx | Circle Mint, permissioned mint/redemption and CCTPx (burn/mint), uses underlying CCTP 2/2 attester messaging. | Per-account limits via Circle Mint: Account-specific, Per-transfer limit via TokenManager: 862K EURC, Per six-hour limits via TokenManager: Inbound/Outbound 4.31M EURC | Yes (via FiatTokenProxy owner) |
| cirBTC | Native mint & bridgeable via CCTPx | Circle Mint, permissioned mint/redemption and CCTPx (burn/mint), uses underlying CCTP 2/2 attester messaging. | Per-account limits via Circle Mint: Account-specific, Per-transfer limit via TokenManager: 9 cirBTC, Per six-hour limits via TokenManager: Inbound/Outbound 135 cirBTC | Yes (via FiatTokenProxy owner) |
| WETH | Bridged via Circle’s new CCTPx protocol | CCTPx (lock/mint), escrowed on Ethereum, uses underlying CCTP 2/2 attester messaging. | Per-transfer limit via TokenManager: 500 WETH, Per six-hour limits via TokenManager: Inbound/Outbound 2,500 WETH | Yes (via the Cross Chain Token Service beacon and the token’s own owner slot is unclaimed) |
The full assessment for each asset can be found in their corresponding threads:
Disclaimer
This review was independently prepared by LlamaRisk, a DeFi risk service provider funded in part by the Aave DAO. LlamaRisk is not directly affiliated with the protocol(s) reviewed in this assessment and did not receive any compensation from the protocol(s) or their affiliated entities for this work.
The information provided should not be construed as legal, financial, tax, or professional advice.