Sentinel-Turing-1 : Run a Validator after genesis
===

The objective of this document is to enable users with the minimum configuration of the server, run a Validator node after the genesis or start of a chain.

### Minimum Configuration Required

Cores : 4
RAM : 8-16GB
Storage Space : 50GB
Storage Type : SSD

### Initializing the Chain

Initialize the `sentinel-hub` validator and set the moniker. *Moniker* is a name that you set to your validator. It will generate genesis.json and config file.

`sentinel-hubd init <moniker name of validator>`

for example, if `ironman_validator` is the moniker to be set, the below command is to be used

`sentinel-hubd init ironman_validator`


### Create An Account

Run the following command to create a new Sentinel account.

`sentinel-hubcli keys add <account name>`


### Check Public Key

Find the validator public key by using the following command

`sentinel-hubd tendermint show-validator`


### Becoming a Validator

After the public key has been identified, use the below command to create a validator.

`sentinel-hubcli tx staking create-validator \`
`--moniker <moniker name of validator> \`
`--amount <amount to be stake in tsent> \`
`--fees < transaction fee in tsent> \`
`--gas <gas value>\`
`--pubkey <validator consensus public key> \ `
`--chain-id <chain id> \ `
`--node <node rpc server address>\`
`--from <name of account which has staking tsent amount> \`
`--commission-max-change-rate 0.01 \`
`--commission-max-rate 0.2 \`
`--commission-rate 0.1 \`
`--min-self-delegation 1 \`
`--broadcast-mode block `


... the image continues ..


### Check added Validator

Find the validators info by using
`sentinel-hubcli query staking validators --chain-id <chain id> --node <node rpc server address>`


# Walkthrough - Running a Validator on Sentinel-Turing-1 after genesis

Video coming soon!