Agave vs Firedancer — Solana Validator Clients
Agave and Firedancer are two independent validator client implementations for Solana. Agave (formerly Solana Labs validator, now maintained by Anza) is the original Rust implementation. Firedancer is a ground-up C implementation built by Jump Crypto for maximum throughput.
Comparison
| Feature | Agave | Firedancer |
|---|---|---|
| Language | Rust | C |
| Maintainer | Anza (formerly Solana Labs) | Jump Crypto |
| Status | Production (mainnet) | Partial mainnet rollout |
| Architecture | Monolithic runtime | Modular tile-based architecture |
| Target TPS | Current network limits | 1M+ theoretical |
| RPC support | Full | Faithful RPC (compatible) |
| Geyser plugins | Yes (Yellowstone) | Planned compatibility |
Why two clients?
Client diversity improves network resilience. If a bug in one implementation causes validators to halt, validators running the other implementation continue producing blocks. This is the same principle behind Ethereum’s multi-client approach (Geth, Nethermind, Besu).
What Firedancer changes for developers
RPC compatibility
Firedancer implements a faithful RPC interface that is compatible with existing Solana RPC methods. Applications built against Agave’s RPC should work without changes against Firedancer’s RPC.
Transaction processing
Firedancer processes transactions differently internally but the on-chain behavior is identical. Your programs execute the same way regardless of which client the validator runs. The SVM (Solana Virtual Machine) specification ensures consistent execution.
Performance implications
Firedancer’s architecture is designed for higher throughput. As more validators adopt Firedancer, the network’s effective throughput may increase, which means:
- More transactions per block
- Potentially lower transaction fees during peak load
- Faster block propagation
FAQ
Do I need to change my code for Firedancer? No. Firedancer maintains RPC and execution compatibility with Agave. Existing programs and transactions work on both clients.
Which client do RPC providers run? Most RPC providers currently run Agave. As Firedancer matures, providers may switch or run both. From a developer perspective, the RPC interface is the same.
When will Firedancer be fully on mainnet? Firedancer is rolling out incrementally. Frankendancer (a hybrid using Firedancer’s networking with Agave’s execution) has been running on mainnet. The full Firedancer client is progressing toward mainnet readiness. Check Jump Crypto’s announcements for the latest timeline.
Sources
Updated: