Jito’s Solana data feed puts a price on seeing trades early

Solana traders can pay to see transactions earlier through BAM without gaining the right to change their order within a committed batch. The product turns information timing into a saleable service, even as its execution rules protect the sequence of an already scheduled batch.

BAM, Jito's Block Assembly Marketplace, streams transactions after a validator commits to executing them. That validator is the leader for a slot, its turn to build a block. The preconfirmation messages arrive before transactions are broken into shreds for network distribution. BAM's searcher documentation, updated Nov. 4, makes the distinction explicit: early visibility does not allow a subscriber to reorder or front-run that transaction within its batch.

Helius's current subscription terms and BAM's validator revenue rules show how that earlier view is priced and who earns from selling it.

A BAM preconfirmation appears only after the leader has accepted a scheduled batch and committed to executing it in order. Unscheduled pending transactions are excluded. The stream therefore reveals committed activity earlier than a shred-based feed, rather than opening a window to rearrange that same batch.

BAM says early testing with distribution partners measured a median, or p50, advantage of 5–10 milliseconds over their existing shred streams. That is an early-test result, not a guaranteed lead for every subscriber or transaction. Nor is the commitment finality: a leader can still skip its slot or land on a fork, so a preconfirmation describes what will execute if the block lands.

BAM announced the service on Sept. 9, 2026 through Helius and Triton. CryptoSlate's July 2025 BAM coverage concerned the proposed sequencing architecture; the commercial data stream adds a separate question about access.

Jito does not sell the stream directly. Its distributors handle pricing, billing and onboarding.

Helius currently offers preconfirmations on Developer, Business, Professional and Enterprise plans, excluding free accounts. For each subscription in a slot that delivers at least one message, the charge is the greater of 300 credits or 10 credits per delivered message. Zero-message slots and uncovered slots cost nothing.

That means 10 delivered messages cost 300 credits, while 100 cost 1,000 credits, according to its published table. Concurrent subscriptions are billed separately. These are credit charges, not a stated dollar price per trade, and Helius says pricing is subject to change.

Customers also need to distinguish the two signals Helius includes by default. Its own preconfirmations appear when the leader executes a transaction and include its local execution status. BAM's arrive earlier, when the leader commits to execution, and carry no execution status in Helius's stream. Both precede shreds, but they describe different stages.

A fixed execution sequence can coexist with paid access to earlier information.

The ordering guarantee concerns the committed batch. Preconfirmations are not finality. Sequence spacing is not time. The split is a published allocation, not measured payouts, profits or losses. Helius's own execution-stage signal is outside this BAM-only path.

Sources and evidence

Sources

1. BAM searcher documentation
2. BAM September 9 launch
3. BAM validator documentation
4. Helius access and signal documentation

Supporting facts

• BAM emits a preconfirmation only after a leader commits to executing a scheduled batch in a known order, before the transactions are shredded and propagated. [1] [2]
• According to BAM, seeing a committed transaction early does not let a subscriber reorder or front-run that transaction within its batch; unscheduled pending work is not streamed. [1]
• BAM access is distributed by Helius and Triton; distribution partners handle pricing, billing and onboarding, and Jito does not sell the stream directly. [1] [2]
• BAM's published preconfirmation revenue allocation is 35% for BAM validators, 35% for the Jito DAO and 30% for distributors. [2]
• BAM says its Verifier checks blocks against execution commitments and a deviating validator can be disconnected; a leader can nevertheless skip a slot or land on a fork, so preconfirmations are not finality. [3] [1]
• The published ordering protections and paid access terms address different dimensions: preserving a committed batch's sequence does not ensure all traders learn about it at the same time. [1] [4]

Method

Schematic of BAM's documented commitment-before-execution signal and partner distribution. A, B and C illustrate a batch, not actual trades. Revenue strip widths use the published 30/35/35 allocation on a 100% basis; no measured latency or earnings are drawn.

Scope

The ordering guarantee concerns the committed batch. Preconfirmations are not finality. Sequence spacing is not time. The split is a published allocation, not measured payouts, profits or losses. Helius's own execution-stage signal is outside this BAM-only path.

Infographic by CryptoSlate

Coverage is partial. BAM's public stake API reported about 39.1% of network stake running BAM at 16:46 UTC on Nov. 7. That is not a measurement of uninterrupted subscriber coverage: non-BAM leaders and opted-out BAM validators do not produce BAM preconfirmations, while Helius warns users to expect gaps.

Solana validators share the data revenue

The commercial arrangement reaches the supply side too. BAM's published split assigns 35% of preconfirmation revenue to BAM validators, 35% to the Jito DAO and 30% to distributors.

Under the current validator rules, AgaveBAM and FireBAM operators are automatically opted into streaming. They can forgo the revenue and opt out, but self-service controls are not available yet. Opting out currently requires a ticket through Jito Developers Discord.

The validator portion is shared through eligible leader slots rather than paid solely to whichever validator produced a particular stream. BAM describes payments over the month after distributors pay the DAO, using priority fees attached to market-tick transactions. Skipped or disconnected slots earn nothing.

This gives participation a revenue incentive alongside an execution obligation. BAM says its Verifier checks produced blocks against commitments and that a validator that deviates can be disconnected.

BAM's operating model therefore puts a price on earlier information while enforcing a committed execution sequence. Assessing access means watching distributor eligibility, usage charges and actual stream coverage alongside those ordering safeguards. A fixed place in a batch does not by itself give every trader an equally early view.