As part of BAM’s roadmap to support client diversity on Solana, Jito is excited to announce that the Frankendancer-compatible BAM client (aka FireBAM), is now live on testnet and mainnet and open for early third-party onboarding.

With this rollout, BAM and the BAM adoption incentive program is now available to an additional ~12% of Solana Validators.

Why FireBAM?

The Jito BAM client, like Jito-Solana before it, builds upon the Agave client created by Anza. It’s main difference is that it provides Solana with enhanced privacy, determinism and execution guarantees thanks to BAM’s TEE (Trusted Execution Environment) infrastructure. Today, ~28% of Solana network stake runs on Jito BAM.

Supporting Solana's client diversity goals meant bringing those same capabilities to Firedancer. With approximately 12% of mainnet stake running Frankendancer, enabling those validators to leverage BAM's scheduling and execution guarantees is critical to achieving that vision. As the Jump Crypto team works toward a full Firedancer release, FireBAM is designed to carry forward seamlessly, starting with Frankendancer today and extending to full Firedancer compatibility once it launches.

FireBAM bridges both worlds, merging Firedancer's performance, throughput, and speed with the privacy and deterministic execution that BAM uniquely provides.

How Does It Work?

FireBAM turns Firedancer into a BAM-compliant validator client by adding a new control/data plane and wiring it into TPU execution.

1. New BAM subsystem: Adds a dedicated bam tile plus gRPC/TLS client, auth challenge signing, scheduler stream handling, heartbeat/keepalive, and result/leader-state feedback.

2. Execution semantics in pack/bank: Pack tile handles BAM bundle assembly/scheduling, emits pre-exec failures, and publishes leader-state updates. Bank tile emits execution results back to BAM (atomic and non-atomic paths).

3. Runtime ops/control: Adds live reconfiguration through set-bam/get-bam for enable/disable and URL without restart.

4. Observability: Adds BAM metrics family in src/disco/metrics/metrics.xml and BAM GUI/plugin status feed.

Net effect: when connected to a BAM node, Firedancer executes BAM-ordered traffic and feeds exact execution outcomes back; when BAM is unhealthy/disconnected, it automatically falls back to normal QUIC/bundle ingestion paths.

Next Steps

Currently, FireBAM is still going through audits with Asymmetric Research, with final fixes expected before the end of June and a full mainnet release targeted for July. From there, the client will be open-sourced and accessible to all Solana validators.

Get in touch

If you’re a validator currently running Frankendancer and are interested in testing FireBAM on either testnet or mainnet, please get in touch here or reach out through the Jito Developer Discord.