Indexed XaiBlockchain Data
Xai is the Arbitrum Orbit AnyTrust chain built for video games, not the artificial intelligence company with a similar name, and it charges gas in XAI while settling through Arbitrum One.
How to query Xai data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Xai 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 Xai 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 Xai 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 Xai 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 Xai activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on Xai 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 Xai 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 Xai 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 Xai balances on page load
- Compliance checks that read one Xai 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 Xai 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 Xai data behind their own API layer
Xai data: frequently asked questions
What is Xai?
Xai is an Arbitrum Orbit chain built for video games, live since 2024, and it is not the artificial intelligence company with a similar name. It settles through Arbitrum One rather than posting to Ethereum directly, which puts two settlement hops between a transaction and L1 finality. Data availability follows Arbitrum’s AnyTrust design: a committee attests that the transaction data is available, and the attestation rather than the data travels upward. Gas is paid in XAI, the network’s own token, so fees are not denominated in ETH. Execution is the EVM, with twenty-byte addresses and the usual token standards, and the network answers to chain ID 660279. Its security arrangement is built around staked operators, and the games deployed on it write item ownership and in-game actions to the chain as contract state.
Xai data on SonarX
SonarX indexes Xai blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token and item transfers with balances. Collection records stay attached to their issuing contracts.
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 Xai on request. Kafka streaming can be enabled for Xai on request.
How SonarX indexes Xai
Game traffic and a committee-held data layer set the terms here. Most of what happens is contract calls and item transfers rather than value moving between addresses, so the meaning sits in decoded logs and a pipeline that follows native transfers sees almost nothing. AnyTrust is the second point: the transaction data stays with a committee and only its attestation is published upward, so a complete history is indexed from the chain rather than derived from Ethereum. And because settlement runs through Arbitrum One, a withdrawal has a leg on each of three networks, which is the path a bridge reconciliation has to walk.
What teams build with Xai data
Item and collection analysis is the first workload: mint and transfer histories restated per item, holder concentration inside a game, and secondary sales tracked against the contract that issued the asset. Player-account work is the second, where an address is a game account and the useful question is retention and progression measured from decoded events rather than from balances. Token accounting on XAI is the third, since the same token pays for gas, funds ecosystem programs and trades elsewhere. Studio-side reporting is the fourth: what a game’s contracts spent, minted and burned over a season. Distribution work runs through tokens and payments, and teams comparing gaming chains usually pull Immutable zkEVM alongside this one.
Getting Xai 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. Xai history is available now, with item-level transfers decoded rather than left as call data. 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 Xai related to xAI, the AI company?
No. They share a name and nothing else. Xai is a blockchain built on the Arbitrum Orbit stack for video games, with its own token and its own validator arrangement, and this page and dataset cover that chain only. Nothing here relates to the artificial intelligence company of a similar name, and no records in the dataset describe it.
Is there a Xai data API?
Real-time and batch APIs over indexed Xai 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 Xai 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 Xai coverage go?
The historical data-share and file delivery cover the chain from its 2024 launch forward, and are available today. Because the transaction data is held by a committee rather than published to Ethereum, that history comes from the chain itself, so depth is a question about this dataset rather than about what can be recovered from the L1.
