Today we're announcing that BAM Preconfirmations are live and accessible through our first two distribution partners: Helius and Triton.

Traders, searchers and applications can now get access to the lowest latency data stream to over 34% of network stake (as of writing) from validators currently running BAM-compatible clients.

What are Preconfirmations?

BAM Preconfirmations is the stream of transactions that the current BAM-enabled leader has committed to executing, as scheduled by a BAM Node. They sit further upstream of shreds: the commit confirmation fires before those transactions are shredded and propagated across the network.

BAM Preconfirmations are ideal for users that have latency sensitive use cases such as arbitrage, liquidations and market making, and want to consume low latency state information to react as fast as possible. Early testing with distribution partners indicated a p50 advantage of over 5-10ms over their existing shred streams.

Why You Can Trust BAM Preconfs

A BAM Preconfirmation is not a prediction. It is only emitted after the leader has received a scheduled batch from the BAM Node and committed to executing it, so what you see in the stream is what the validator has already agreed to execute, in that order. Executing committed batches as scheduled is a protocol obligation for every BAM validator, and the BAM Verifier checks the resulting blocks against those commitments. 

A validator that deviates is detected and can be disconnected from the network. As with any pre-block signal on Solana, a preconf is not finality: a leader can still skip its slot or land on a fork, so preconfs tell you what will execute if the block lands, not that the block will land.

Preconfirmation Data Stream Flow

Here’s how preconfirmations flow based on BAM’s unique transaction processing pipeline:

1. Once a BAM-enabled validator comes up on the leader schedule, the BAM Node receives orderflow and schedules it
2. The BAM Node sends the scheduled transactions to the leader for execution
3. The leader commits to executing them and sends a commit confirmation back to the BAM Node
4. That confirmation triggers the BAM Node to stream the preconfirmation out to co-located distributors
5. Distributors receive the preconfirmations and serve them to their subscribers

Distribution Partners

We're partnering with Helius and Triton to distribute BAM Preconfirmations. Working with them enables BAM to access their existing network of subscribers, and gives subscribers the flexibility to onboard directly to their preferred provider and use the existing billing methods without needing to create additional accounts with Jito.

Revenue Distribution

Validators running BAM clients (AgaveBAM or FireBAM) will be automatically opted in to streaming preconfirmations to our distribution partners, enabling them to monetize their preconfirmation streams immediately.

For those that don't want to stream out their preconfirmations, there will be an option to opt out and forgo the associated revenue. Self-serve opt-out is expected in a future BAM client release. To opt out today, reach out on the Jito Developers Discord to get manually added to the opt-out list.

Stakeholder Splits

The distributors will bear responsibility of charging end customers through their subscription service, and total revenue generated will be split in the following way:

• 30% for Distributors
• 35% for BAM Validators
• 35% for Jito DAO

The 35% going to BAM Validators is shared out across the network. The mechanism below explains how.

Validator Revenue Distribution Mechanism

Distributors pay Jito DAO, and BAM validators receive their share over the following month. That share gets paid slot by slot via priority fees: the connected BAM Node submits a transaction for the market-tick program, and for opted-in leaders it attaches a priority fee to that transaction.

Since leader slots are stake-weighted, paying the same amount per slot ends up stake-proportional on its own. Validators only get paid for slots where they are connected to BAM, therefore skipped or disconnected slots pay nothing.

Paying out as a priority fee keeps the value inside Solana's in-protocol fee mechanism, so the revenue lands as an on-chain block reward.

Based on the go-to-market timeline for BAM Preconfs, BAM validators can expect to start seeing the incremental revenue starting October 2026.

Get Access Today

If you’re a searcher, app or trader and want to get access to BAM preconfirmations, please visit:

• Triton: https://customers.triton.one/onboarding/ 
• Helius: https://www.helius.dev/docs/pre-confirmations/overview 

Distribution partners will be able to answer all your questions regarding pricing and access, as well as provide timely customer support once onboarded.

BAM Validator Questions

BAM Validators – if you have any questions about BAM Preconfirmations please open a ticket on the Jito Developers Discord #🆘-open-ticket channel choose the option for “Validator Support”