For the complete documentation index, see llms.txt. This page is also available as Markdown.

Installation

Install and synchronize Lava Mainnet, one command at a time.

Mainnet · lava-mainnet-1 · Ubuntu 24.04 / x86-64

Use a normal Linux account with sudo access. Commands assume a new node and the same shell session. Existing operators should use Upgrade.

1. Prepare packages

Refresh package metadata.

sudo apt update

Install dependencies

Install download, build and snapshot tools.

sudo apt install -y ca-certificates curl jq git make build-essential golang-go lz4 tar

Install the binary

Select a release

Use the network-approved release. This pinned stable release is the reference, not an automatic upgrade decision.

LAVA_VERSION=v6.2.5

Download lavad

Download the Linux amd64 release asset.

Check the download

For v6.2.5, this must print OK. A different release needs its own published checksum.

Install

Place the verified executable in the system path.

Verify the binary

Confirm the selected version starts successfully.

Initialize and connect

Initialize once

Replace MY_NODE with your own moniker. Do not rerun this over an existing validator home.

Download genesis

Save network genesis to the node configuration.

Verify the network

Continue only if the file is valid JSON and this check returns true.

Download the address book

Load BlockPro’s published peer discovery file.

Check the address book

Ensure the download contains peer records, not an HTML error page.

Set minimum gas prices

Set this node’s local transaction admission policy.

Set a persistent peer

Use the BlockPro peer published for this network.

Use bounded pruning

Keep the application’s standard pruning policy; archive operation needs more disk space.

Apply Lava consensus timing

Apply the timings from the official joining guide.

Run with systemd

Create the service

Run the node as the current non-root account, with automatic restart after a process failure.

Load the unit

Tell systemd about the new service.

Enable on boot

Enable the service without starting it yet.

Restore recent state

Follow Snapshots before starting. The current binary may not replay every historical upgrade from genesis. Choose a snapshot compatible with the installed release.

Start

Start the node after restoration.

Follow logs

Look for advancing blocks; Ctrl+C leaves the service running.

Check synchronization

Wait for catching_up to become false and compare the height with the explorer.

Next: Validator or Useful Commands.

Upstream reference.

Last updated