Indexed Gnosis BeaconBlockchain Data

This is the consensus layer of Gnosis Chain, and it keeps records of its own. It has produced blocks since 2021, ran alongside the proof-of-authority execution chain for about a year, and took over ordering that chain’s blocks at the merge on 8 December 2022. It runs the same Gasper design as Ethereum’s consensus layer, pairing Casper FFG finality with LMD-GHOST fork choice, but at its own parameters: five-second slots, sixteen slots to an epoch, so an epoch closes every eighty seconds. A validator is registered by depositing 32 mGNO, which is one GNO, through a deposit contract on the execution chain. This layer runs no virtual machine and stores no contract code. What it records is the validator registry, attestations, proposals, slashings, exits and withdrawal payments, keyed by validator index and BLS public key.

SonarX indexes the objects this layer produces: beacon blocks and their slots, the validator registry and every state change that moves a validator through it, attestations, deposits and exits, penalties, sync-committee duty and withdrawal payments. The same normalized model is used on every chain SonarX covers, so consensus records join execution records on the same height.

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

The denomination is the trap. Deposits are made in GNO and the beacon layer counts in mGNO at thirty-two to the token, so every balance, reward and penalty in these records carries a factor that has to be applied before a number means anything to an accountant. Second, funding and life are recorded on different layers: the deposit is an execution-layer transaction while activation, duty and exit are consensus records, so attributing a validator to whoever paid for it is a join across the two. Third, eighty-second epochs produce many more epoch rows per day than Ethereum’s.

Reward accounting is the first workload: what a validator was owed per epoch, what it received, and what the difference cost, restated in GNO rather than in the unit the chain counts in. Staking analytics is the solution area that work belongs to across networks. Penalty and participation research is the second, since missed attestations and slashings are the only public record of how an operator behaved under stress. Withdrawal reconciliation is the third and crosses both layers, because a payment reduces a validator balance here and appears as a credit there. Validator-set research is the fourth, since a one-GNO deposit produces a much wider set than a large minimum does. Ethereum Beacon Chain is the standard comparison.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Consensus history is available now, and it is worth saying whether execution records are in scope too. 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.