Arc

EVM Layer 1 / Chain ID 5042 / Private dataset

Arc is an EVM-compatible Layer 1 built by Circle that uses USDC as its native gas token, designed for payments, FX, and capital markets apps.

Website Explorer

Quick Facts

Access Private dataset

Runtime EVM

Chain ID 5042

Provisioning By request

Category Layer 1

Access: Private dataset
Networks: 1
Chain ID: 5042
Runtime: EVM
Provisioning: By request
License: Open-source SDK

Networks

arc-mainnet chain ID 5042

Real-time EVM mainnet by request

Arc on SQD

Validated at ingestion

Arc data is validated by SQD Network workers before it reaches the Portal. Validation is performed across the network rather than by a single ingestion node, so a faulty upstream source can't poison the dataset.

Decoded, schema-typed

Arc data served as decoded, schema-typed tables, ready to query. Your indexer queries the data directly without writing RLP parsers.

Archive plus real-time

Single Portal endpoint serves Arc from genesis through the current head, with sub-second hot-path latency. No separate streaming pipeline to wire up.

Open-source SDK

Both the Squid SDK and the Pipes SDK are open-source. Connectors for Postgres, ClickHouse, MongoDB, SQLite and Parquet, plus a custom-target hook. Run your Arc indexer on your own infrastructure or on SQD Cloud.

Build with Arc data

Common production patterns teams build with SQD on Arc.

DeFi & Trading

Index swaps, liquidations, and positions on Arc in real time.

Analytics

Build dashboards and metrics from full Arc historical state.

AI Agents

Give agents structured, decoded Arc data with the MCP server.

Wallets & Payments

Power balance, transfer, and history views for Arc wallets.

Compliance & KYT

Validated Arc data for transaction monitoring and audits.

Stablecoins

Track every mint, burn, and transfer of Arc stablecoins.

Real-World Assets

Auditable Arc data for tokenized RWA issuance and transfers.

Get access to Arc data

Arc is available to Enterprise customers via SQD Private Portal.

Talk to the team

Get Arc data on Private Portal. We'll reply with pricing and onboarding details.

Frequently asked questions

How does SQD compare to running an Arc RPC node?

An Arc RPC node serves raw bytes for recent state and rate-limits per request. SQD's Portal pre-indexes the full Arc archive into decoded, schema-typed tables (blocks, transactions, logs) and serves them as a single streaming endpoint. You skip the multi-day node sync, archive storage, monitoring, and scale-out work, and pay only for the data you stream.

What does SQD cost for Arc data?

Arc is available to Enterprise customers via SQD Private Portal. Contact us for pricing.

How is SQD's Arc data different from a block explorer like Etherscan?

Block explorers are read-optimized for human browsing of single blocks or addresses. SQD is built for programmatic indexing: stream millions of Arc blocks into your own database, run analytical queries across the full history, and back production applications with decoded data. Output is structured tables, not HTML pages, and there are no per-call rate limits geared toward UI traffic. If you wanted to build your own Arc explorer, the SQD Portal is what you would back it with.

Can I self-host SQD's Arc indexer?

Yes. Both the Squid SDK and the Pipes SDK are open-source. You can run an Arc indexer on your own infrastructure pointing at the SQD Network or the Portal. SQD Cloud also offers managed hosting if you'd rather not operate it yourself.

Can I export Arc data to a data warehouse or pipeline?

Yes. The Pipes SDK streams Arc data from the Portal into Postgres, ClickHouse, MongoDB, SQLite, Parquet, or a custom target you implement. See the SDK docs for the connector reference.

Does SQD validate Arc data?

Every Arc block ingested into SQD is validated by the SQD Network workers (hash chain, parent reference, and where applicable finality) before it reaches the Portal. Validation is performed across the network, not by a single ingestion process, so a faulty upstream node can't poison the dataset.

Does SQD support real-time Arc data?

Yes. Arc is served with both real-time and historical data from the same Portal endpoint, with sub-second latency on the hot path. No separate streaming pipeline to wire up.