Complete Validator Setup Guide - Linux

This guide provides all the information for users to set up a node, validator, and perform basic health diagnostics on the validator after it is running.

Hardware Recommendations

Currently the recommendation for hardware is to follow the Cosmos documentation.
Reduce the hardware specifications at your own risk! This may cause validator instability which could lose to the loss of stake and delegated stake positions.

Running As A Background Process

Since the log output of the node will block the terminal and run in the foreground (and will therefore die when the session is ended/closed) it is recommended to use a program to run the node in the background. There are two recommended options:
There are also recommendations to run as a background service in the Cosmos docs.


Users must follow the Mainnet Node Guide first.

Creating a Validator

Creating a validator involves sending a create-validator command to the node you wish to validate from. For the purposes of this guide we will be creating a validator on the node which was created based on the Mainnet Node Guide.
Creating the validator is as simple as running the following command. Before running this command please read the following:
Running a validator should only be done by experienced Linux System Administrators. When you stake JUP in a validator, that JUP is at risk of being "slashed". Slashing is explained here.
jupiterd tx staking create-validator --amount=9000000ajup --pubkey=$(jupiterd tendermint show-validator) --moniker="[your node moniker]" --chain-id="jupiter_85-1" --commission-rate="0.01" --commission-max-rate="0.05" --commission-max-change-rate="0.01" --gas="auto" --min-self-delegation="5000000" --from=[keyname] --fees=500ajup
--amount // The quantity of staked aJUP
--pubkey // The validator's public key
--monker // The node moniker which will be doing validation, found in the config.toml file
--min-self-delegation // Minimum amount of aJUP required to be delegated from the node operator in order for validation to be performed
--from // The name of the key being used to sign the create-validator tx


Validator operators must keep security in mind. Validators publicly exposed to the internet may suffer from Distributed Denial of Service (DDoS) attacks which could reduce their uptime and therefore result in slashing of JUP and delegated JUP.
Additionally, using the wrong key management techniques could expose your validator's private key to attackers and cause theft of all of your funds.
Follow all of the Cosmos validator security suggestions and be aware of your validator security at all times.