Indexed BahamutBlockchain Data

Bahamut is an EVM Layer 1 whose consensus, Proof of Stake and Activity, adds a usage term to ordinary staking. A contract’s activity is the sum of the gas users spend interacting with it, and a validator’s ranking is set by its stake together with the activity of the contracts it deployed, so the chances of validating and the rewards earned both move with real usage. Every validator posts the same stake, 8,192 FTN, which removes stake size as a differentiator; rewards accrue up to that same effective balance and anything above it is withdrawn automatically. The native asset is FTN, and it pays for gas. Execution is account-based over twenty-byte addresses with the standard token interfaces, so Solidity contracts and their artifacts deploy unchanged, and the network answers to chain ID 5165.

SonarX indexes Bahamut blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances, in the normalized model used on every chain SonarX covers.

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

Gas per contract is a consensus input here rather than a derived metric, so receipts have to be attributed to the contract that consumed them and not only to the transaction that paid. Internal calls make that harder than it sounds: gas spent inside a call to another contract belongs to a different account than the one the transaction was addressed to, so the attribution comes out of traces rather than out of the receipt alone. Validator standing then moves with those totals rather than with deposits, so a reward series only makes sense next to a contract-usage series for the same period.

Validator and reward accounting is the workload this design creates, and it is unusual: explaining a validator’s income means reading the gas its contracts consumed, not just the blocks it produced. Contract usage analysis is the second job and serves the same question from the application side, since a team here has a direct interest in how much gas its own deployments attract. Position-level DeFi analytics is the third, built from decoded events with internal transfers attached. Teams studying unconventional validator incentives usually read this chain beside Flare and Core.

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.