Get Started with
Blockdaemon Today!
Contact us to learn how we can help you power your blockchain business.
Unparalleled Security & Compliance
Seamless Integration & Scalability
Dedicated Customer Support
A clear look at Firedancer and Frankendancer on Solana mainnet, including deployment status, stake distribution, client diversity, and what operators should monitor next.
.png)
Jump Crypto’s Firedancer is a high performance client for Solana. Frankendancer began producing blocks on Solana mainnet in 2025.
This blog covers the current deployment status, the difference between Firedancer and Frankendancer, the latest stake distribution, and the indicators operators should monitor next.
The Firedancer repository produces two distinct validators.
Both are part of the Firedancer project, but they serve different roles in Solana’s validator ecosystem.
Frankendancer is the hybrid validator.
It uses Firedancer’s networking and block-production components, while Agave, the validator client maintained by Anza, handles execution and consensus.
Firedancer is the fully independent validator client.
It shares no code with Agave and is designed to give Solana a second client implementation. MEV capture on either client is enabled through Jito integration. The in-client revenue-scheduling path was removed earlier in 2026.
In May 2026, CoinDesk reported on Firedancer’s status as “live and running in production,” and that the client had processed tens of millions of transactions over the preceding months.
The rollout is gradual for technical reasons.
A defect in consensus or block-production logic can create network risk when a client carries a significant share of stake. On Solana, the network stops finalizing blocks if approximately one-third of stake becomes unavailable. A new implementation needs time under production conditions before it can safely carry more stake.
To support a wider rollout, the team completed a public audit competition with a one-million-dollar bug bounty pool.
Source: https://reports.firedancer.io/
Firedancer’s client-diversity benefit depends on stake distribution.
A new client helps reduce dependence on a single implementation when it carries enough stake to support network operations during a client-specific issue.
Firedancer is in an early production phase. A severe Agave issue would still create material network risk because the independent Firedancer client does not yet carry enough stake to support normal operation.
That position is consistent with the rollout model. Firedancer is gaining production exposure before taking on a larger share of validator responsibility.
Firedancer is live on Solana mainnet and processing production traffic.
Frankendancer remains the larger production path associated with the Firedancer project, which continues to receive regular updates. The fully independent client is moving through a staged rollout shaped by security review, production testing, and operator readiness
The project release history shows steady activity through 2026, including alignment with Agave stable versions, refinements to the networking path, improvements to block packing, and updates to operator tooling.
These updates keep the hybrid validator aligned with the broader Solana validator ecosystem and help reduce operator friction.
For operators and infrastructure teams, the key indicators are stake share, public release readiness, and support for upcoming Solana consensus changes.
To discuss your Solan staking strategy, book a call with a Blockdaemon staking expert today.
Contact us to learn how we can help you power your blockchain business.
