Indexed CantoBlockchain Data

Canto has produced blocks since its genesis on 26 July 2022. Its execution layer is an EVM provided by Ethermint on top of a Cosmos SDK consensus layer running Tendermint BFT under proof of stake, so Solidity contracts deploy unchanged while every account keeps a canto bech32 form and a twenty-byte hex form. CANTO is the native token, written acanto at eighteen decimals. Its core financial primitives ship as free public infrastructure: an exchange that charges liquidity providers nothing, a pooled lending market forked from Compound v2, and NOTE, a fully collateralized unit of account issued by that market and soft-pegged to the dollar. None of the three carries a governance token, so none can turn around and extract rent. Applications earn instead from a share of the gas their own contracts consume.

SonarX indexes both halves of this chain. On the EVM side that means blocks, transactions and receipts, logs decoded against contract ABIs, execution traces with their internal transfers, and token balances. Underneath sit the Cosmos records: typed messages, staking, IBC arrivals and the conversions the protocol performs on receipt. It is all normalized into the model SonarX uses across every network it covers, Evmos included.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. Balance tables and the balance APIs can be enabled for Canto on request.

Two mechanisms put records here that other EVM chains do not have. Gas revenue is attributed per contract and claimable by whoever registered it, so fee income is chain state rather than an inference from traces, and accrual and withdrawal are separate rows. The second is what happens to an arriving IBC transfer: if the recipient holds too little CANTO to pay for gas, the protocol swaps part of the incoming asset for some and converts the remainder into an ERC-20 representation. What arrived is therefore not what was sent, and one holding shows up in both a module balance and an ERC-20 balance.

Lending-market analytics is the first workload: collateral, borrow positions and liquidations read from decoded logs, against a market whose parameters are governed rather than sold. NOTE supply and peg work is the second, following issuance against the collateral behind it. Per-contract revenue accounting is the third and is specific to this chain, because gas income is recorded rather than estimated, which is also why teams comparing revenue-sharing designs pull Archway alongside it. Inflow attribution is a fourth, since an asset arriving over IBC can be part-swapped and re-presented as an ERC-20 before it ever reaches a contract, and a naive reading counts that twice. DeFi analytics covers position-level work of this kind across chains.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Canto history is available now, so a first delivery is provisioning rather than engineering. 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.