Getting started

Running a validator means running a client that takes part in consensus around the clock, on a server you look after, with keys you protect, for stake you have to earn. This page lays out the order. Each step links to the page that covers it.

1. Choose a client

Today’s production clients come in two independent implementations, plus forks of each that add block-building integrations:

• Agave: Anza’s client.
  • Jito-Solana: Jito’s fork of Agave, with the Jito block engine and BAM, Jito’s block assembly marketplace.
  • Harmonic Salsa: Harmonic’s fork of Agave, for its block-building marketplace.
• Firedancer: Jump’s independent implementation.
  • FireBAM: Jito’s fork of Firedancer, for BAM.
  • Harmonic Samba: Harmonic’s fork of Firedancer.

Most pages here name Agave or Firedancer. Unless a page says otherwise, what applies to a client applies to its forks too. Check the fork’s release notes for anything it changes.

Frankendancer (Firedancer’s networking on Agave’s runtime) is legacy:

• Firedancer removed it from its main branch in October 2026.
• Its last release, v0.1204.40300 (2026-09-21), came out before mainnet switched to Alpenglow.

If you still run it, plan a move to Firedancer or Agave.

Opinion

Client diversity makes the network more resilient. If you’re starting out, pick the client whose docs and community you find easiest to work with. You can switch later without changing your keys or vote account.

2. Set up the host

Hardware, disk layout, OS and kernel tuning, firewall rules and systemd units are mechanical, and best done as code. Two places to start:

• Requirements: each client publishes its own minimum hardware and network requirements. Use the most recent version of those, not numbers copied into a blog post.
• Automation: validator-ansible is an open Ansible template for the host setup. It covers disks, kernel and network tuning, firewall and service units, for Agave and Firedancer alike. Fork it and adjust it to your hardware.

3. Generate your keys

Create your identity, vote account and withdraw authority before you do anything on mainnet. Keep the withdraw authority cold from day one. See Key setup and management, including how to make sure your vote account has a BLS key, which Alpenglow requires.

4. Run on testnet first

Testnet is where you learn your client’s failure modes without risking stake, and most delegation programs require testnet participation anyway. See Getting stake.

5. Go to mainnet and earn stake

Create a mainnet vote account with a deliberate commission, publish your validator info, and apply to delegation programs and stake pools: Getting stake.

6. Keep it healthy

Monitor it, keep up with releases, and know what you’ll do when it fails. Resources lists the places operators get release announcements and help.