Indexed Cosmos HubBlockchain Data

The Cosmos Hub has produced blocks since March 2019, and it is the first chain built with the Cosmos SDK rather than a general platform for contracts. Validators run CometBFT, the Tendermint BFT engine, under proof of stake: a committed block is final at once, so there is no confirmation depth to wait out and no reorg to unwind. ATOM is the native token, divisible into a million uatom, and it pays fees and secures the chain through delegation, with a bonded position released twenty-one days after unbonding begins. Accounts are bech32 strings carrying a cosmos prefix. The Hub runs SDK modules rather than a contract VM, so activity here is transfers, delegation, governance and packet routing instead of bytecode execution. Inter-Blockchain Communication, the protocol that turned a set of sovereign chains such as Osmosis into a network, arrived with the Stargate upgrade in early 2021. Since 2023 the Hub has also leased its validator set to other chains.

SonarX indexes the Hub’s history: blocks, transactions and the typed messages inside them, module events, delegation and reward records, governance proposals and votes, IBC packets with the denominations they carry, and derived account balances. Everything is normalized into the model SonarX uses across every network it covers, so a Cosmos question and a question about an EVM chain are asked in one query language.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request.

A transaction here is a container rather than a single action: one signed transaction can carry several typed messages that all succeed or fail together, so counting transactions and counting transfers give different answers. Events are attribute pairs emitted by protocol modules, not logs decoded against an ABI, which makes decoding a schema problem instead of a bytecode one. Rewards are the awkward part, because delegation rewards accumulate as fractional state in the distribution module and only become a transaction when somebody withdraws them, so an income series has to be rebuilt from state that was never a transfer.

Reward and delegation accounting is the first workload, and it is the reason most institutions arrive: a staking position’s income has to be derived per epoch from module state, per validator, with commission netted, and auditors ask for it in exactly those terms. Staking analytics covers that shape of work across chains. Interchain flow analysis is the second, following value across IBC channels to see which chains actually trade with each other rather than which ones are connected. Governance research is the third, since proposals, deposits and votes are recorded on chain and read as a history of decisions. Custody reconciliation runs underneath all of it, and teams usually pull Celestia or another SDK chain into the same warehouse to close the counterparty side.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Hub history is available now as a share or a file delivery, and streaming is provisioned on request. If the question spans several Cosmos chains, say so early, because the scoping is different. 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.