Firedancer

Firedancer is Jump Trading Group's independent validator client for Solana, built entirely in C from the ground up. Announced in early 2022 and released to mainnet in December 2025, it is the first fully independent alternative to the Agave (formerly Solana Labs) client. Where Agave is written in Rust and carries the lineage of the original Solana implementation, Firedancer starts from a clean slate — rewriting every primitive, from networking and signature verification to block production and transaction execution, with low-latency trading infrastructure as its design north star.

Why Client Diversity Matters

Before Firedancer, Solana ran almost entirely on a single validator codebase. That meant a critical bug in Agave could halt the entire network — a vulnerability that contributed to several high-profile outages. Firedancer directly addresses this. With two independently implemented clients, a bug in one does not affect the other. The network can continue producing blocks even if an edge-case vulnerability disables every Agave node simultaneously. This is the same resilience principle that underpins Ethereum's multi-client model, and it is widely considered a precondition for a production-grade, institutional-grade network.

Architecture: Tiles and Kernel-Bypass Networking

Firedancer's distinguishing engineering choice is its tile-based architecture. Rather than running validator logic in a monolithic process, Firedancer divides work into specialized, independently schedulable "tiles" — discrete pipeline stages that handle transaction ingestion, deduplication, signature verification, block packing, and data availability. Each tile runs in isolation, can be optimized independently, and communicates with adjacent tiles through high-speed ring buffers. The result is a validator that saturates hardware resources rather than leaving cores idle.

The networking stack is similarly rebuilt from first principles. Firedancer implements kernel-bypass networking for both ingress (QUIC and UDP) and egress, bypassing the operating system's network stack to eliminate latency and CPU overhead. Signature verification uses AVX512-optimized ED25519 implementations that process multiple signatures in parallel on a single core. The block production pipeline uses a custom erasure coding system rather than relying on standard libraries. Every component reflects Jump's two decades of experience building latency-sensitive trading infrastructure.

Frankendancer: The Hybrid Bridge

Because rewriting a complete Solana validator is a multi-year effort, Jump introduced an intermediate configuration called Frankendancer. Frankendancer grafts Firedancer's networking layer and block production logic onto the existing Agave runtime and consensus code. Operators running Frankendancer benefit from Firedancer's superior transaction ingestion, deduplication, and DoS mitigation while Agave continues handling execution and consensus.

Frankendancer shipped to Solana testnet in 2024 and to mainnet later that year, carrying the v0.x version series. By the time full Firedancer launched in December 2025, Frankendancer had accumulated roughly 26% validator adoption — evidence that the Solana operator community was ready to run non-Agave software in production.

Full Firedancer: Mainnet Launch

The full Firedancer client — an entirely independent validator with no Agave code in the critical path — first reached testnet in July 2025 as v1.1.0. After more than 100 days of continuous testnet operation producing over 50,000 blocks without major issues, the full client was declared mainnet-ready. Jump announced the launch at Solana Breakpoint in Abu Dhabi on December 12, 2025.

Kevin Bowers, Chief Scientist of Jump Trading Group and the technical lead behind Firedancer, demonstrated at Breakpoint 2024 that Firedancer can sustain over 1 million transactions per second on commodity hardware. That number — achieved across six nodes in a controlled lab environment — has become the headline benchmark for Firedancer's potential. An earlier single-core fd_quic test in May 2023 clocked 1.4 million TPS with small transactions and 270,000 TPS with larger ones, with network throughput reaching 5.8 Gbps on a single core.

In real-world mainnet conditions, throughput is bounded by the slowest widely-adopted client. Full performance gains become available as network-wide Firedancer adoption grows and as complementary protocol upgrades — including Alpenglow consensus (targeting sub-150ms finality) and the removal of block compute caps via SIMD-0370 — are activated.

Adoption as of August 2026

Firedancer's rollout has been deliberate. As of August 10, 2026, the full Firedancer client runs on 57 of 698 active validators, accounting for 11.64% of total staked SOL, according to the wenfiredancer.com adoption tracker. Combined with Frankendancer's continuing presence, the Jump codebase represents a meaningful share of the network's consensus-producing capacity.

The team's published roadmap targets 50% network stake running Firedancer-derived software by mid-to-late 2026. Adoption has grown without a hard cutover: operators migrate at their own pace, the hybrid Frankendancer path remains available for those who want an incremental step, and the fdctl binary handles both configurations through a single control interface.

Wiredancer and Post-Quantum Research

Jump's infrastructure investment extends beyond software. Wiredancer, announced in August 2025, deploys FPGA-based hardware acceleration cards at the network edge of validators. Two daisy-chained FPGAs handle transaction deduplication and ED25519 signature verification at line rate in hardware, delivering clean, verified traffic directly into the validator before software processes it. In stress tests on a Solana mini-network, a simulated DDoS attack with invalid signatures cut throughput by over 50% on unprotected nodes; nodes with Wiredancer saw almost no impact.

On the cryptography side, the Firedancer team has been building post-quantum readiness into the stack. They developed a Falcon-512 signature verification implementation that runs at 3.6 microseconds on Zen5 hardware — 2.6 times faster than the reference implementation — in anticipation of SIMD-0416, a proposed syscall that would expose post-quantum signature verification to Solana smart contracts. The team's quantum migration research also explores lattice-based approaches for future consensus and transaction signature schemes.

Security and Open Source

Firedancer's security model reflects its architecture. Each tile runs with the minimum system calls required for its function, enabling highly restrictive sandboxing. An independent security audit by Neodyme was completed during the testnet phase. A public bug bounty program remains active. All code is available under the Apache 2.0 license at github.com/firedancer-io/firedancer, and the team provides a live validator GUI dashboard at gui.firedancer.io for monitoring network health and client distribution.

Hardware requirements for running Firedancer are similar to those for Agave: a minimum of 24 CPU cores, 256 GB RAM, and a 2 TB NVMe SSD, with AVX512 support recommended for full signature-verification performance.