Infrastructure Integration

Arc is an EVM-compatible blockchain, so standard Ethereum tooling works out of the box. However, several architectural differences affect how infrastructure providers index data, stream blocks, and expose balance APIs.

​

Key differences from Ethereum

​

Chain metadata

Additional RPC endpoints are available through Blockdaemon, dRPC, and QuickNode.

​

Integration considerations

​

Balance APIs

eth_getBalance returns the account’s native balance in USDC at 18-decimal precision. If your platform displays balances, label the value as USDC rather than ETH. The same underlying balance is also accessible through the ERC-20 interface at 6-decimal precision.

​

No-reorg indexing

Arc’s deterministic finality means you never need to handle chain reorganizations or uncle blocks. Every block your indexer receives is permanent. You can treat a single block confirmation as final and skip reorg-recovery logic entirely.

​

Sub-second block streaming

Blocks arrive faster than once per second. Your ingestion pipeline must handle high-throughput streaming without assuming a minimum interval between blocks. Multiple consecutive blocks may share the same block.timestamp because sub-second blocks can fall in the same wall-clock second.

​

Randomness

PREVRANDAO always returns 0. If your tooling surfaces this opcode value, note that it does not provide randomness on Arc.

​

Self-hosted access

For independent verification or direct RPC access without third-party providers, you can run your own Arc node. The execution client (arc-node-execution) is Reth-based, and the consensus client (arc-node-consensus) is Malachite-based.

​

Sub-pages