Skip to main content
Wallets on Arc use standard EVM tools: secp256k1 signing, EIP-1559 fees, and standard RPC methods. Arc’s USDC-native design requires changes to balance display, fee labels, transaction history, and approval handling.

​
Key differences for wallets

Three Arc design decisions affect every wallet integration:

​
Arc behaviors relevant to this integration

The following Arc behaviors can affect wallet operations. See the integration guides on this page and the EVM differences page for details:
  • Blocklist enforcement: Blocked senders are rejected before the transaction enters the mempool. Transfers that involve a blocked address during execution revert at runtime, using gas without changing state. Handle both cases in your UI. For details, see Transaction lifecycle.
  • Dust amounts: balanceOf() returns 0 for amounts smaller than 1×10⁻⁶ USDC (the 6-decimal minimum). The native balance can hold amounts smaller than that threshold (dust). Dust is still spendable as gas. A balanceOf() of 0 does not mean the address has no USDC.

​
What you need

Before you start, confirm you have the following:

​
Integration guides

Add Arc to a wallet

Chain configuration, balance display, transaction history, and fee handling for wallet providers.

Transaction lifecycle

Arc uses two states: pending or final. There are no intermediate confirmation states.

Display transaction fees

Fetch, estimate, and display transaction fees in USDC.