Indexed GonkaBlockchain Data
Gonka is a Cosmos SDK network for decentralized AI compute, where hardware hosts earn rewards for running AI workloads and the chain records the accounts, transfers and messages that coordinate them.
How to query Gonka data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Gonka 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 Gonka 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 Gonka 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
Realtime API
Enabled on requestREST over the indexed dataset
Query indexed Gonka 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 Gonka data behind their own API layer
Gonka data: frequently asked questions
What is Gonka?
Gonka is a network for decentralized AI compute. Hardware hosts contribute processing power to run AI workloads, and the network rewards that work in its native token instead of rewarding hashing that produces nothing else. The chain itself is built on the Cosmos SDK with CometBFT consensus: it runs its own validator set and its own state, and it records the accounts, token transfers and module messages that coordinate hosts, workloads and rewards.
Gonka data on SonarX
SonarX indexes Gonka blocks and block results, transactions including failed ones, the events every block and transaction emits, decoded transaction messages, and token transfers priced and netted by account. Tokens carry their metadata, so amounts read in the units holders see. The same normalized model covers every network SonarX indexes, so Gonka can be joined to other Cosmos SDK chains in one query.
Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request.
How SonarX indexes Gonka
A Cosmos SDK block changes state in more places than its transactions. Each transaction carries one or more messages, and the modules that handle them write what happened as events. The chain also emits events at the start and end of every block, which is where rewards and other automatic state changes appear. SonarX indexes block results and block-level events alongside transactions, so those changes are not lost, and it keeps failed transactions, since a failed message still costs fees and still says something about the account that sent it.
What teams build with Gonka data
Reward analysis is the first workload: what the network paid out and which accounts received it. Token flow tracking is the second, following rewards from host accounts to exchanges and other holders. Network activity research is the third, reading transactions, failures and fees over time to see how the network is used. Wallet analytics covers account-level reporting across chains, and Cosmos Hub is a common second dataset.
Getting Gonka 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. Gonka history is available now, and real-time delivery is provisioned on request. 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.
What Gonka data does SonarX index?
SonarX indexes Gonka blocks and block results, transactions including failed ones, the events each block and transaction emits, decoded transaction messages, and token transfers priced and netted by account. Tokens are carried with their metadata so amounts read in the units holders see.
How do I get Gonka 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.
Is Gonka a Cosmos chain?
Gonka is built on the Cosmos SDK, so its blocks, transactions and events follow the Cosmos model and are indexed with the same structure SonarX uses for other Cosmos SDK networks. It runs its own validator set and its own state rather than living inside the Cosmos Hub.
Why do Gonka events matter more than transactions?
Because the state change is in the events. On a Cosmos SDK chain a transaction carries messages, and what actually moved, minted or changed hands is written as events by the modules that handled them, plus events emitted at the start and end of each block. Reading transactions alone misses rewards and other changes the chain applies on its own.
Is Gonka an EVM chain?
No. Gonka does not run the Ethereum Virtual Machine. Accounts, messages and events follow the Cosmos SDK model, with bech32 addresses rather than Ethereum hex addresses, so Gonka data is modeled as a Cosmos network.
