Skip to main content
Arc is a stablecoin-native Layer-1 blockchain built by Circle, purpose-built for real-world financial applications. Arc uses USDC as its native gas token, achieves sub-second deterministic finality, and is fully EVM-compatible. More on Arc here.

Address derivation

Turnkey supports Arc address derivation with ADDRESS_TYPE_ETHEREUM. This address format is valid across the Arc network and is identical to standard EVM address derivation.

Transaction construction and signing

Because Arc is EVM-compatible, existing Ethereum tooling works on Arc without modification: We have an example that demonstrates how to construct and broadcast an Arc transaction:

Transaction management and gas sponsorship

Turnkey’s Transaction Management handles the full lifecycle of Arc transactions — construction, broadcast, nonce management, and status monitoring.

Gas sponsorship (fee abstraction)

Set sponsor: true to enable fee sponsorship — your users never need to hold USDC to pay gas. Turnkey covers fees on your behalf and passes costs through as a monthly line item.
To enable gas sponsorship, ensure it is activated in your Turnkey dashboard before setting sponsor: true.

Differences from standard EVM chains

A few Arc-specific behaviors are worth knowing when integrating with Turnkey:
  • USDC is the native gas token. ETH is not the native asset on Arc, so accounts need a USDC balance to transact. Native USDC uses an 18-decimal interface (standard msg.value semantics), while the ERC-20 interface on the same balance uses 6 decimals. To display a native value as USDC, divide by 1012. Don’t credit or record balances from the 6-decimal value: truncation at the 6-decimal boundary records less than was transferred.
  • Blob transactions (EIP-4844, type 3) are not supported. Turnkey supports signing type 3 transactions on Ethereum, but Arc’s mempool rejects them — use legacy, type 1, or type 2 transactions on Arc.
For the full list of protocol-level differences, see Arc’s EVM differences.

Transaction parsing, policies, and signing

Please refer to our Ethereum network page for details on transaction parsing, policies, and signing, as Arc shares the same EVM architecture. Turnkey’s EVM transaction parser, policy engine, and SIGN_TRANSACTION activity types all apply — including EIP-712 typed data signing.

Arc network support

Turnkey supports:

Benefits of using Turnkey with Arc

  • Secure key management: Private keys are securely stored in Turnkey’s enclave infrastructure
  • Policy controls: Apply custom policies to authorize transactions based on destination, value, calldata, and more
  • Developer-friendly: Integrate with existing EVM development workflows — ethers, viem, Foundry, Hardhat