Indexed Arbitrum NovaBlockchain Data
Arbitrum Nova is the AnyTrust chain in the Arbitrum family, built for high-volume low-value activity, where a committee signs for transaction data instead of posting it to Ethereum.
How to query Arbitrum Nova data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Arbitrum Nova 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 — on request
Used for:
- Analytics teams already on Snowflake that want Arbitrum Nova 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 Arbitrum Nova 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 requestEvent stream
Consume Arbitrum Nova 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 Arbitrum Nova activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on Arbitrum Nova 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
Balances
Enabled on requestTables and REST
Read what a Arbitrum Nova 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 Arbitrum Nova 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 Arbitrum Nova balances on page load
- Compliance checks that read one Arbitrum Nova 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 requestREST over the indexed dataset
Query indexed Arbitrum Nova 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 Arbitrum Nova data behind their own API layer
Arbitrum Nova data: frequently asked questions
What is Arbitrum Nova?
Arbitrum Nova is an EVM chain that has been live since August 2022, running the same Nitro stack as Arbitrum One and settling on Ethereum. What separates the two is data availability. Nova runs AnyTrust: a committee of known members signs certificates stating that the transaction data is available, and only those certificates go to Ethereum. If the committee fails to sign, the chain falls back to posting data on Ethereum as an ordinary rollup does. Gas is paid in ETH and ARB plays no part in fees. Execution is the Nitro EVM, so contracts and twenty-byte addresses behave as they do on Arbitrum One, and the network answers to chain ID 42170 rather than 42161. It was built for activity that is high in volume and low in value per transaction, which is why games and social applications settled here.
Arbitrum Nova data on SonarX
SonarX indexes Nova end to end: blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances. Deposits and retryable tickets stay identifiable instead of being flattened into ordinary transactions.
Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. Balance tables and the balance APIs can be enabled for Arbitrum Nova on request. Kafka streaming can be enabled for Arbitrum Nova on request.
How SonarX indexes Arbitrum Nova
The committee is the thing to plan around. Because only availability certificates reach Ethereum, a Nova archive assembled from L1 data has gaps it cannot detect. Two block numbers run here as they do across Nitro, one counted by the chain and one approximating Ethereum’s, so a time series has to say which it means. The fee model matters for interpretation too: transactions are cheap enough that applications write activity onchain that would be kept off it elsewhere, so decoded logs carry the meaning rather than value transfers.
What teams build with Arbitrum Nova data
Application analytics is the first workload, because the chain’s traffic is application traffic: counting actions per contract, per account and per item, from decoded logs rather than from transfers. Bridge and flow reconciliation is the second, since assets reach Nova through Arbitrum One and Ethereum and a position statement has to match all three sides. Cost comparison is the third and is specific to this pair: running the same contracts on Nova and on Arbitrum One prices the difference between an AnyTrust chain and a rollup that publishes every byte. Token distribution work sits on tokens and payments, and teams surveying the family usually pull Xai in beside it.
Getting Arbitrum Nova 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. Nova history is available now, indexed from the chain rather than reconstructed from Ethereum. 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 Arbitrum Nova data API?
Real-time and batch APIs over indexed Arbitrum Nova 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 Arbitrum Nova 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 Arbitrum Nova coverage go?
The historical data-share and file delivery cover the chain from its 2022 launch forward, and are available today. Because Nova publishes availability certificates to Ethereum rather than its transactions, that history is indexed from the chain itself, which is the only complete source for it.
How is Arbitrum Nova different from Arbitrum One?
They share the Nitro stack and the EVM, and differ on where transaction data lives. Arbitrum One publishes its data to Ethereum. Nova uses AnyTrust, where a committee attests that the data is available and only the attestation is posted, which makes transactions cheaper and the trust assumption different. They are separate networks with separate chain IDs, separate state and separate datasets.
Can an Arbitrum Nova history be rebuilt from Ethereum?
Not on its own. Only availability certificates and settlement records reach Ethereum, so a pipeline that derives an L2 history from L1 data comes up short here. SonarX indexes the chain directly, which is why the dataset carries transactions, receipts and decoded logs rather than the attestations that stand in for them.
