Validator FAQs

Check the FAQ for running a validator on Egaxd.

General Concepts

What is a validator?

What is "staking"?

What is a full node?

What is a delegator?

Becoming a Validator

How to become a validator?

Validator keys and states

What are the different types of keys?

What are the different states a validator can be in?

What is "self-bond"? How can I increase my "self-bond"?

Is there a testnet faucet?

Is there a minimum amount of EGAXD that must be staked to be an active (bonded) validator?

How will delegators choose their validators?


Do validators need to be publicly identified?

What are the responsibilities of a validator?

What does staking imply?

Can a validator run away with its delegators' EGAXD?

How often will a validator be chosen to propose the next block? Does it go up with the quantity of EGAXD staked?


What is the incentive to stake?

What is the incentive to run a validator?

What is a validator's commission?

How are block provisions distributed?

How are fees distributed?

What are the slashing conditions?

Are there any best practice guides on preventing double-signing?

Do validators need to self-bond EGAXD?

How to prevent concentration of stake in the hands of a few top validators?

Technical Requirements

What are hardware requirements?

What are software requirements?

What are bandwidth requirements?

What does running a validator imply in terms of logistics?

How to handle key management?

What can validators expect in terms of operations?

What are the maintenance requirements?

How can validators protect themselves from Denial-of-Service attacks?


  • Telegram

  • Discord

  • Twitter

Built with ❤️ by the Egaxd Core Development Team. © 2024 All rights reserved.

Last updated