Validators and clients: Agave, Firedancer, Jito, BAM, Harmonic

'Agave versus Firedancer' no longer describes the network. Most validators now run one of two codebases with a block-building layer on top, and the names you see combine both.

Updated Fact-checked November 10, 2026 Data as of 2026-11-16 00:42 UTC 9 sources
Short answer

A validator is a computer that checks every block, votes on it and takes turns producing blocks; 662 were voting on November 16, 2026. The software it runs (its client) comes from two codebases, Anza's Agave and Jump Crypto's Firedancer, usually with a block-building layer on top: Jito's original client, BAM or Harmonic. On 10 November 2026 Agave-derived clients ran about 83% of stake and Firedancer-derived clients about 16%.

  • Validators voting
    662
  • Delinquent
    38
  • Needed to pass a third of stake
    18
Read from the Solana network, 2026-11-16 00:42 UTC. These numbers refresh every two hours; the network page keeps the history.

A validator does three jobs: it re-runs every block to check it, it votes on which blocks are valid, and when the leader schedule says so, it produces blocks itself. It holds a copy of every account on Solana. Holders delegate stake to validators; a validator’s weight in votes and its share of leader slots both follow its stake.

How many there are, and how concentrated

On November 16, 2026, 662 validators were voting and 38 were delinquent, holding 0.08% of stake. The 18 largest held more than a third of all stake. Under Alpenglow the threshold that matters most is 20% (see Alpenglow explained), which fewer validators reach. The validators page reads the counts and all three thresholds every two hours.

What the client names mean

The client is the validator’s software. Validators report a client name in gossip, and the names combine two things: the codebase underneath, and the block-building layer on top.

Reported name Codebase Block-building layer Stake share, 10 Nov 2026
AgaveBam Agave BAM 37.3%
HarmonicAgave Agave Harmonic 23.1%
JitoLabs Agave (Jito-Solana) Jito’s original bundle auction 20.8%
HarmonicFiredancer Firedancer Harmonic 8.6%
Firedancer Firedancer none 5.7%
FireBAM Firedancer BAM 1.9%
Rakurai Agave Rakurai scheduler 1.2%
Agave Agave none 1.0%

Shares are by stake, from getClusterNodes joined to getVoteAccounts on 10 November 2026, and agreed with two independent validator sites that day; the client name is self-reported. Two readings follow from the same table:

  • By codebase: Agave-derived about 83%, Firedancer-derived about 16%. A bug in Agave’s core would still touch most of the network.
  • By block-building layer: BAM about 39%, Harmonic about 32%, Jito’s original client about 21%.

The codebases

  • Agave is Anza’s validator client, the continuation of the original Solana Labs code. Mainnet nodes reported 4.4.0 and 4.4.1 on November 16, 2026.
  • Firedancer is an independent client written from scratch by Jump Crypto’s team. Frankendancer was its hybrid stage (Firedancer networking with Agave execution); Firedancer’s docs now call those v0.x releases legacy. Full Firedancer releases use date-style versions such as v26.10.6. Firedancer and Frankendancer were not supported for the 21 October handover to Alpenglow (solana.com); Firedancer v26.10.2 added Alpenglow support, and three weeks after the switch Firedancer-derived clients again ran about 16% of stake.

The block-building layers

  • Jito-Solana (reported as JitoLabs) is Agave plus Jito’s bundle auction and tip programs: the original MEV client (MEV and Jito tips).
  • BAM is Jito’s newer network of scheduler nodes in secure enclaves that order transactions privately and attest to the ordering (bam.dev).
  • Harmonic offers “configurable block building for Solana”: the validator chooses among block builders (harmonic.gg).
  • Rakurai is a high-throughput scheduler.

What it costs to run one now

Cost Since Alpenglow Before 21 Oct 2026
Taking part in consensus 0.8 SOL Validator Admission Ticket per epoch, burned from the vote account (about 0.8 SOL a day at 25.8-hour epochs) vote transactions, up to about 1.1 SOL a day in fees (Anza’s requirements page still says this)
Vote account deposit a rent-exempt minimum, refundable the same, at the older, higher rate
Server Anza’s recommendation: 12 cores / 24 threads or more at 2.8 GHz+, 256 GB RAM or more, separate NVMe disks for accounts and ledger (1 TB+ each), 2 Gbit/s symmetric for a staked node, 10 Gbit/s recommended same
Admission only the 2,000 highest-staked validators take part no cap

A validator earns inflation rewards for voting and keeps its commission from its delegators’ share; it also keeps the fees and priority fees of the blocks it produces, and its MEV commission on tips. Whether that covers the ticket and the server depends on its stake. Commission varies widely: on November 16, 2026, 220 validators charged 0% and 61 charged 100% (mostly operators staking their own SOL), and 23.0% of stake sat with 100%-commission validators.

What this means for you

If you delegate, the client a validator runs affects you less than its commission, its uptime and where its servers are. Our guide on choosing a validator explains what to look at, without a leaderboard. If you read “Solana is Agave versus Firedancer”, note the date: by November 2026 most stake runs Agave with BAM or Harmonic on top.

Questions people ask

How many validators does Solana have?

662 vote accounts were voting on November 16, 2026, with 38 more delinquent (not voting). About 3,800 nodes were in gossip that day, but most of those are RPC nodes that do not vote. Our validators page keeps the count daily.

How much does it cost to run a Solana validator?

Since Alpenglow, each validator has a 0.8 SOL admission ticket burned from its vote account every epoch, about 0.8 SOL a day at today's epoch length, instead of paying for vote transactions. Add a dedicated server: Anza recommends 12 or more cores at 2.8 GHz or faster, 256 GB of RAM or more, separate NVMe disks and at least 2 Gbit/s for a staked node.

Has Firedancer been released?

Yes. Full Firedancer was announced live on mainnet in December 2025, and its releases now use date-style numbers (v26.10.6 on 5 November 2026). Firedancer-derived clients, including Harmonic and BAM variants, ran about 16% of stake on 10 November 2026.

Is there a minimum stake to run a validator?

There is no protocol minimum, but Alpenglow admits only the 2,000 highest-staked validators, and a validator needs enough stake delegated to it for rewards to cover the 0.8 SOL ticket each epoch and the server.

Sources

  1. Anza docs: Agave validator requirements (hardware; last changed 2025-11-17)
  2. solana.com: BLS pubkey and the Validator Admission Ticket (0.8 SOL per epoch)
  3. solana.com: Alpenglow (clients supported for the migration)
  4. Agave releases (v4.4.1, 5 Nov 2026)
  5. Firedancer releases (v26.10.6, 5 Nov 2026)
  6. Firedancer docs (Frankendancer as the legacy v0.x line)
  7. BAM (bam.dev)
  8. Harmonic (harmonic.gg)
  9. Solana RPC: getClusterNodes (clientId) and getVoteAccounts (stake), read 2026-11-10