Skip to main content
Monad staking data provides comprehensive information about validator operations, delegator activities, and staking rewards on the Monad network. This dataset includes staking events, validator creation records, reward distributions, epoch transitions, and daily validator stake snapshots.

​
Available Tables

TableDescription
monad.staking.eventsAll staking events including delegations, undelegations, and withdrawals
monad.staking.validator_creationRecords of validator creation events
monad.staking.validator_rewardsRecords of rewards distributed to validators per epoch
monad.staking.rewards_claimedRecords of staking rewards claimed by delegators
monad.staking.epochsRecords of epoch transitions on the network
monad.staking.validator_commission_changesRecords of validator commission rate changes
monad.staking.validator_stake_dailyDaily snapshots of validator stake and commission state

​
Overview of Monad Staking

Monad uses a Proof of Stake consensus mechanism where validators stake MON tokens to secure the network, validate transactions, and produce blocks. The staking mechanism includes:
  • Validators: Node operators who stake MON to validate transactions and produce blocks. Each validator has a unique validator_id and an associated auth_address (authorization/operator address).
  • Delegators: Token holders who delegate their MON to validators to earn a portion of rewards without running validator infrastructure.
  • Epochs: Time periods of approximately 50,000 blocks (~5.5 hours) after which rewards are distributed and stake changes take effect.
  • Commission: Percentage of block rewards retained by validators before distributing to delegators.
  • Block Rewards: Validators receive 25 MON plus priority fees when they propose blocks.

​
Key Concepts

  • Epoch: A time period in Monad (~50,000 blocks or ~5.5 hours) after which stake changes activate and rewards are distributed
  • Validator ID: A unique integer identifier assigned to each validator by the Monad network
  • Auth Address: The validator’s authorization/operator address with control over the validator stake
  • Activation Epoch: The epoch when staking actions (delegate/undelegate) take effect

​
Common Identifiers

Several identifiers are used consistently across these tables:
  • Validator ID: Unique identifier for the validator (validator_id)
  • Auth Address: The validator’s authorization/operator address (auth_address)
  • Delegator Address: The staker’s wallet address (delegator_address)
  • Contract Address: The staking precompile contract address (contract_address)

​
Block Information

All tables include standard block information:
  • block_timestamp: Timestamp of the relevant block
  • block_number: Block number
  • block_hash: Hash of the block

​
Unique Identifiers

Each table includes a unique_id column that can be used as a primary key for the records.