Firedancer Rollout Status
Firedancer is a new Solana validator client built from scratch by Jump Crypto. It is designed for high throughput, strong sandboxing, and independence from the existing Agave codebase.
Two validators, one codebase
The Firedancer repository produces two distinct validator builds:
| Variant | Description | Agave dependency |
|---|---|---|
| Frankendancer | Hybrid client using Firedancer’s networking and block production with Agave’s execution and consensus | Partial |
| Firedancer | Full independent validator with no Agave code | None |
Frankendancer serves as the stepping stone. Validators can run it today to benefit from Firedancer’s networking stack while keeping Agave’s battle-tested execution engine. The full Firedancer client removes all Agave dependencies.
Design goals
Performance. Firedancer’s concurrency model draws from low-latency trading systems. Core Solana primitives (signature verification, account lookups, transaction scheduling) are reimplemented in C with explicit memory management and lock-free data structures.
Security. The architecture supports a highly restrictive sandbox model. Each component runs with minimal system call permissions, reducing the attack surface compared to a general-purpose runtime.
Client diversity. A from-scratch implementation means a bug in Agave does not automatically affect Firedancer. This reduces the risk of a single implementation bug halting the network.
Requirements
Firedancer runs on Linux only, requiring kernel v4.18 or later. There is no Windows or macOS support.
Current status
Frankendancer is available on testnet. Validators can join with:
./build/firedancer-dev --testnetCheck the Firedancer documentation for the latest mainnet rollout timeline and configuration guides.
Impact on developers
For RPC users and application developers, the validator client is transparent. Your transactions are processed the same way regardless of whether the leader runs Agave or Firedancer. The differences are in block production speed and networking, which may improve transaction landing rates and reduce confirmation latency.
FAQ
Do I need to change my code for Firedancer? No. Firedancer implements the same Solana protocol. RPC methods, transaction format, and program execution remain identical.
Is Firedancer faster than Agave? Firedancer targets higher throughput through its architecture, but real-world performance depends on network conditions and workload. Benchmarks are not yet published for mainnet conditions.
Can I run Firedancer as an RPC node? Check the Firedancer documentation for current RPC node support status. The initial focus is on validator nodes.
Updated: