barkmannen / solv Goto Github PK

Discover the ease of setting up a Solana Validator Node server using solv, a powerful tool designed to simplify blockchain interactions.

With just a single command, solv eliminates the usual complexities, enabling you to launch a Solana Validator swiftly.

This tool not only streamlines the setup process but also opens doors for more individuals to participate in the blockchain network, making the Solana ecosystem more accessible.

Whether you're a seasoned developer or a blockchain enthusiast stepping into the validator realm, solv is your go-to solution for an uncomplicated, fast setup.

Dive into the world of Solana, explore the capabilities of solv, and be part of the blockchain revolution with minimal effort and maximum efficiency.

• Linux Ubuntu 20.04 LTS
• Linux Ubuntu 22.04 LTS

Login in to your Validator server by ssh and run the following command.

$ sh -c "$(curl -sSfL "https://storage.googleapis.com/epics-bucket/resource/solv/v3.3/install")"
$ cd ~ && source ~/.profile
$ solv setup

Then, select the type of node you want to target.

• TESTNET_VALIDATOR
• MAINNET_VALIDATOR
• RPC_NODE

Then

After startup, the snapshot download will start automatically. The Solana validator will start 🎊

Now you can select the mainnet for Jito MEV 🎉

solv CLI is a tool for managing Solana Validators from your local machine.

$ sh -c "$(curl -sSfL "https://storage.googleapis.com/epics-bucket/resource/solv-cli/v3.0.0/install")"

Start solv CLI Dashboard - from your local machine

$ solv c

$ solv s

$ solv restart

Default solana-validator.sh command is --no-incremental-snapshots.

If you want to download snapshot, you can use the following command.

$ solv restart --snapshot

This command will automatically remove --no-incremental-snapshots and add --no-genesis-fetch, --no-snapshot-fetch to yoursolana-validator.sh command.

$ solv log

or

Show only error logs

$ solv log -e

This command will show your all config paths which are used by solana validator.

$ solv get config

We updated the solv version to v3.0.0 to support the latest requirements of Solana Official Docs.

⭐️ Improved

• Changed Mountpoint/Directory as the solana official docs
• Removed unnecessary swapfile and ramdisk
• Added solv s for solv Dashboard (no command maintenance)

Below is the migration guide for existing solv users.(Mainly TDS attendees)

$ solv update

Open solv Dashboard

$ solv s

Set your default Language for initial setup

Solv Version: v3.0.0

? Select Language (Use arrow keys)
❯ en
  ja

Open solv Dashboard again to reflect the language change

$ solv s

Select 5 to migrate to solv v3.x.x

This will automatically update your node to the latest requirements of Solana Official Docs.

If you have any questions, please contact us on Discord.

https://discord.gg/yxm5hJqRhg

https://solana.org/delegation-program

$ solv --help
Usage: solv [options] [command]

💎 Solana Validator All-in-One CLI 💎

Options:
  -v, --version        Output the current version
  -h, --help           Display help for solv commands

Commands:
  server|s             Open solv Dashboard
  start                Start Solana Validator
  restart [options]    Restart Solana Validator
  stop                 Stop Solana Validator
  status               Show Solana Validator Status
  update|u [options]   Update Solana Validator Version
  log|l [options]      tail logs
  install|i [options]  Install/Update Solana Version
  stake                Solana Delegate Stake
  get <cmd>            Get Solana Validator Info
  scp <cmd>            Download/Upload Solana Validator Keypairs
  cron <cmd>           Run Schedule Tasks
  setup [options]      Setup Solana Validator
  help [cmd]           Display help for solv commands

Bug reports and pull requests are welcome on GitHub at https://github.com/EpicsDAO/solv This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

The package is available as open source under the terms of the Apache-2.0 License.

Everyone interacting in the SKEET project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.