technology
Jump Crypto: Firedancer Validator Release Adds Failover Options
By Roll · Chief of Staff · 19 Oct 2026
Jump Crypto released a new version of its Firedancer software for Solana validators on October 13, 2026. The update includes several practical features for operators.
Jump Crypto’s Firedancer team published Firedancer v26.10.2 on Oct. 13, 2026, a mainnet-ready release of its Solana validator software. NFA.
Release Overview
The version launched directly on GitHub. It arrived as a complete mainnet build ready for live network use. The notes list support for every feature in Solana 4.3 as the foundation for the update.
Failover Tools
Validators running the software can now write an Agave-compatible tower file in real time. This file lets operators switch to Agave during an issue without losing vote history. The process keeps the validator in a safe state before any switch happens.
Identity Commands
The set-identity command gained a new requirement option. It can now demand a tower file through a vote-history-file argument. This change ties identity updates more closely to existing vote data.
Wait Command
A firedancer wait command was added to the tool set. It pauses operation until the validator reaches a safe state for failover or exit. Operators use this step to avoid abrupt stops during maintenance.
Added RPC Methods
The built-in RPC layer gained four new methods. These include getMaxRetransmitSlot, getSlotLeader, getSlotLeaders and getLeaderSchedule. Each method supplies direct data that was previously available only through external sources.
Entrypoint Role
Firedancer gained the ability to serve as an entrypoint node. This lets Agave validators connect through it for initial network entry. The feature expands how the software fits into mixed validator setups.
Networking Adjustments
The mlx5 network setup received an extra stage. This stage loads the ib_uverbs kernel module during startup. The step ensures smoother hardware initialization on supported systems.
Stake Delegation Path
Stake delegations now carry a fallback disk path. The path sits unused during normal operation yet provides a backup location if the primary path fails.
Upgrade Notes
The identity change creates a break with older admin commands. Commands from v26.9.x binaries no longer work with the new version. Operators must update tools when moving to this release.
The release notes present each item as a direct addition to the validator package. Holders receive these functions through a single mainnet build that covers core network tasks and fallback options.