Install validator software
You can choose to install the conventional Solana client, or Jito-Solana client if you wish to capture MEV revenue.
You can find additional information on the Jito-Solana client in these sources:
Fill in the fields to configure your validator node:
Validator name: your validator's ID used for monitoring.
Local secrets path: a path to the directory on your server where your validator’s key pairs are stored (e.g., /root/.secrets).
Swap file size, gb: the size of the swap file on your server.
Ramdisk size, gb: the size of the RAM disk on your server (0 or 100+ Gb).
Solana client: Solana or Jito.
Solana version: Solana software version.
We highly recommend creating a RAM disk with as much RAM as you can possibly allocate for your validator to make sure it performs and votes well. Please note that a small RAM disk is worse than none. This is why you can set either O or 100+ Gb.
In Advanced Settings, enter custom paths provided they already exist, or leave the fields empty to use default paths (grayed out placeholders):
Ledger path: blockchain ledger data, including transactions and signatures.
Accounts path: location for storing account data, such as balances and account states.
Snapshots path: snapshots of the Solana blockchain state at specific intervals are saved for quick synchronization.
Accounts hash cache path: cache of the hashes of account states.
When specifying a path, make sure that it already exists. Failure to do so may lead to irreversible changes.
Click the Run Command button to have the Agent install the validator software.
If SVT fails to perform your command and notifies you about it, click Cancel Task to skip the command. After your command has been successfully skipped, a respective log entry will be added in the Command History section.
If the installation has been successfully launched, you will see this:
To view a real-time log of the Docker container running the current command, enter your server’s address in IP address and click Show Live Logs, or run this command in your CLI (see View real-time logs for details):
The newly created validator may take a while to be added to the validator list (up to 10 minutes on Mainnet and up to 30 minutes on Testnet).
Last updated
