Indexed GnosisBlockchain Data
Gnosis Chain prices gas in xDAI, a bridged stablecoin, and secures an EVM Layer 1 with GNO staked one token at a time, which keeps its validator set unusually wide.
How to query Gnosis Chain data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Gnosis Chain 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 Gnosis Chain 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 Gnosis Chain 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 Gnosis Chain 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 Gnosis Chain activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on Gnosis Chain 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
Available todayPurpose-built tables
Protocol-level Gnosis Chain datasets modelled for one job, so the decoding and the joins are done before the data reaches you.
- DeFi
Used for:
- Position-level Gnosis Chain 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 Gnosis Chain share with a modelled slice
Balances
Enabled on requestTables and REST
Read what a Gnosis Chain 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 Gnosis Chain 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 Gnosis Chain balances on page load
- Compliance checks that read one Gnosis Chain 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
Available todayREST over the indexed dataset
Query indexed Gnosis Chain 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 Gnosis Chain data behind their own API layer
Gnosis Chain data: frequently asked questions
What is Gnosis Chain?
Gnosis Chain has produced blocks since 2018, when it launched as the xDai Chain, and it took its current name in 2022. It answers to chain ID 100, targets five-second blocks, and runs the EVM with the same twenty-byte addresses, receipts and event logs as Ethereum. Two things make it unusual. Gas is paid in xDAI, a stablecoin bridged from DAI, so the native currency of the chain is dollar-denominated rather than volatile. And GNO, not xDAI, is the asset that secures it: a validator is registered with one GNO rather than a large stake, which is why the validator set is unusually wide. Consensus itself lives on a separate chain, indexed as Gnosis Beacon Chain, and took over block production at the merge on 8 December 2022, replacing the proof-of-authority system the chain ran before that.
Gnosis Chain data on SonarX
SonarX indexes Gnosis Chain 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 a Gnosis Chain query and an Ethereum query take the same shape.
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 Gnosis Chain on request. Kafka streaming can be enabled for Gnosis Chain on request.
How SonarX indexes Gnosis Chain
The unit of account is the first thing to get right. Native value here is a stablecoin, so a fee column is already in dollars and any pipeline that converts it again, or ranks it beside a volatile gas token, reports nonsense. The second is that the history has two halves: blocks before December 2022 were produced under proof of authority and carry different consensus fields from the ones after it, and staking records live on the beacon side rather than in execution blocks.
What teams build with Gnosis Chain data
Payment-flow analysis is the first workload and the one the fee model suits, because the cost of a transfer and the transfer itself are denominated in the same dollar-pegged unit, so a cost-per-payment series needs no exchange rate. Token analytics is where that work sits across the networks SonarX indexes. Bridge and supply reconciliation is the second, since xDAI in circulation is backed by DAI locked elsewhere and only balances when both sides are counted. Validator and reward accounting is the third, and it spans two datasets by design. Community and DAO treasury reporting is the fourth, which on this chain means resolving many small contract-held positions rather than a few large ones.
Getting Gnosis Chain 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. Gnosis Chain history is available now, and it is worth saying whether consensus records are in scope as well. 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 a Gnosis Chain data API?
Yes. A real-time API over indexed Gnosis Chain data is available today, reading the same indexed dataset as the Snowflake share. The balances and batch APIs are enabled on request, so tell us the lookup pattern you need and we will confirm what is possible.
How do I get Gnosis Chain 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 Gnosis Chain coverage go?
The historical data-share and file delivery cover the chain's recorded history from its 2018 start as the xDai Chain forward, and are available today. That history crosses a change of consensus in December 2022, so blocks either side of it were produced by different systems, and continuity across the boundary is part of what gets checked when the share is scoped.
Is Gnosis Chain the same as Gnosis Safe?
No. Gnosis Chain is the network this page covers, the EVM chain that used to be called the xDai Chain. Safe, the smart-contract wallet system that began as Gnosis Safe, is a separate product deployed on many chains, and its contracts on this network are indexed here like any others. GNO is the token used for staking and governance rather than for gas.
How are Gnosis Chain fees recorded when gas is a stablecoin?
In the native currency field, which on this chain happens to hold a dollar-pegged asset. xDAI arrives by bridging DAI, so a fee is already denominated in dollars and a cost series needs no price join to be readable. The trap is comparison: treating that column as a volatile gas token, or converting it a second time, produces figures that are wrong by whatever the reference asset did that day.
