SonarX

Indexed ArcBlockchain Data

Arc is Circle's EVM-compatible Layer 1 for stablecoin finance. A proof-of-authority set of regulated institutions runs Malachite, a Tendermint-family BFT engine, so blocks reach deterministic finality in under a second, and USDC is the native gas token.

Arc logo

How to query Arc data with SonarX

Instant Data Share

Enabled on request

Snowflake, and file dumps to your object storage

Query Arc blockchain data with plain SQL from a live database inside your own Snowflake account, populated with the indexed chain dataset. There is no pipeline to build and no second copy to store. The same dataset ships as file dumps to your own object storage for lakes and warehouses that are not Snowflake.

  • Full history as a Snowflake data-share
  • File dumps to S3 or your own object storage
  • Real-time delivery, current to chain tip

Used for:

  • Analytics teams already on Snowflake that want Arc data beside their existing tables
  • Fund accounting and treasury reporting that reconciles against a fixed history
  • Cross-chain questions answered in one SQL statement instead of one query per chain
  • Loading Arc history into BigQuery, Databricks, Redshift or a Spark lake
  • Replacing a self-hosted indexer and the engineering time that keeps it running
  • Serving one governed dataset to several desks without copying it per team

Kafka Streaming

Enabled on request

Event stream

Consume Arc activity as a continuous stream of normalized records, produced as the chain is indexed instead of polled for.

Used for:

  • Trading and execution systems that act on Arc activity within seconds
  • Fraud and anomaly detection that has to fire before settlement
  • Live dashboards and alerting on Arc wallet or protocol activity
  • Feeding a stream processor that already reads from Kafka
  • Keeping an internal store hot without waiting for a batch window
  • Event-driven services that would otherwise poll on a timer

Curated Datasets

Enabled on request

Purpose-built tables

Protocol-level Arc datasets modelled for one job, so the decoding and the joins are done before the data reaches you.

  • DeFi
  • Staking
  • Tokens and payments
  • RWAs and tokenization

Used for:

  • Position-level Arc lending, swap and liquidity analysis
  • Reward, delegation and validator reporting without rebuilding the model
  • Token distribution, holder and payment-flow reporting
  • Risk and exposure work that needs protocol state, not raw logs
  • Skipping the decoding layer an in-house team would have to maintain
  • Extending an existing Arc share with a modelled slice

Balances

Enabled on request

Tables and REST

Read what a Arc address held, either as it stands now or exactly as it stood at a past block or timestamp.

  • Point-in-time balance tables, as at any block or timestamp
  • Real-time balances API for latest and historical balances
  • Batch API for wallets, tokens and balances in bulk

Used for:

  • Reconstructing Arc portfolios and NAV as at a reporting date
  • Audit and reconciliation work that has to be repeatable months later
  • Wallet and portfolio products that render Arc balances on page load
  • Compliance checks that read one Arc address at one block height
  • Refreshing holdings for a whole book of accounts on a schedule
  • Tax and cost-basis workflows that need holdings at each event

Realtime API

Enabled on request

REST over the indexed dataset

Query indexed Arc records over REST, reading the same dataset the share reads, with no warehouse in the path.

Used for:

  • Applications that need one answer rather than a table scan
  • Customer-facing screens where query latency is visible to a user
  • Services that have no data warehouse and do not want to run one
  • Prototyping against production data before committing to a share
  • Backend checks that run per request instead of per batch
  • Teams that want indexed Arc data behind their own API layer

Arc data: frequently asked questions

What is Arc?

Arc is Circle’s Layer 1 for stablecoin finance, described by Circle as an open blockchain network built for the world’s financial markets, real-time money movement and agentic economic activity. Public mainnet opened on 16 September 2026. It is EVM-compatible and runs Reth, a Rust implementation of the Ethereum execution client, so contracts written for Ethereum deploy unchanged and addresses, receipts and event logs take the shapes an EVM pipeline already reads. Underneath, the chain is unlike Ethereum. Consensus is Malachite, a high-performance implementation of the Tendermint BFT protocol, run by a proof-of-authority validator set composed of regulated institutions; the founding cohort announced alongside Circle includes BlackRock, DTCC, Galaxy, Global Payments, ICE, Mastercard, MoneyGram, SBI Group, Standard Chartered, Sumitomo Corporation and Visa. Finality is deterministic and instant: a transaction is final on inclusion, in under a second, with no reorganization risk. USDC is the native gas token, and a fee manager stabilizes gas fees using USDC as the unit of account, so the cost of a transaction is a dollar figure rather than a function of a volatile coin.

