Indexed EvmosBlockchain Data

Evmos was a Cosmos SDK Layer 1 that ran an EVM. Its mainnet opened in 2022, halted within days when a bug was found, and restarted from a fresh genesis weeks later, which is why a complete history spans two chain identifiers. Validators ran a Tendermint BFT protocol under proof of stake, EVMOS was the native token written aevmos at eighteen decimals rather than the six most Cosmos chains use, and every account had an evmos bech32 address and a twenty-byte hex address derived from one key. Solidity contracts deployed, logs decoded against their ABIs, and a token-pair module let one balance be held either as a bank denomination or as an ERC-20. The network no longer produces blocks: governance voted to shut mainnet down, so the chain’s history is complete and fixed.

SonarX indexes the chain in both of its shapes: blocks and headers, transactions and receipts, event logs decoded against contract ABIs, execution traces with internal value transfers, token transfers and balances, and the Cosmos records beside them, from typed messages and staking to IBC transfers and the conversions between a denomination and its ERC-20 view. All of it is normalized into the model SonarX uses across every network it covers, Canto included.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request.

Two genesis events and a closed end make this an unusual backfill. The first mainnet ran for days before it was stopped, so the earlier chain identifier is a separate and very small dataset that most analyses can skip deliberately rather than by accident. Within the long run, the token-pair module is the trap: one balance can be held as a bank denomination or as an ERC-20 view of itself, and converting between them is a protocol action rather than a transfer, so counting both views double counts supply. Address duality does the same to holders, since one key appears as bech32 and as twenty bytes.

Close-out accounting is the first workload and the most common: a fund or a desk that held positions here still owes an auditor a defensible record of them, and the chain is no longer available to query in the usual ways. Wind-down tracing is the second, following what left over IBC and where it went, which is a question about counterparty chains as much as this one. Research on a completed lifecycle is the third, because a chain with a start, a peak and an end is a rare full sample for anyone studying how EVM activity behaves in a Cosmos setting, and Nibiru offers the live comparison. DeFi analytics covers contract-level work across chains.

Tell us the delivery target and how far back you need, and the share is scoped against that. Evmos coverage is provisioned on request, so tell us the history depth and the delivery target and we will scope it. Say whether the first, short-lived chain identifier is in scope, because most requests only want the long run. 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.