SOLANA·HUB
DE
Infrastructure

Firedancer V1 Live on Solana Mainnet — Gradual Rollout, Frankendancer Stays the Broad Hybrid

As of 17 May 2026: full Firedancer V1 is producing blocks on Solana mainnet — on a limited set of validators, roughly 100 days and about 50,000 blocks, a deliberately gradual rollout after a 1M USD audit competition.

SOLANA·HUB Editorial · ·
Source: CoinDesk

Update 17 May 2026 — Firedancer V1 Is Live on Mainnet

The status has changed from prior months: full Firedancer V1 — not only the Frankendancer hybrid — is producing blocks on Solana mainnet.

  • Per the official Solana post, Firedancer has been running “on a handful of validators” for roughly 100 days and has successfully produced around 50,000 blocks.
  • Firedancer founding engineer Ritchie Patel told CoinDesk (16 May 2026): “Firedancer is live and running in production.” The rollout is deliberately gradual and progressive rather than a broad public launch.
  • It followed a Firedancer V1 audit competition on Immunefi with a 1M USD reward pool (9 April to 9 May 2026, per the Solana Ecosystem Roundup April 2026).

Context: this is client diversity at the code level — a second, fully independent validator implementation alongside Agave. The pure-Firedancer path is intentionally limited to a small set of validators; Frankendancer (hybrid) remains the more broadly deployed path. A network-wide activation has not occurred.

What Is Known

Jump Trading Group is developing Firedancer as a second independent validator client for Solana, written in C. The migration is two-staged:

  • Frankendancer (versions v0.xxx.yyyyy) — hybrid with Firedancer network layer and Agave runtime + Agave consensus. Runs on mainnet, broadly deployed.
  • Pure Firedancer (versions 1.x) — complete re-implementation of all three validator layers in C. In production on mainnet since May 2026, but on a limited set of validators (see update above). The Firedancer Docs naturally lag this status.

What Frankendancer Already Runs

From the Firedancer Getting-Started Docs:

  • Network stack (TPU/QUIC, shred reception, repair) is handled by Firedancer’s C code
  • Block production components during active leader slots
  • Runtime, consensus, and account storage continue to run on Agave Rust code

Validator operators can build Frankendancer from source — the Jump team does not publish pre-built binaries. Current tag conventions: v0.xxx.yyyyy for Frankendancer releases, v1.x for the pure Firedancer version.

Concrete Stake Shares

Concrete stake shares of Frankendancer and Firedancer validators are viewable via Solana Beach and comparable validator trackers. The Jump team has not named a network-wide pure-Firedancer activation timeline; per CoinDesk the rollout remains deliberately gradual.

How Firedancer Relates to Alpenglow

Firedancer and Alpenglow address different layers:

  • Firedancer = validator software (which code runs)
  • Alpenglow = consensus protocol (how validators agree)

Once Alpenglow is activated on mainnet (per Anza CEO Brennan Watt in the Anza26 post, planned for Q3 2026), Firedancer would also need to ship an Alpenglow-compatible implementation.

What to Watch

  • Stake migration from pure Agave to Frankendancer and to pure Firedancer
  • When the Jump team expands the pure-Firedancer rollout beyond the current validator set
  • Hardware requirement reductions: the Firedancer roadmap names this as a long-term goal
  • How the Alpenglow migration affects the Firedancer roadmap

For deeper architectural detail, see our Knowledge Pillar Firedancer & Frankendancer.

Sources

#firedancer #frankendancer #validator #jump-crypto