Skip to main content
Arc uses USDC as its native gas token. For relayers and paymasters, this means your gas infrastructure runs entirely on USDC. Fund your signing account or paymaster contract with USDC and Arc handles the rest.

​
Choose your path

​
What you need

Before you start, confirm you have the following:

​
Arc behaviors relevant to this integration

The following Arc behaviors can affect relayer and paymaster operations. Each is covered in EVM differences:
  • PREVRANDAO always returns 0: If any contract in your stack uses PREVRANDAO for ordering or selection logic, it always reads 0 on Arc. Use an oracle or VRF instead. See Execution and opcode differences.
  • Blob transactions (EIP-4844 type-3) are rejected: Arc does not support type-3 transactions. Do not relay or route them. See Execution and opcode differences.
  • The next block’s base fee is published in extra_data: If you build custom gas-estimation tooling, read the next base fee from the parent header’s extra_data field (8-byte big-endian) rather than re-deriving it. See Fee market and block behavior.
  • Relay fees use 18-decimal precision: Native USDC (the gas token) has 18 decimals. Relay fees and paymaster charges are denominated in native USDC, not ERC-20 USDC (6 decimals).
  • EIP-7702 set-code transactions work on Arc: Arc’s Osaka baseline includes EIP-7702. EOAs can delegate execution to a contract by signing a type-4 authorization. Paymasters may receive UserOperations from EIP-7702-delegated accounts; the behavior is the same as for smart contract accounts.

​
Integration guides

Operate an EIP-3009 relayer on Arc

Submit gasless USDC transfers using a user’s transferWithAuthorization signature.

Deploy an ERC-4337 paymaster on Arc

Deploy and operate an ERC-4337 paymaster contract on Arc.