Validator Metadata
Validator metadata is stored on-chain and visible to delegators. Keep it current and professional.Viewing Metadata
Check your validator’s current metadata:- Name and description
- Image and project URLs
- Network addresses
- Public keys
- Gas price and commission
- Staking pool info
Updating Metadata
Some metadata changes take effect immediately, others at the next epoch. Immediate updates:- Name
- Description
- Image URL
- Project URL
- Network addresses
- Public keys (protocol, network, worker)
- Gas price
Metadata Update Commands
Update Name
Update Description
Update Image URL
Update Project URL
Update Network Address
Network address updates take effect at the next epoch. Ensure your node is accessible at the new address before the epoch boundary.
Update P2P Address
Update Protocol Public Key
When rotating the protocol key:Gas Price Management
Viewing Current Gas Price
Updating Gas Price
As a validator with Operation Cap:- Monitor network conditions
- Check other validators’ quotes
- Mainnet typical: 750-1,000 MIST
- Update during low-activity periods
Commission Management
Checking Current Commission
Updating Commission Rate
For active validators:- Communicate changes to delegators in advance
- Consider market rates (typically 2-10%)
- Changes take effect next epoch
- Don’t change too frequently
Peer Reporting
Validators can report peers for malicious behavior.Reporting a Validator
Undoing a Report
- Only report for legitimate protocol violations
- Document reason for report
- If 2f+1 validators report, target is slashed
- False reporting can damage reputation
Operation Cap Management
What is Operation Cap?
Operation Cap allows delegation of validator operations without exposing the main validator account key. Operations enabled:- Update gas price
- Report validators
- Undo validator reports
Viewing Operation Cap
Transferring Operation Cap
Delegate operations to another account:Rotating Operation Cap
Invalidate current cap and create new one:- Compromised operator account
- Changing operational team
- Security policy updates
Committee Management
Joining the Committee
After becoming a candidate and accumulating minimum stake:Leaving the Committee
To voluntarily leave the validator set:- Submit leave request
- Remain active until next epoch
- Removed at epoch boundary
- Staking pool becomes inactive
- Delegators can withdraw
- Extended maintenance (>24 hours)
- Hardware migration
- Voluntary exit from validation
Becoming a Validator
For new validators joining the network.Step 1: Generate Validator Info
validator.infofile with metadata- Copies keys from your sui.keystore
- Name, description, URLs
- Public keys (protocol, network, worker, account)
- Network addresses
- Initial gas price
- Proof of possession
Step 2: Become Candidate
Step 3: Accumulate Stake
As a candidate:- Start your fullnode to sync with the network
- Accept self-stake and delegations
- Promote your validator to attract delegators
- Reach minimum stake requirement
Step 4: Join Committee
Once minimum stake reached:Offline Signing
For enhanced security, sign validator transactions offline.Supported Operations
become-candidatejoin-committeeleave-committeeupdate-metadataupdate-gas-pricereport-validator
Offline Signing Process
1
Generate unsigned transaction
2
Sign on offline machine
3
Execute signed transaction
Multisig Operations
For multisig validator accounts:Monitoring Validator Status
On-Chain Status
Node Health
Performance Metrics
Track validator performance:Common Operational Tasks
Daily Checks
Weekly Tasks
- Review performance metrics
- Check for software updates
- Verify backup completion
- Review validator ranking
- Analyze delegator changes
Monthly Tasks
- Review commission rate competitiveness
- Analyze reward trends
- Capacity planning review
- Update validator website/documentation
- Community engagement
Best Practices
Operational Excellence
- Maintain high uptime: >99.5% availability
- Monitor actively: Set up alerts for critical issues
- Update promptly: Apply updates within 24-48 hours
- Communicate clearly: Keep delegators informed
- Document changes: Maintain operational log
- Test before production: Use testnet for new procedures
Security
- Protect keys: Use HSM or secure offline storage
- Use Operation Cap: Separate operational and financial keys
- Regular audits: Review access logs and configurations
- Principle of least privilege: Limit access to essential personnel
- Incident response plan: Document procedures for compromises
Delegator Relations
- Transparency: Publish regular performance reports
- Communication: Announce maintenance and changes
- Competitive commission: Research market rates
- Professional presence: Maintain website and social media
- Support: Respond to delegator questions