Indexed Immutable zkEVMBlockchain Data

Immutable zkEVM is an Ethereum Layer 2 built for games, live on mainnet since 2023. It is EVM-equivalent and was built with Polygon’s zkEVM technology, so Solidity contracts, twenty-byte addresses and the ERC-20, ERC-721 and ERC-1155 standards behave as they do on Ethereum, and state updates settle there behind zero-knowledge validity proofs instead of a fraud-proof window. Blocks are produced by a sequencer the network operates rather than by an open validator set. Gas is paid in IMX, the token Immutable already used on its earlier network, and that earlier network is the source of most confusion about this chain: Immutable X, launched in 2021, is a StarkEx validium with no EVM and a different record shape. IMX itself originates as an ERC-20 on Ethereum and is bridged in to pay for gas here. Activity on the chain is game economies rather than trading, which means minting, item transfers and marketplace settlement.

SonarX indexes Immutable zkEVM end to end: blocks and headers, transactions and receipts, event logs decoded against contract ABIs, execution traces, and token transfers, collections and balances. The same normalized model is used on every chain SonarX covers, so one game’s economy and a wallet’s holdings elsewhere are answered from the same shapes.

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 Immutable zkEVM on request. Kafka streaming can be enabled for Immutable zkEVM on request.

The machinery is standard here; the workload is not. Item-level ownership rather than account balances is what analysts ask for, and an ERC-1155 batch transfer carries arrays of token ids and amounts inside one event, so a single log can move hundreds of items and has to be expanded before holdings can be counted. Royalties are also enforced onchain rather than by marketplace convention: every ERC-721 and ERC-1155 collection has to implement an operator allowlist, and a transfer called by a contract outside that list reverts. Player transactions are often relayed as well, which means the sending address is an operator and the item’s owner has to be read from the transfer itself.

Studios and the funds that back them ask different questions of the same records. Economy analysis is the first: how many items were minted against how many were burned or consumed, and what that does to the floor of a collection over a season. Holder concentration is the second, which needs ownership restated per item and per account rather than per transfer. Marketplace settlement and royalty flows are the third, following a sale from the trade to the payout. Player-account analysis is a fourth, since a studio usually wants activity attributed to a person across several games rather than to one address in one title. Token-level work such as supply and distribution analysis runs through tokens and payments, and teams comparing NFT-heavy networks usually pull ApeChain alongside this one.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. 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.