Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates to Validator Docs #1207

Merged
merged 6 commits into from
Jan 28, 2022
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions docs/validators/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,31 +8,31 @@ order: 1

The [Cosmos Hub](../README.md) is based on [Tendermint](https://github.com/tendermint/tendermint/tree/master/docs/introduction), which relies on a set of validators that are responsible for committing new blocks in the blockchain. These validators participate in the consensus protocol by broadcasting votes that contain cryptographic signatures signed by each validator's private key.

Validator candidates can bond their own ATOM and have ATOM ["delegated"](../delegators/delegator-guide-cli.md), or staked, to them by token holders. The Cosmos Hub has 125 validators, but over time the number of validators will increase to 300 according to a predefined schedule. The validators are determined by who has the most stake delegated to them — the top 125 validator candidates with the most stake are the current Cosmos validators.
Validator candidates can bond their own ATOM and have ATOM ["delegated"](../delegators/delegator-guide-cli.md), or staked, to them by token holders. The Cosmos Hub has 150 validators, but over time the number of validators can increase. The validators are determined by the total number of ATOM tokens delegated to them — the top 150 validator candidates with the most voting power are the current Cosmos validators.

Validators and their delegators earn ATOM as block provisions and tokens as transaction fees through execution of the Tendermint consensus protocol. Initially, transaction fees are paid in ATOM but in the future, any token in the Cosmos ecosystem will be valid as fee tender if the token is whitelisted by governance. Note that validators can set commission on the fees their delegators receive as additional incentive.
Validators and their delegators earn ATOM as block provisions and tokens as transaction fees through execution of the Tendermint consensus protocol. Note that validators can set a commission percentage on the fees their delegators receive as additional incentive. You can find an overview of all current validators and their voting power on [Mintscan](https://www.mintscan.io/cosmos).

If validators double sign, are frequently offline, or do not participate in governance, their staked ATOM (including ATOM of users that delegated to them) can be slashed. The penalty depends on the severity of the violation.
If validators double sign, are offline for an [extended period](./validator-faq.html#what-are-the-slashing-conditions), their staked ATOM (including ATOM of users that delegated to them) can be slashed. The penalty depends on the severity of the violation.

## Hardware

For validator key management, validators must set up a physical operation that is secured with restricted access. A good starting place, for example, would be co-locating in secure data centers.

Validators are expected to equip their datacenter location with redundant power, connectivity, and storage backups. Expect to have several redundant networking boxes for fiber, firewall, and switching and then small servers with redundant hard drive and failover. Hardware can be on the low end of datacenter gear to start out with.
Validators are expected to equip their datacenter location with redundant power, connectivity, and storage backups. Expect to have several redundant networking boxes for fiber, firewall, and switching and then small servers with redundant hard drive and failover.

Initial network requirements can be low. The current testnet requires minimal resources. Then bandwidth, CPU, and memory requirements rise as the network grows. Large hard drives are recommended for storing years of blockchain history.
You can find the minimum hardware requirements on the [instructions for joining mainnet](../hub-tutorials/join-mainnet.md). As the network grows, bandwidth, CPU, and memory requirements rise. Large hard drives are recommended for storing years of blockchain history, as well as significant RAM to process the increasing amount of transactions.

## Set Up a Website

Set up a dedicated validator's website and signal your intention to become a validator on the Cosmos Forum [Validator Candidates](https://forum.cosmos.network/t/validator-candidates-websites/127/3) site. Posting your validator website is important because delegators want to have information about the entity they are delegating their ATOM to.
We suggest you set up a dedicated validator's website and signal your intention to become a validator in the [Cosmos Discord](https://discord.gg/cosmosnetwork). Posting your validator website can help because delegators want to have information about the entity they are delegating their ATOM to.

## Seek Legal Advice

Seek legal advice if you intend to run a Validator.
We recommend you seek legal advice if you intend to run a Validator node.

## Community

Discuss the finer details of being a validator on our community chat and forum:
Discuss the finer details of being a validator on our community Discord and sign up to the newsletter to get regular updates:

* [Validator Chat](https://riot.im/app/#/room/#cosmos_validators:matrix.org)
* [Validator Forum](https://forum.cosmos.network/c/validating)
* [Cosmos Developers Discord](https://discord.gg/cosmosnetwork)
* [Newsletter](https://cosmos.network/updates/signup/)
Loading