Indexed InjectiveBlockchain Data

Injective has produced blocks since November 2021, and it is an appchain with a single purpose that it approached from the opposite side of market structure to Osmosis. Validators run a Tendermint BFT protocol under proof of stake and INJ is the native token. The exchange is a module in the chain rather than a contract on it, so spot and derivatives markets, the order book, matching, positions and funding are all protocol state. Orders do not clear one at a time: the orders resting in a market are settled in a batch auction that gives every fill the same clearing price, a design chosen to make front-running unprofitable rather than merely expensive. CosmWasm contracts run beside the exchange for everything the module does not do. Accounts carry an inj prefix in bech32 and the same twenty bytes written as a hex address, because the chain uses Ethereum-style keys. Fees collected across applications are pooled and auctioned periodically for INJ, which is then burned.

SonarX indexes the chain and the venue together: blocks and transactions with their typed messages, order-book activity and fills from the exchange module, derivative positions and funding, CosmWasm contract activity, bridged and IBC denominations, staking records, and derived balances. Everything is normalized into the model SonarX uses across every network it covers, so exchange records here join to positions held elsewhere.

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

An order book that lives in the protocol emits no trade logs, so fills are read from the module’s own state transitions. The batch auction catches people out: many fills in one market clear together at a single price, so a fill is not the child of a transaction and a trade count taken from transaction rows will not match the venue’s own. Derivatives carry state that no transfer records, because funding accrues against open positions and insurance funds absorb shortfalls. Identity cuts the other way, since an account’s bech32 address and its hex form are the same twenty bytes and belong to one holder.

Market-structure research is the first workload and the most natural: order-book depth, fill distribution under a uniform clearing price, funding and basis series, and liquidation clustering studied across the venue rather than sampled. Risk and collateral monitoring is the second, tracking open positions against insurance-fund coverage through periods of stress. Supply accounting is the third and is specific to this chain, because the periodic auction removes INJ from circulation, so issuance and burn have to be netted from chain records instead of read off a published figure. DeFi analytics covers the contract side across chains, and desks comparing onchain venues usually pull Hyperliquid alongside it.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Injective coverage is provisioned on request, so tell us the history depth and the delivery target and we will scope it. If the work is market-level rather than account-level, say so, because the two are scoped differently. 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.