Step 3: Installation

Installing the Solana CLI, generating identity keys, and configuring the cluster.

Step 3: Installation

We will install the official binary release of the Agave validator client (formerly Solana Labs). This tool suite includes the agave-validator binary required to run your node and the solana CLI for managing keys.

⚠️ Important: Agave Transition

The original solana-labs/solana repository was archived on January 22, 2025. Core development has transitioned to the Anza agave fork. The installer has been renamed from solana-install to agave-install, and the validator binary from solana-validator to agave-validator. The solana CLI and solana-keygen tools retain their names.

---

1. Install Agave Tool Suite

We will install the latest stable release directly from the official release channel.

💡 Version Check: As of early 2026, the recommended Mainnet version is in the v3.x series. Always check the official Solana Tech Discord #mb-announcement channel or the Agave releases page for the exact version tag before installing.

A. Download and Install

Switch to your solana user and run the installation script.

# Switch to the service user
su - solana

# Install the stable release using agave-install
sh -c "$(curl -sSfL https://release.anza.xyz/stable/install)"

💡 Tip: You can also install a specific version by replacing stable with a version tag, e.g.: sh -c "$(curl -sSfL https://release.anza.xyz/v3.1.9/install)"

B. Update PATH

The installer will ask you to update your PATH. Add this to your shell profile so the commands are available every time you log in.

# Add to .profile (or .bashrc)
echo 'export PATH="/home/solana/.local/share/solana/install/active_release/bin:$PATH"' >> ~/.profile

# Reload profile
source ~/.profile

# Verify installation
solana --version
agave-validator --version

Expected output: solana-cli 3.x.x ...

💡 Updating later: After the initial install, you can update to a new version at any time with: agave-install update

---

2. Generate Identity Keypair

Every node on the network (Validator or RPC) requires a "Node Identity." This keypair identifies your machine to the cluster and allows it to participate in the gossip protocol.

⚠️ Security Warning: This keypair must be stored on the server (Hot Wallet).

• For Validators: This key signs blocks. If stolen, attackers can impersonate your validator.

• For RPCs: This key has no funds, but establishes your node's reputation.

A. Create a Keys Directory

mkdir -p /home/solana/keys

B. Generate the Keypair

solana-keygen new -o /home/solana/keys/validator-identity.json

You will be asked for a passphrase. For automated servers, most operators leave this empty (press Enter), but institutional setups may use a password manager to inject the passphrase on boot.

---

3. Configure Cluster

Now we tell the Solana CLI to talk to Mainnet Beta by default and use the keypair we just generated.

# Set target to Mainnet Beta
solana config set --url https://api.mainnet-beta.solana.com

# Set default keypair
solana config set --keypair /home/solana/keys/validator-identity.json

Verify connectivity:

solana gossip

You should see a massive list of IP addresses. This confirms your node can reach the network.

---

4. Node Types: What's next?

At this stage, the path diverges depending on your goal:

Option A: RPC Node (Non-Voting)

• You do not need a Vote Account.

• You are ready to create the startup script.

Option B: Validator Node (Voting)

• You strictly require a Vote Account Keypair to participate in consensus.

• We will generate this in the Validator Setup section.