Arc data on SonarX

SonarX indexes Arc end to end: blocks and headers, transactions and receipts, event logs decoded against contract ABIs, execution traces including internal value transfers, and token transfers and balances. The same normalized model is used on every chain SonarX covers, so an Arc query and an Ethereum query take the same shape and join without a translation layer.

Historical coverage as a data-share or a file delivery, real-time delivery to chain tip, Kafka streaming, balance tables and the balance APIs are all enabled for Arc on request: tell us which surfaces you need and the share is scoped against that.

How SonarX indexes Arc

Two properties of Arc shape how its data is read. The first is the gas token. USDC on Arc is one balance behind two interfaces: a native interface with 18 decimals, used for gas and native value transfers, and an ERC-20 interface with 6 decimals. A dollar moved natively and a dollar moved as a token therefore carry different raw values, and a successful native transfer also emits a standard ERC-20 Transfer log from a system address, so the two views can be reconciled from the logs alone. The second is fees. The base fee is paid to the block beneficiary rather than burned, so fee flows appear as value received by validators instead of as supply leaving circulation. Arc targets the Osaka hard fork as its EVM baseline, with blob transactions unsupported and PREVRANDAO fixed at zero, which simplifies the block model relative to mainnet Ethereum.

What teams build with Arc data

Payments reconciliation comes first on a chain whose unit of account is the dollar: matching on-chain USDC movements, native and token, against ledgers held elsewhere, with sub-second finality meaning a settled transfer is settled. Tokenized-asset analytics is second. Circle’s launch partners include BlackRock deploying its BUIDL fund with native USDC, and DeFi venues such as Aave, Morpho and Uniswap, so holder registries, issuance and redemption flows and collateral usage are readable from decoded logs and traces together, the same way RWA tokenization work runs on other chains. Stablecoin FX and treasury flows are third, since Arc positions onchain FX between stablecoins as a core use. Comparisons against Tempo and other payment-first chains come up as teams decide where dollar settlement will live.

Getting Arc data from SonarX

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Arc history runs from the 2026 mainnet launch, so a first delivery is a matter of enabling the surfaces you need. The published coverage matrix for every network SonarX indexes lives in the data documentation, and the rest of the catalogue is at all indexed chains.

Is there an Arc data API?

Real-time and batch APIs over indexed Arc data are enabled on request: the same indexed dataset the Snowflake share reads, served over REST once provisioned. Tell us the lookup pattern you need.

How do I get Arc data into Snowflake?

SonarX provisions a data-share into your own Snowflake account. The share appears as a database you query with SQL, so there is no pipeline to build and no second copy to store, and it stays current as SonarX advances the indexing pipeline.

How far back does Arc coverage go?

The historical data-share and file delivery cover Arc's recorded history from its 2026 mainnet launch forward, and are enabled on request. Real-time delivery keeps the same dataset current to chain tip once provisioned.

How does USDC as gas change Arc data?

Two ways. USDC is exposed through two interfaces that share one balance, a native interface with 18 decimals and an ERC-20 interface with 6, so a native transfer and a token transfer of the same dollars carry different raw values and both need to be read. And the base fee is paid to the block beneficiary rather than burned, so fee accounting follows a different path from Ethereum.

Is Arc EVM-compatible?

Yes. Arc targets the Osaka hard fork as its baseline and supports EIP-7702 set-code transactions, so contracts, addresses, receipts and event logs take the shapes an EVM pipeline already reads. Documented differences include no blob transactions, PREVRANDAO always returning zero, and native value transfers emitting a standard ERC-20 Transfer log from a system address.

Arc logo

Get Arc data from SonarX