On this page
The RealValidator Team Editorial team

Solana's validator client landscape includes Jito-Solana (an Agave fork with MEV hooks; approximately 85-90% of staked SOL as of May 2026, trending down per BlockEden), Frankendancer (a hybrid using Firedancer networking with Agave execution; approximately 26% of staked SOL, up from ~21% in early 2026 and ~8% in June 2025), Agave standalone (Anza's canonical client without Jito hooks; residual share), and Full Firedancer (Jump Crypto's independent C-implementation, on testnet as of May 2026 and not yet in mainnet production). Reported categories overlap — some Frankendancer deployments include Jito MEV patches — so client-share percentages do not sum to 100%.

This tracker records validator client distribution and the ongoing migration toward more diverse client implementations. Client diversity is a structural decentralization signal: heavy concentration on a single client implementation creates correlated bug-and-bus-factor risk; bug-busting diversity protects the network against single-client failure modes.

Current state (as of 2026-05-16)

Source: BlockEden.xyz network analytics, May 2026.

  • Jito-Solana share: approximately 85-90% of staked SOL. Range cited in primary sources (e.g., BlockEden 2026-03-16: 72-88%); central estimate is 85-90%, trending downward.
  • Frankendancer share: approximately 26% of staked SOL (May 2026). Up from ~21% in early 2026 and ~8% in June 2025. Approximately 165 validators on Frankendancer per BlockEden (2026-03-16).
  • Full Firedancer share: 0% on mainnet. On testnet as of May 2026.
  • Agave (non-Jito, non-Frankendancer) share: residual; specific percentage not enumerated by primary sources because the dominant clients overlap (Jito-Solana is itself Agave-derived).
  • Overlap caveat: Categories above overlap. A validator running Frankendancer with Jito MEV patches counts in both buckets in BlockEden's reporting methodology; the Solana Foundation does not currently publish a non-overlapping client-share metric.

Timeline

  • 2026-05-16 (snapshot): Tracker established. Frankendancer at ~26% of staked SOL; Full Firedancer on testnet; Jito-Solana dominant but trending down. Source: BlockEden 2026-03-16 analytics extrapolated forward.
  • 2026-03-16: BlockEden publishes ~165 validators / ~26% stake on Frankendancer; Jito-Solana range 72-88% (methodology overlap noted). Source: BlockEden.xyz article 2026-03-16.
  • 2025-10: Frankendancer at approximately 20.9% of staked SOL. Adoption trend established.
  • 2025-08: Earlier primary source cited Jito-Solana at 88%. Source noted in Stakewiz documentation cross-references.
  • 2025 (late): Frankendancer goes live on Solana mainnet. Frankendancer is the production hybrid combining Firedancer's networking layer with Agave's execution layer; production deployment precedes Full Firedancer mainnet activation.
  • 2025-06: Frankendancer share approximately 8% of staked SOL. Early adoption phase.

What this means for stakers

Client diversity matters to stakers in two specific ways:

  1. Network resilience. A bug in a dominant client (e.g., Jito-Solana at 85%+) that produces invalid blocks or causes validators to crash would halt or destabilize the network. Diversification across implementations reduces this risk. A staker indirectly benefits from a more diverse network because their stake is at less risk of a cluster-halting bug.

  2. MEV participation. Jito-Solana enables a validator to receive Jito Block Engine MEV revenue. A validator not running Jito-Solana (or a Jito-patched Frankendancer) does not participate in Jito MEV, so its APY excludes the Jito MEV component (~0.13% at epoch 971). Stakers who care about MEV exposure should confirm the validator's client status — observable via Stakewiz's is_jito field.

The Solana Foundation's Delegation Program (SFDP) requires the validator software be one of an approved list of recent releases; specific minimum versions are cited at solana.org/delegation-criteria. The Wiz Score's version component penalizes validators running outdated client builds (see the Helius profile for an example of how a -20 version penalty contributes to a low composite score).

Watch: When Full Firedancer activates on mainnet (timing not yet announced), the client landscape becomes meaningfully three-way diverse. This is expected to be a multi-month adoption curve; this tracker will record stake-share milestones as they pass.

Affected validators in this directory

The wiki-directory validator's client status is recorded in each profile's Infrastructure or MEV policy section. Notable client choices:

  • Orca — runs Frankendancer (version string 0.821.30114 per the profile, derived from Stakewiz's version field at epoch 971). The only Frankendancer validator in the directory per profile content.
  • Jito-Solana running validators — most of the directory's profiles cite Jito-Solana as their client (visible via the is_jito: true flag on Stakewiz). Specific validators include Helius, Jito Labs, Solana Compass, Capital Alliance, and others.
  • Non-Jito (pure Agave) running validators — a minority in the directory; primarily SFDP-newer validators that have not adopted Jito-Solana.

For a per-validator client status, see the Infrastructure section of each profile.

Sources

Tracker since 2026-05-16. Client share figures cited from BlockEden.xyz analytics (most recent published article 2026-03-16) with operator-curated forward inference through 2026-05-16. Numerics re-verified against the same source on each tracker refresh.