Staking Overview
Sui uses a delegated proof-of-stake (DPoS) mechanism where:- Validators operate nodes and participate in consensus
- Delegators stake SUI tokens with validators
- Rewards are distributed based on stake and performance
- Epochs define reward distribution periods (24 hours on mainnet)
Validator Stake
Stake Components
Validator stake consists of:- Self-stake: Validator’s own SUI tokens
- Delegated stake: SUI delegated by token holders
- Total stake: Self-stake + delegated stake
Minimum Stake Requirements
To join the active validator set:- Mainnet: ~30 million SUI
- Testnet: ~1 million SUI
Minimum stake requirements may change through governance. Always verify current requirements before attempting to join.
Checking Validator Stake
View your validator’s stake:Reward Mechanisms
Reward Sources
Validators earn rewards from:- Computation fees: Gas fees from transaction execution
- Storage fees: Fees for on-chain data storage
- Stake subsidies: Network-issued rewards (decreases over time)
Reward Calculation
Rewards are calculated based on:Epoch-Based Distribution
Rewards are distributed at epoch boundaries:- Epoch duration: 24 hours (mainnet), varies on testnet
- Distribution time: Automatic at epoch change
- Claiming: Rewards are automatically compounded
Commission Structure
Setting Commission Rate
Validators charge commission on delegated stake rewards:Commission Calculation
Commission is calculated on delegator rewards:Updating Commission
For active validators:Delegation Management
Accepting Delegation
As a validator candidate or active validator, you automatically accept delegations. Delegators can stake with you through:- Sui Wallet
- CLI commands
- dApps and exchanges
Delegation Flow
- Delegator stakes SUI with your validator
- Stake activates at next epoch boundary
- Rewards accrue each epoch
- Auto-compounding: Rewards are automatically re-staked
Maximum Delegations
There is no maximum delegation amount. However:- Higher total stake increases validator rewards
- Very high stake may require more resources
- Voting power is capped to prevent centralization
Gas Price Oracle
Validators participate in the gas price oracle by submitting quotes:Setting Gas Price Quote
Gas Price Considerations
- Too low: May not cover operational costs
- Too high: Reduces network competitiveness
- Market-based: Monitor network conditions and adjust
- Mainnet: 750-1,000 MIST
- Testnet: 1,000 MIST
Reward Monitoring
Tracking Validator Rewards
Query validator rewards:Validator APY
Check annual percentage yield:Reward History
Track historical performance:Performance Impact on Rewards
Participation Requirements
Validators must:- Maintain uptime: >99% availability
- Participate in consensus: Vote on blocks
- Process transactions: Execute transactions correctly
- Stay synced: Keep up with network checkpoints
Performance Penalties
Poor performance results in:- Reduced rewards: Missing consensus rounds reduces epoch rewards
- Tallying score impact: Low participation affects validator score
- Risk of slashing: Byzantine behavior may result in stake slashing
- Reputation damage: Delegators may withdraw stake
Slashing Conditions
Validators can be slashed for:- Equivocation: Signing conflicting messages
- Byzantine behavior: Malicious actions reported by 2f+1 validators
- Protocol violations: Breaking consensus rules
Operation Cap
What is Operation Cap?
Operation Cap is a capability object that allows delegating validator operations:- Update gas price: Without using validator account key
- Report validators: Submit peer reports
- Operational flexibility: Separate hot/cold key management
Managing Operation Cap
Check current Operation Cap:Withdrawal and Unstaking
Delegator Unstaking
Delegators can unstake at any time:- Unstake request submitted
- Stake remains active until next epoch
- Funds available after epoch boundary
Validator Leaving
To remove your validator:- Submit leave request
- Remain active until next epoch
- Removed from active set at epoch boundary
- Staking pool becomes inactive
- Delegators can withdraw stake
Reactivating Validator
After leaving, to rejoin:Best Practices
For Validators
- Competitive commission: Research market rates (typically 2-10%)
- Transparent communication: Announce changes in advance
- High uptime: Maintain >99.5% availability
- Regular updates: Keep node software current
- Performance monitoring: Track participation metrics
- Delegator relations: Build trust through reliability
For Delegators
When choosing validators, consider:- Performance history: Check uptime and participation
- Commission rate: Balance cost with validator quality
- Total stake: Ensure validator meets minimum
- Reputation: Research validator’s track record
- Communication: Active, transparent operators
Reward Optimization
Maximizing Validator Rewards
Strategies:- Maintain high uptime: Participate in all consensus rounds
- Optimize commission: Attract delegation without reducing profitability
- Build reputation: Transparent communication and reliable operation
- Marketing: Promote validator to attract delegators
- Performance: Ensure infrastructure meets demands
Cost-Benefit Analysis
Monthly costs (example):Actual rewards vary based on network conditions, validator performance, and total network stake. This is a simplified example.
Governance Participation
Validators participate in network governance:Voting Power
Based on total stake (self-stake + delegated):Governance Rewards
Participating in governance may provide:- Additional rewards for voting
- Influence over protocol parameters
- Say in network upgrades
Tax and Accounting
Record Keeping
Maintain records of:- Epoch rewards received
- Commission earned
- Operating expenses
- Stake changes
- Commission rate changes
Tax Considerations
Considerations:- Rewards may be taxable when received
- Commission is typically ordinary income
- Operating costs may be deductible
- Jurisdiction-specific regulations apply