Sui Validators
Sui uses a delegated proof-of-stake model where validators process transactions and maintain network consensus through Mysticeti, a Byzantine fault-tolerant consensus protocol. These guides are for operators who run validator nodes on the Sui network, and cover validator configuration, committee management, rewards, and operational best practices.
What do the validator guides cover?
Deployment and Configuration
Learn how to set up, configure, and manage a Sui validator node.
Management
Reference guide for ongoing Sui validator node operations, covering storage management, key management, metrics, logs, dashboards, software updates, state sync, and joining or leaving the validator set.
Tools
Use the Sui CLI to interact with a full node's validator commands.
Rewards
Learn how Sui calculates and distributes validator and staker rewards, how voting power is allocated and capped, and how the tallying rule and slashing affect a validator's rewards each epoch.
Alert Reference
A collection of the Prometheus Alertmanager rules that trigger alerts and warnings on validator and full nodes.
How does the validator set change?
Sui tracks validators in a validator set that changes at epoch boundaries. To join, an address calls request_add_validator_candidate and becomes a preactive validator candidate. The candidate then calls request_add_validator to join the active validator set active_validators in the next epoch. Sui processes new candidates at the end of the epoch.
To leave, a validator calls request_remove_validator, and the validator set records the removal as a pending request. After a validator leaves the active set, stakers can still withdraw their stake from it. The active set holds at most 150 validators.