Indexed Akash NetworkBlockchain Data

Akash Network has run a public mainnet since 2020, and it sells computing capacity rather than block space. Validators run a Tendermint BFT protocol under proof of stake, AKT is the native token in uakt denominations, and accounts are bech32 strings with an akash prefix. The chain is a market rather than a platform for applications. A tenant publishes a deployment describing the resources it wants, providers answer with bids in a reverse auction, the tenant accepts one and that creates a lease, and the lease is paid from an escrow account that settles as blocks are produced. Providers are identified by certificates and by audit attestations signed by third parties, so provider identity is itself a chain record. Containers themselves run on the providers’ own hardware. The network operates today under its second chain identifier, which is where any long history has to start.

SonarX indexes the marketplace as the chain records it: blocks and transactions with their typed messages, deployments and the resource groups inside them, bids and closed orders, leases and their state changes, escrow accounts and their settlement, provider certificates and audits, staking records, 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.

Money here does not move in transactions. A lease settles by drawing on escrow every block, so spend on compute is the difference between two heights rather than a payment anyone signed, and a cost series has to be accumulated across ranges instead of summed from transfers. The market side compounds that: most bids never become leases, so a large share of the records describe offers that moved no value at all, and treating them as activity overstates it. Leases also close for several reasons, an exhausted escrow among them, which makes lease duration a question about balances.

Provider revenue accounting is the first workload: what a provider earned per lease and per period, derived from escrow settlement rather than from invoices. Capacity market research is the second, reading bids against accepted leases to see what resources actually cleared and how the spread between asking and winning bids behaved, which is much the same exercise as studying the block-space market on Celestia. Reward and delegation accounting is the third, and staking analytics covers that shape of work across chains. Tenant spend attribution is a fourth, and teams looking at networks that pay for physical work usually pull IoTeX 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. Akash Network coverage is provisioned on request, so tell us the history depth and the delivery target and we will scope it. Say whether the market side or the settlement side leads, 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.