Firedancer v26.09.4 cuts the mainnet validator's memory from 307 GB to 182 GB
Victoria Shinder2 min readFiredancer, the independent Solana validator client developed by Jump Crypto, published v26.09.4 on 22 September and labels it a mainnet-ready release. The headline change is memory: the project says the footprint drops from about 307 GB to about 182 GB on mainnet and from about 233 GB to 109 GB on testnet.
The release also adds a kernel-bypass networking provider for Mellanox ConnectX network cards based on mlx5. The [net] provider setting now defaults to "auto" and picks the new driver where the hardware supports it. It brings support for the Solana 4.3 features, which the notes list as no-op transactions, a doubled disinflation rate and the removal of inactive stake, along with faster snapshot loading, gossip performance work and stability fixes across networking, repair, runtime and snapshot loading. OpenSSL is updated to 3.6.4.
Two configuration changes need attention. In the [snapshots] section, the *_snapshot_interval_slots settings are renamed to *_snapshot_interval_blocks, and [net] auto_level is removed. The notes tell operators to re-run firedancer configure init all after upgrading. The release follows a string of versions this month, including mainnet releases on 10 and 15 September and prereleases in between.
What it means
Memory has been one of the costs that shape who can run a Solana validator. Cutting the requirement by roughly 125 GB on mainnet widens the range of hardware that can host Firedancer, which matters for the client's main purpose: giving Solana a second, independently written validator so that a bug in one implementation does not halt the whole network.
For operators the upgrade is not a drop-in replacement. Renamed configuration keys are exactly the kind of change that fails quietly if a template is carried forward unchanged, so the re-run of the configure step the notes ask for is the step to automate. The kernel-bypass default also deserves a check: "auto" selecting a new network path on supported cards is a behaviour change, and operators should confirm which provider their nodes actually use after the upgrade. The Solana 4.3 features arrive with the client, but their activation on the network is a separate, cluster-wide decision.