Indexed Kava CosmosBlockchain Data

Kava Cosmos is the Cosmos SDK co-chain of the Kava network, which has produced blocks since 2019. One validator set running a Tendermint BFT protocol under proof of stake produces one block, and that block advances both this co-chain and the EVM co-chain covered on Kava. KAVA is the native token in ukava units, and accounts are bech32 strings with a kava prefix. This side is where the network’s own financial modules live: an over-collateralized position mints USDX, the network’s native stablecoin, and separate lending and swap modules keep their own state with HARD and SWP as their governance assets. There is no contract VM here, so activity is typed messages against modules rather than bytecode execution. Assets that arrive from the EVM side carry a converted denomination on this one. The network has migrated through a long run of chain identifiers, and the current one is its tenth.

SonarX indexes this side of the network: blocks and transactions with their typed messages, collateral and debt positions and the liquidations against them, lending and swap module state, delegation and reward records, governance proposals and votes, IBC transfers with the denominations they carried, converted assets from the EVM side, and derived balances. Those records land in the normalized model SonarX uses on every network it covers.

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

Nothing on this side is a contract, and that is the first thing to plan for. USDX is minted against collateral locked in a module, borrow positions accrue as module state, and liquidations are performed by the protocol itself, so a position’s life has to be reconstructed from state that no transaction describes. Collateral ratios and liquidation thresholds are governance parameters that have moved over the chain’s life, so a solvency series has to be read against the settings in force at the time. Assets carried over from the EVM co-chain arrive under a converted denomination, so one token can be counted twice unless the two sides are netted.

Collateral and debt accounting is the first workload: positions, their collateralization through stress windows, and the liquidations that closed them, all derived from module state rather than from transfers. Stablecoin supply work is the second, following minting and repayment against the collateral backing it. Reward and delegation accounting is the third, and staking analytics covers that shape of work across chains. Cross-surface flow analysis is a fourth and is specific to this network, since capital moves between the co-chains without ever leaving it. Teams studying chains whose finance runs as protocol modules usually pull Osmosis into the same warehouse.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. This history is available now as a share or a file delivery, and streaming is provisioned on request. Say whether you need one co-chain or both, because that decides the scope. 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.