On this page
The RealValidator Team Editorial team

Firedancer is Jump Crypto's independent Solana validator client, written in C and not derived from the Agave codebase; Frankendancer is the production hybrid client combining Firedancer's networking layer with Agave's execution engine. Frankendancer has been live on mainnet since late 2025 and runs approximately 26% of staked SOL as of epoch 971 (2026-05-15), per BlockEden.xyz. Full Firedancer remains testnet-only as of the same date.

The distinction between the two matters for client-diversity analysis. Frankendancer's networking improvements reduce the risk of a single-codebase consensus bug, but execution is still Agave-derived; full Firedancer would represent the first fully independent client implementation on Solana mainnet, removing the remaining shared-execution-code surface.

What each is, exactly

Frankendancer ships Firedancer's Transaction Processing Unit (TPU — see the styleguide vocabulary) and networking stack on top of an otherwise Agave-derived runtime. The packet ingest, scheduling, and shred propagation paths are Firedancer code; the on-chain program execution, state management, and consensus logic are Agave. This is a practical interim — Frankendancer was deployable years before full Firedancer because the networking layer is independently testable without requiring complete runtime compatibility.

Full Firedancer is the complete reimplementation: TPU, runtime, BPF interpreter, state management, and consensus. It is on testnet as of May 2026 (per Jump Crypto's Firedancer page) and is not yet running production stake. Deployment to mainnet does not have a published target date; Jump has stated it ships when correctness validation is complete, not on a calendar.

Agave is the Anza-maintained Rust client, the fork-successor to the original Solana Labs validator. It runs the majority of stake not covered by Frankendancer or the Jito-Solana fork (see the Jito disambiguation).

Stake share as of epoch 971

Per BlockEden.xyz's March 2026 client adoption report:

  • Frankendancer: approximately 26% of staked SOL, up from 20.9% in October 2025 and ~8% in June 2025.
  • Jito-Solana (Agave-derived MEV client): approximately 72-88% of staked SOL — the wide range reflects double-counting where validators run Jito-Solana with Frankendancer-style networking patches. Trend is downward as Frankendancer adoption grows.
  • Plain Agave: the remainder, primarily on the Solana Foundation Delegation Program validators and operators who have not migrated.

The 26% Frankendancer figure should be cited with its source date because client adoption shifts each epoch. An earlier figure of ~21% appeared in BlockEden reporting from February 2026; the more recent ~26% supersedes it.

Why hybrid client diversity matters

Solana's consensus liveness historically depended on a single client codebase. A bug that halted Agave halted the network — most visibly in the September 2021 and June 2022 outages. Frankendancer changes the failure surface in one direction: a networking bug in Frankendancer would not affect Agave validators, and vice versa, so a packet-processing fault no longer cascades across all of mainnet stake.

It does not change the execution surface. A bug in BPF interpretation or state transition would still affect both Frankendancer and Agave validators because both share that code. Full Firedancer closes this remaining shared surface; until it deploys to mainnet, client diversity is partial.

What this means for stakers

For staker evaluation, the relevant question on a validator profile is which client the validator is running at the current epoch:

  • "Runs Jito-Solana (Agave-derived)" — earns MEV via the Jito Block Engine (see the Jito disambiguation).
  • "Runs Frankendancer" — contributes to client diversity; MEV participation depends on whether Jito Block Engine integration is enabled.
  • "Runs plain Agave" — typically SFDP-only validators or new operators.
  • "Runs full Firedancer" — not applicable on mainnet as of epoch 971; would indicate testnet participation only.

Validators running Frankendancer or Jito-Solana with current versions also satisfy Marinade SAM software-version eligibility filters; validators on outdated Agave releases lose SAM allocation.

Sources

Client share cited: BlockEden, epoch 971, 2026-05-15. Adoption changes each epoch; verify on a fresh snapshot before citing a specific percentage.