Committee Management

​

Committee Overview

• Active validators: Currently participating in consensus
• Candidate validators: Registered but not in active set
• Pending validators: Will join in next epoch
• Leaving validators: Will exit in next epoch

​

Committee Size

• Mainnet: ~100-150 validators
• Testnet: ~50-100 validators
• Dynamic: Size can change through governance

​

Epoch System

​

Epoch Duration

• Mainnet: 24 hours
• Testnet: Typically 24 hours (may vary)
• Devnet: Often shorter for testing

​

Epoch Boundaries

1. Reward distribution occurs
2. Committee membership updates
3. Metadata changes take effect
4. Staking changes activate
5. New epoch begins

​

Checking Current Epoch

# Query current epoch
curl -X POST http://localhost:9000 \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "suix_getLatestSuiSystemState",
    "params": []
  }' | jq '.result.epoch'

# Via CLI
sui client call --package 0x3 --module sui_system \
  --function get_current_epoch \
  --args 0x5

​

Committee Selection

​

Selection Criteria

1. Minimum stake: Must meet or exceed minimum requirement
2. Stake ranking: Higher stake increases probability of selection
3. Committee size limit: Only top validators by stake are selected
4. Active status: Must not be in leaving or slashed state

​

Stake-Weighted Selection

• Higher chance of inclusion in active set
• Greater voting power in consensus
• Larger share of rewards

​

Checking Committee Membership

# List all active validators
sui client call --package 0x3 --module sui_system \
  --function get_validators \
  --args 0x5

# Check if specific validator is active
sui validator display-metadata <address> | grep "active"

• Suiscan Validators
• SuiVision Validators

​

Joining the Committee

​

Prerequisites

1. ✅ Complete validator setup
2. ✅ Register as candidate
3. ✅ Accumulate minimum stake
4. ✅ Fully sync node with network
5. ✅ Verify all ports accessible
6. ✅ Test node performance

​

Registration Process

sui validator make-validator-info \
  "Validator Name" \
  "Description" \
  "https://example.com/logo.png" \
  "https://example.com" \
  "validator.example.com" \
  1000

sui validator become-candidate validator.info

sui validator display-metadata

sui validator display-metadata | grep "total_stake"

sui validator join-committee

​

Activation Timeline

Time 0:00  - Submit join-committee request
Time 0:00  - Status: Pending Validator
Time 24:00 - Epoch boundary
Time 24:00 - Status: Active Validator
Time 24:00 - Begin consensus participation

​

Leaving the Committee

​

Voluntary Exit

sui validator leave-committee

• Remain active until next epoch
• Removed at epoch boundary
• Staking pool becomes inactive
• Stop earning rewards
• Delegators can unstake

​

Exit Timeline

Time 0:00  - Submit leave-committee request
Time 0:00  - Status: Leaving Validator
Time 24:00 - Epoch boundary
Time 24:00 - Status: Inactive Candidate
Time 24:00 - Staking pool deactivated

​

Involuntary Removal

1. Insufficient stake: Falling below minimum
2. Slashing: Byzantine behavior reported by 2f+1 validators
3. Inactivity: Extended downtime or non-participation

​

Validator States

​

State Transitions

Not Registered
      |
      v
  Candidate ←→ Active Validator
      ↑            |
      |            v
      └──── Inactive/Slashed

​

Candidate

• Registered validator
• Not in active set
• Can accept stake
• Can join committee if sufficient stake

sui validator display-metadata | grep "pending"

​

Active Validator

• In current committee
• Participating in consensus
• Earning rewards
• Can be delegated to

• Maintain node uptime
• Participate in consensus
• Process transactions
• Submit gas price quotes

​

Pending Validator

• Requested to join committee
• Will activate next epoch
• Should ensure node is ready

• Verify node fully synced
• Confirm all ports accessible
• Monitor for epoch boundary
• Ready to start consensus

​

Leaving Validator

• Requested to leave committee
• Still active current epoch
• Will deactivate next epoch

• Complete current epoch normally
• Communicate with delegators
• Prepare for deactivation

​

Inactive/Slashed

• Removed from committee
• Not earning rewards
• May have reduced stake (if slashed)

• Address removal cause
• Restore stake if needed
• Rejoin as candidate
• Request committee membership

​

Committee Operations

​

Voting Power

Voting Power = Validator Stake / Total Committee Stake

Validator stake: 50M SUI
Total committee stake: 2B SUI
Voting power: 50M / 2B = 2.5%

• More influence in consensus
• Higher rewards potential
• Greater responsibility

