Skip to main content
The sui validator command provides tools for managing validator operations on the Sui network.

Synopsis

Global Options

path
Path to client configuration file
string
The Sui environment to use
boolean
Return command outputs in JSON format

Commands

make-validator-info

Create validator information and generate key files.
string
required
Validator name
string
required
Validator description
string
required
URL to validator image/logo
string
required
Validator project/website URL
string
required
Hostname for the validator
u64
required
Gas price in MIST
Example:
Generated Files:
  • protocol.key - Protocol keypair (BLS12381)
  • account.key - Account keypair (from active address)
  • network.key - Network keypair (Ed25519)
  • worker.key - Worker keypair (Ed25519)
  • validator.info - Validator information YAML file

become-candidate

Request to become a validator candidate.
path
required
Path to validator.info file generated by make-validator-info
u64
Gas budget for this transaction (default: 200000000 MIST)
boolean
Serialize transaction instead of executing it
Example:

join-committee

Request to join the active validator set.
u64
Gas budget for this transaction (default: 200000000 MIST)
boolean
Serialize transaction instead of executing it
Prerequisites:
  • Must already be a validator candidate
  • Must meet stake requirements
Example:

leave-committee

Request to leave the active validator set.
u64
Gas budget for this transaction (default: 200000000 MIST)
boolean
Serialize transaction instead of executing it
Prerequisites:
  • Must be an active validator
Example:

display-metadata

Display validator metadata.
SuiAddress
Validator address to query. Uses active address if not specified
boolean
Output in JSON format (default: true)
Example:
Output includes:
  • Validator status (Active/Pending)
  • Name, description, URLs
  • Network addresses
  • Public keys
  • Gas price
  • Commission rate
  • Staking pool information
  • Operation cap ID

update-metadata

Update validator metadata.

Metadata Types

name - Update validator name (effective immediately):
description - Update description (effective immediately):
image-url - Update image URL (effective immediately):
project-url - Update project URL (effective immediately):
network-address - Update network address (effective next epoch):
primary-address - Update primary address (effective next epoch):
worker-address - Update worker address (effective next epoch):
p2p-address - Update P2P address (effective next epoch):
network-pub-key - Update network public key (effective next epoch):
worker-pub-key - Update worker public key (effective next epoch):
protocol-pub-key - Update protocol public key and proof of possession (effective next epoch):

update-gas-price

Update the gas price used to calculate Reference Gas Price.
u64
required
New gas price in MIST
ObjectID
Validator’s OperationCap ID. Required if sender is not the validator itself
u64
Gas budget for this transaction (default: 200000000 MIST)
boolean
Serialize transaction instead of executing it
Example:

report-validator

Report or un-report a validator.
SuiAddress
required
Sui address of the validator being reported
ObjectID
Reporter validator’s OperationCap ID. Required if sender is not the reporter validator
boolean
If true, undo an existing report
u64
Gas budget for this transaction (default: 200000000 MIST)
boolean
Serialize transaction instead of executing it
Prerequisites:
  • Reporter must be an active validator
Example:

serialize-payload-pop

Serialize the payload for generating Proof of Possession.
SuiAddress
required
Authority account address (hex with 0x prefix)
AuthorityPublicKeyBytes
required
Authority protocol public key (hex encoded)
Example:
Use case: Take the payload offline to sign with an Authority protocol keypair.

display-gas-price-update-raw-txn

Display the serialized data of a gas price update transaction.
SuiAddress
required
Address of the transaction sender
ObjectID
required
Object ID of validator’s OperationCap
u64
required
Gas price to be set
u64
Gas budget for this transaction (default: 200000000 MIST)
Example:

register-bridge-committee

Register as a Sui native bridge committee member.
path
required
Path to Bridge Authority Key file (secp256k1)
string
required
Bridge authority URL for signature collection
boolean
default:"false"
Only print unsigned transaction without executing (for offline signing)
SuiAddress
Must be present if —print-only is true
u64
Gas budget for this transaction (default: 200000000 MIST)
Prerequisites:
  • Must be an active validator
  • URL must use http or https scheme
Example:

update-bridge-committee-node-url

Update Sui native bridge committee node URL.
string
required
New node URL to register
boolean
default:"false"
Only print unsigned transaction without executing
SuiAddress
Must be present if —print-only is true
u64
Gas budget for this transaction (default: 200000000 MIST)
Prerequisites:
  • Must be a bridge committee member
Example:

Validator Lifecycle

Becoming a Validator

Operating a Validator

Leaving the Validator Set

Validator Metadata Updates

Immediate vs Next Epoch

Some metadata updates take effect immediately, while others take effect in the next epoch: Immediate:
  • Name
  • Description
  • Image URL
  • Project URL
Next Epoch:
  • Network address
  • Primary address
  • Worker address
  • P2P address
  • Network public key
  • Worker public key
  • Protocol public key

Key Rotation

Bridge Committee

Joining Bridge Committee

Updating Bridge URL

Gas Price Management

The Reference Gas Price (RGP) is calculated based on all active validators’ gas prices. As a validator:
Gas Price Considerations:
  • Set competitive rates to attract stake
  • Consider operational costs
  • Monitor network RGP trends
  • Updates take effect in the next epoch

Validator Reporting

Validators can report peers for misbehavior:
Reporting impacts:
  • Accumulating reports may affect validator reputation
  • Severe misbehavior can lead to removal from the active set
  • Only active validators can report

Offline Transaction Signing

For enhanced security, generate transactions on an online machine and sign offline:

Best Practices

  1. Secure key storage: Use hardware security modules (HSM) for protocol keys
  2. Backup keys: Maintain secure, offline backups of all validator keys
  3. Monitor uptime: Ensure high availability to avoid penalties
  4. Test updates: Use testnet to validate metadata and key updates
  5. Gradual gas price changes: Avoid sudden price changes
  6. Regular metadata review: Keep validator information current
  7. Bridge security: Secure bridge authority endpoints

Troubleshooting

Cannot Join Committee

Metadata Update Not Applying

Key Rotation Issues