Indexed ArchwayBlockchain Data

Archway has produced blocks since 2023, and its premise is that the applications on a chain should earn from the traffic they create. Validators run CometBFT under proof of stake, ARCH is the native token in aarch units at eighteen decimals rather than the six most Cosmos chains use, and accounts are bech32 strings with an archway prefix. Execution is CosmWasm: contracts compile to WebAssembly and there is no EVM here, so the token standards and address shapes an Ethereum team expects do not apply. What the chain adds underneath is an accounting layer. It meters the gas each contract consumes, credits a share of fees and of new issuance to a reward address the contract nominates, and lets contracts schedule callbacks, pay other accounts’ fees, and operate accounts on other chains over IBC.

SonarX indexes what the chain commits: blocks and transactions with their typed messages, contract instantiation and execution, per-contract gas consumption, reward accrual and withdrawal, scheduled callbacks and their outcomes, fee grants, governance records, staking and delegation, and derived balances. All of it is normalized into the model SonarX uses across every network it covers, including the Cosmos Hub whose modules this chain builds on.

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

Rewards are keyed by contract rather than by account, and that reshapes every query about income. The chain records gas consumed per contract, accrues a fee share and an issuance share to the address that contract nominated, and settles only when somebody withdraws, so accrual and payment sit at different heights and neither one alone is revenue. Two further features break common assumptions. A scheduled callback executes with no signer and no fee payer, so a state change can exist with nobody behind it. And a contract can pay for a user’s transaction, which separates sender from payer.

Contract revenue accounting is the first workload and the one the chain exists to support: what a deployment earned, over which periods, against the gas its users burned. Application analytics is the second, reading contract execution to see which flows drove that traffic in the first place. Fee-payer attribution is the third and is specific to this chain, because a contract sponsoring transactions makes cost per user a different question from cost per account. DeFi analytics covers contract-level work of this kind across chains, and teams comparing revenue-sharing designs usually pull Canto alongside it.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Archway history is available now as a share or a file delivery, and streaming is provisioned on request. Say which contracts matter, because scoping by contract beats taking the chain whole. 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.