​

Consensus Participation

1. Propose blocks: When elected as leader
2. Vote on proposals: Participate in each round
3. Sign certificates: Validate transactions
4. Maintain state: Keep synced with network

# Check consensus metrics
curl -s http://localhost:9184/metrics | grep -E \
  "current_round|committed_subdags|consensus_votes"

​

Quorum Requirements

• 2f+1 stake: For quorum (f = faulty validators)
• Byzantine fault tolerance: Tolerates up to f failures
• Liveness: Requires >2f+1 honest validators

• f = 33M stake can be faulty
• Quorum = 67M stake needed
• Safety maintained if less than 33M stake byzantine

​

Stake Management

​

Monitoring Total Stake

# Check your validator's stake
sui validator display-metadata | grep -E "total_stake|self_stake"

# Check minimum requirement
sui client call --package 0x3 --module sui_system \
  --function get_min_validator_stake \
  --args 0x5

​

Stake Changes

1. Delegations: New delegations activate
2. Unstaking: Withdrawal requests complete
3. Rewards: Automatically added to stake
4. Slashing: Penalty applied if reported

​

Self-Stake Management

# Add self-stake
sui client call --package 0x3 --module sui_system \
  --function request_add_stake \
  --args 0x5 <stake-coin-object>

# Request unstake
sui client call --package 0x3 --module sui_system \
  --function request_withdraw_stake \
  --args 0x5 <staked-sui-object> <amount>

​

Validator Ranking

​

Ranking Factors

1. Total stake: Primary ranking factor
2. Performance: Uptime and participation
3. Commission rate: Lower can attract more delegation
4. Reputation: Track record and reliability

​

Checking Rankings

• Suiscan Rankings
• SuiVision Rankings

curl -X POST http://localhost:9000 \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "suix_getValidatorsApy",
    "params": []
  }' | jq '.result.apys | sort_by(.apy) | reverse'

​

Delegation Dynamics

​

Attracting Delegations

1. Performance history: Uptime and participation
2. Commission rate: Competitive pricing
3. Stake size: Indicator of trust/success
4. Reputation: Community standing
5. Communication: Transparency and updates

​

Managing Delegations

• Monitor delegation changes
• Communicate with delegators
• Maintain transparency
• Provide regular updates
• Announce changes in advance

​

Delegation Limits

• Very high stake may centralize network
• Voting power caps may apply through governance
• Consider network health

​

Governance Participation

​

Proposal Voting

• Protocol upgrades
• Parameter changes
• Network policies
• Economic parameters

​

Voting Weight

Vote Weight = Validator Total Stake / Network Total Stake

​

Best Practices

1. Stay informed: Follow governance discussions
2. Review proposals: Understand implications
3. Vote actively: Participate in governance
4. Communicate: Share voting rationale with delegators
5. Consider delegators: Votes affect their stake too

​

Committee Health

​

Monitoring Committee

# View committee size
curl -X POST http://localhost:9000 \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "suix_getValidatorsApy",
    "params": []
  }' | jq '.result.apys | length'

# Check stake distribution
curl -X POST http://localhost:9000 \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "suix_getLatestSuiSystemState",
    "params": []
  }' | jq '.result.activeValidators | map(.stakingPoolSuiBalance)'

​

Decentralization Metrics

• Nakamoto coefficient: Minimum validators for 33% stake
• Geographic distribution: Validator locations
• Client diversity: Node software variations
• Stake distribution: Concentration vs. distribution

​

Emergency Procedures

​

Committee Disruption

1. Check validator health
2. Monitor Discord announcements
3. Review logs for errors
4. Contact other validators
5. Follow emergency procedures

​

Fork Scenarios

• Follow official guidance
• Do not modify configuration without instruction
• Coordinate with other validators
• Wait for resolution from Mysten Labs

​

Best Practices

​

Committee Participation

1. Maintain readiness: Keep node healthy and updated
2. Monitor actively: Watch for epoch transitions
3. Communicate clearly: Inform delegators of changes
4. Plan ahead: Coordinate maintenance with epochs
5. Stay informed: Follow network updates

​

Operational Standards

1. High availability: >99.5% uptime
2. Fast updates: Apply within 24-48 hours
3. Active monitoring: 24/7 alerting
4. Backup systems: Redundancy for critical components
5. Documentation: Maintain operational procedures

​

Resources

​

Monitoring Tools

• Sui Explorer
• SuiVision
• Sui Metrics

​

Documentation

• Validator Operations
• Staking and Rewards
• Validator Requirements