Indexed Polygon zkEVMBlockchain Data

Polygon zkEVM opened as a mainnet beta in March 2023 and was a validity rollup: transactions were ordered into batches by a sequencer, an aggregator produced a zero-knowledge proof that the batch had executed correctly, and a contract on Ethereum verified that proof. Settlement rested on mathematics rather than on a challenge period, which is what separated the design from an optimistic rollup. The virtual machine ran EVM bytecode, so twenty-byte addresses, Solidity contracts and existing tooling carried over, with a short list of opcode and precompile differences. Gas was paid in ETH. The chain was built with the Polygon CDK, the same toolkit behind X Layer, and it was always a different network from Polygon PoS: separate chain ID, separate validator arrangement, separate history.

Polygon has since sunset that sequencer, and the chain no longer produces blocks.

SonarX indexes blocks and headers, transactions and receipts, event logs decoded against contract ABIs, execution traces including internal value transfers, and token transfers and balances. The same normalized model is used on every chain SonarX covers, so Polygon zkEVM records line up with Polygon PoS and Ethereum records in one query rather than three schemas.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. The real-time balances API and the batch wallets, tokens and balances API are available for Polygon zkEVM, and the rest can be enabled on request. Kafka streaming can be enabled for Polygon zkEVM on request.

State on this chain arrived in stages, and an indexer that ignored the difference published numbers that later moved. The sequencer’s trusted state was readable straight away, the batch data then reached Ethereum, and the state settled only when the validity proof for that batch was verified. Rows taken from the trusted tip could still be reorganized, so SonarX reconciles the indexed history against the proven state rather than treating first publication as final. Reconstruction from L1 is unusually uniform here: batch data was posted as calldata for the whole of the chain’s life, so there is one encoding to handle and no blob retention window to race.

Most requests are now retrospective, and a bounded history suits that. Exit and balance reconstruction is the first: stating what an address or a fund held at a given block, and what happened to it, which is a point-in-time question rather than a monitoring one. Cross-network accounting is the second, since assets moved between Polygon PoS, Ethereum and the rollup, and a bridge flow only balances when every leg sits in the same warehouse. Research is the third, and this chain is a rare complete case study: a validity rollup’s entire life, from first batch to last, is available for work on proving costs, settlement lag and user retention that normally has to be done on a moving target. Position-level DeFi analytics runs on the same indexed tables.

Tell us the delivery target and how much of the history you need, and the share is scoped against that. The record is complete rather than growing, 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.