Firedancer v26.11.0 makes Alpenglow the only consensus mode and adds failover, on testnet
The Firedancer team published two releases of its Solana validator client on 11 November: v26.11.0 for testnet and v26.10.8, which it marks as ready for mainnet.
The release notes say v26.11.0 is not suggested for mainnet. Its first change is that Alpenglow is now the only consensus mode available. Three configuration keys are no longer supported as a result: [consensus] alpenglow, [tiles.tower] write_vote_history_file and [tiles.txsend] txsend_src_port. Merges on 14 November continued the clean-up, with pull requests titled "keyguard: remove vote txn support" and "disco: remove txsend link leftovers".
The release adds a failover mechanism between two Firedancer validators, which the team describes as easy to use, fast and secure, with a separate guide in the documentation. It supports all Solana 4.4 features and three feature gates: geo_aware_leader_schedule (SIMD-0675), validator_location_registration (SIMD-0674) and stricter_shred_validation (SIMD-0504).
Mainnet memory usage drops from 159 GiB to 142 GiB. The transaction cache and the cost tracker get fallback paths on disk, set under [paths] txncache and [paths] cost_tracker, which the notes say are not written during normal, healthy operation. A new kernel-bypass networking provider, iavf, supports Intel ice and i40e network cards through SR-IOV virtual functions. An experimental auction strategy for block packing can be enabled with [tiles.pack] schedule_strategy = "auction", and the experimental efficient mode gets further improvements.
The mainnet-ready v26.10.8 is a smaller release. It speeds up loading incremental snapshots at the start of an epoch by enlarging the in-memory stake delegations cache and improves its telemetry, speeds up transaction replay by removing redundant serial execution, and fixes a rare address translation bug for account data during cross-program invocations.

Why it matters
Operators should expect the Alpenglow-only change and the removed keys when v26.11.x reaches mainnet, and configuration files that still set them will need editing. For now, mainnet validators running Firedancer stay on the v26.10 line.