Developer insights

Indexing and Simulating Arc Correctly

November 17, 2026
3
min read
November 17, 2026
3
min read

Summary

‍

Arc keeps the JSON-RPC surface and signing model familiar for infrastructure teams. Providers, explorers, indexers, and data platforms can continue to work with Ethereum-style addresses, secp256k1 signatures, EIP-1559 transactions, and standard block and receipt queries.

These assumptions can pass local tests while leaving gaps that surface on the network. An API may label native units as ETH, an indexer may watch only the ERC-20 contract, or a local fork may omit Arc’s execution rules.

Start with familiar EVM infrastructure

Arc does not support EIP-4844 blob transactions, and PREVRANDAO returns 0. Native balances are USDC at 18-decimal precision rather than ETH. Fee fields retain the EIP-1559 shape, while Arc’s fee market applies its own smoothing model.

The Infrastructure integration overview and Index Arc events guide outline the integration path. The sections below focus on the protocol behaviors that affect an RPC-backed data pipeline.

The system event stream covers native USDC movements

Arc emits an EIP-7708 Transfer from the system emitter for every native USDC movement. The stream covers plain native sends, contract endowments, SELFDESTRUCT value transfers, and the native leg of ERC-20 activity. It uses 18-decimal values. Gas fees and block rewards are not part of this event stream.

The ERC-20 USDC contract emits its own Transfer for ERC-20-interface activity. That creates two records for one transfer() call:

Movement Emitter(s) Precision
Plain native send System emitter 0xffff…fffe 18 decimals
ERC-20 transfer() System emitter and USDC contract 18 and 6 decimals

Two indexing footguns follow from that event model: filtering only the ERC-20 USDC contract misses native sends, and treating both emitters as separate movements double-counts every ERC-20 transfer().

Use the system emitter as the canonical native-movement stream, match on emitter when both logs appear, and keep eth_getBalance as a balance query rather than another set of Transfer records. Current emitter addresses, event signatures, and mint/burn mapping are in USDC system events.

Native accounting can retain the system event's 18-decimal value. When a pipeline normalizes it to the 6-decimal USDC unit used for product analytics, it divides by 1012:

const OFFSET = 12n;

function toSixDecimals(nativeValue: bigint): bigint {
  return nativeValue / 10n ** OFFSET;
}


Historical backfills need one additional boundary. Before Zero5, Arc Testnet emitted legacy NativeCoin* events instead of the EIP-7708 system Transfer. After Zero5, the EIP-7708 model applies; mainnet uses that model from genesis. Backfill rules and the legacy emitter live in the same USDC system events reference.

Make the pipeline's unit model explicit

The raw interfaces use two decimal scales. A pipeline can retain native logs at 18 decimals and normalize product analytics to 6-decimal USDC. eth_getBalance and system Transfer.value require division by 1012. ERC-20 Transfer.value and balanceOf already use 6 decimals. Gas price multiplied by gas used produces a native fee value that must be converted to USDC for display.

Mixing raw 18- and 6-decimal values in one metric changes the result by a factor of 1012. Keeping the raw value, the normalized value, and the conversion rule at ingestion prevents downstream consumers from having to infer which scale they received.

Local simulation does not cover every Arc rule

Anvil, Foundry, and generic local forks are useful for ordinary EVM tests. They do not, by themselves, reproduce Arc's native-coin precompiles, EIP-7708 event emission, USDC blocklist enforcement, or Arc-specific value-transfer rules.

Cases that depend on those behaviors are better tested against Arc Testnet at https://rpc.testnet.arc.io (chain ID 5042002). A passing local fork alone does not show that the pipeline handles Arc-specific behavior. Refer to the Value transfer rules section for the native-coin, precompile, and blocklist behavior that local forks do not model.

Fee market, ordering, and finality

Arc keeps EIP-1559 transaction fields and applies EWMA smoothing to the base fee. Backend systems can use eth_gasPrice for a simple estimate or eth_feeHistory when they need recent fee history. Gas accounting is denominated in native USDC units at 18 decimals, so labeling those values as ETH can misstate the asset and unit.

Sub-second blocks can share a timestamp. (blockNumber, logIndex) therefore provides a more reliable ordering key than block.timestamp, and ingestion capacity may need to account for bursts of many blocks per second.

Finality is deterministic on inclusion. Once a transaction is included in a committed block, it is final, so Arc pipelines can omit Ethereum-style confirmation buffers, reorg rollback, and uncle handling. The Deterministic finality reference explains the consensus model behind this guarantee.

Infrastructure validation checklist

  • Balance and fee APIs label USDC, not ETH
  • The indexer subscribes to the system emitter and deduplicates ERC-20 transfers
  • Decimal transforms are documented and tested (18 ↔ 6)
  • Tests cover plain native sends and ERC-20 transfers, including the dual-emitter path
  • Simulation and CI include Arc RPC cases for precompiles, EIP-7708, and blocklist behavior
  • Ordering uses block number and log index
  • Confirmation policy treats one committed block as final
  • Zero5 and mainnet-genesis event models are understood for historical backfills

Explore open-source Arc apps built with Circle developer tools, from payments and FX to DeFi, wallets, and treasury flows.

Arc mainnet is an open L1 blockchain launched and offered by Arc Network Services LLC (“Arc LLC”) and operated by a permissioned validator set. Arc testnet is offered by Circle Technology Services, LLC (“CTS”). Arc LLC and CTS are software providers only and do not provide regulated financial or advisory services. Neither the Arc mainnet nor testnet has been reviewed or approved by the New York State Department of Financial Services or any other regulatory authority.

The Arc network is provided “as is” and “as available.” Use of Arc involves inherent risks associated with blockchain technology, including smart contract vulnerabilities, network disruptions, and the absence of recourse for transaction errors or losses. The ability to transact on Arc depends on the ability to obtain and use USDC to pay gas fees. Neither Arc LLC nor any permissioned validator is responsible for the content, accuracy, legality, or functionality of third-party applications, protocols, or services built on or integrated with Arc.

You are solely responsible for any features or services you provide to users, including obtaining any necessary licenses or approvals and otherwise complying with applicable laws. All Arc features may be modified, delayed, or cancelled at any time without notice and, where applicable, at the sole discretion of Arc LLC or CTS. Nothing herein constitutes a commitment, warranty, guarantee, or legal, regulatory, tax, or investment advice.

Contents