Staking
Staking
BNB Smart Chain (BSC) staking data provides comprehensive information about validator operations, delegator activities, and staking rewards on the BSC network. This data set includes daily snapshots of delegator balances, staking events, validator creation records, and reward distributions.
Available Tables
Table | Description |
---|---|
bsc.staking.delegator_balances_daily | Daily snapshots of delegator balances for each validator |
bsc.staking.events | All staking-related events including delegations, undelegations, and claims |
bsc.staking.stake_credit_balances | Real-time balances of stake credit tokens for each delegator-validator pair |
bsc.staking.validator_creation | Records of validator creation events |
bsc.staking.validator_rewards | Records of rewards distributed to validators and their delegators |
Overview of BSC Staking
BNB Smart Chain’s Proof of Staked Authority (PoSA) consensus mechanism relies on validators who stake BNB tokens to secure the network, validate transactions, and produce blocks. The staking mechanism includes:
- Validators: Node operators who stake a minimum required amount of BNB to validate transactions and produce blocks
- Delegators: Token holders who stake their BNB with validators to earn a portion of rewards without running validator infrastructure
- Stake Credit Tokens: Tokens representing delegator stakes with specific validators
- Rewards: BNB tokens earned by validators and delegators for their participation in network consensus
Common Identifiers
Several identifiers are used consistently across these tables:
- Operator Address: The validator’s management address (
operator_address
) - Consensus Address: The validator’s block validation address (
consensus_address
) - Delegator Address: The staker’s wallet address (
address
ordelegator_address
) - Credit Contract: The validator’s stake credit token contract address (
credit_contract
orstake_credit_address
)
Block Information
All tables include standard block information:
block_timestamp
: Timestamp of the relevant blockblock_number
: Block numberblock_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.