Indexed IoTeXBlockchain Data

IoTeX has produced blocks as its own Layer 1 since 2019, the year IOTX stopped being an ERC-20 and became the native token of the chain. Consensus is Roll-DPoS: delegates are elected by stake, a verifiable random function draws a committee from them each round, and that committee finalizes blocks under a PBFT vote. Execution is EVM-compatible, so Solidity contracts deploy unchanged and the chain’s fungible token standard, XRC-20, matches ERC-20 field for field. IoTeX was built for DePIN, the class of networks that pay for physical work such as sensing, mapping and wireless coverage. One property shapes every query against it: an account has a bech32 form beginning io1 and a twenty-byte 0x form, and both are the same keys. Token standards and contract shapes come from Ethereum, the identity model does not.

SonarX indexes IoTeX blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances. Native actions that move value without a contract call are indexed beside the EVM records.

Full historical coverage is provisioned for IoTeX on request. Balance tables and the balance APIs can be enabled for IoTeX on request. Kafka streaming can be enabled for IoTeX on request.

Two encodings of one account are the standing problem. Every address appears as io1 in native tooling and as 0x in EVM tooling, so a holder view built from one form alone splits a single owner in two, and both are normalized to one account before balances are derived. The second problem is that not everything is a contract call. Transfers, staking buckets and reward claims are typed native actions with their own payloads, so a history assembled from decoded logs would miss the value that never entered the EVM.

Reward accounting is the recurring workload, because delegation, epoch rewards and the release of matured buckets are protocol records a fund has to derive rather than read off a transfer log, and staking analytics is the solution area it belongs to. Token-flow analysis is the second, following XRC-20 assets and the bridged supply that arrived from Ethereum. Address-level research is the third, and it is where the two encodings matter most, since a study that treats io1 and 0x forms as separate wallets will double its population. Teams tracking networks that pay for physical or computational work usually pull Akash Network 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. IoTeX coverage is provisioned on request, so tell us the history depth and the delivery target and we will scope it. 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.