githubEdit

Lava Node Setup

Follow this guide to run your own LavaNet node and use it for your Lava Provider.

This is not financial advise. All information provided here are sourced from the following sites: https://services.kjnodes.com/mainnet/lava/installation/arrow-up-right https://services.mellifera.network/Mainnet/lava-network/snapshot_and_dataarrow-up-right

Hardware requirements: RAM: 64 GB RAM Storage: 2 TB NVME SSD OS: Linux 22.04 Rent a server here (optional): https://www.interserver.net/r/950716arrow-up-right

Set Node name

Change it to anything you like.

MONIKER="my_node"

Install dependencies

sudo apt -q update
sudo apt -qy install curl git jq lz4 build-essential
sudo apt -qy upgrade

Install GO

This will install Go version 1.22.8

sudo rm -rf /usr/local/go
curl -Ls https://go.dev/dl/go1.22.8.linux-amd64.tar.gz | sudo tar -xzf - -C /usr/local
eval $(echo 'export PATH=$PATH:/usr/local/go/bin' | sudo tee /etc/profile.d/golang.sh)
eval $(echo 'export PATH=$PATH:$HOME/go/bin' | tee -a $HOME/.profile)

go version

Download and build binaries

Install Cosmovisor and create a service

Initialize the node

Update chain-specific configuration

Set Ports

This is a more simplified command to manually set the Ports of your LavaNet node. You can manually change it depending on your needs. Make sure there are no conflicts as this might cause the node to not run.

Download latest chain snapshot

Make sure that the port numbers you will assign is not in use.

Use this command to check.

Replace port-number depending on what port you are trying to check.

  • Tendermint RPC

Navigate to /.lava/config and open config.toml file. Take note of the URL and Port.

image

  • Rest (API)

Navigate to /.lava/config and open app.toml file. Take note of the URL and Port. Make sure it is set to enable = true.

image

  • gRPC

Navigate to /.lava/config and open app.toml file. Take note of the URL and Port. Make sure both gRPC and gRPC-web is set to enable = true.

image

Setup Firewall

These are just recommended port settings, which I am currently using. Change it depending on your own server settings.

Start service and check the logs

Check sync status

Run the following command:

If you get a result false that means node is fully synced.

Check connected peers:

Archive Snapshot

If you want to run a full archive node, you can use this snapshot. The following commands will delete the existing /data folder. Make sure you create a backup in case you need it. Set the proper pruning settings to nothing before running the node.

Start the node and let it sync

Last updated